naseke Posté(e) le 11 avril 2009 Partager Posté(e) le 11 avril 2009 Bonjour, Je suis propriétaire d'un 408 depuis Novembre 2008 sans problèmes (sauf une bizarrerie avec la carte ethernet mais disparu après reboot)... Bref j'ai mis la dernière version du firmware (DSM 2.1-0839) et depuis j'ai régulièrement des remise à zéro de la config du nas et ce matin il a redémarrer sans son volume 1 ! Etant donné qu'il se réinitialisait souvent toutes les fonctions avancés été désactiver sauf l'arret automatique à 1h du mat et le redemarrage à 6h... et c'est justement à 6 h qu'il a commencer à biper alors que la veille jusqu'à minuit et demi je l'utilisé ... j'ai fait un e2fsck /dev/md2 mais il m'a répondu : e2fsck: Bad magic number in super-block while trying to open /dev/md2 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> j'ai recommencé avec l'optiojn -b mais la réponse est la même ... Quelqu'un peut m'indiquer une solution SVP car j'avais (ça y est j'en parle déjà au passé ...) presque 1 To de données. Merci par avance. alors mon 408 est configuré avec 4 diques de 1 To en raid 5 et les dd sont des ST31000340AS seagate 7200.11 1 To avec comme firmware le SD1A apres quelques recherches : Bon aprés recherche dans la log message j'ai eu hier un pepin ... (la question est pourquoi ... ) Apr 11 00:47:06 kernel: sd 3:0:0:0: timing out command, waited 360s Apr 11 00:47:06 kernel: end_request: I/O error, dev sdd, sector 6545375 Apr 11 00:47:06 kernel: read error, md2, sdd3 index [3], sector 791960 [raid5_align_endio] Apr 11 00:53:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 00:53:06 kernel: end_request: I/O error, dev sdb, sector 6545375 Apr 11 00:53:06 kernel: read error, md2, sdb3 index [1], sector 6545383 [raid5_end_read_request] Apr 11 00:53:06 kernel: sd 3:0:0:0: timing out command, waited 360s Apr 11 00:53:06 kernel: end_request: I/O error, dev sdd, sector 3758167 Apr 11 00:53:06 kernel: read error, md0, sdd1 index [3], sector 3758175 [raid1_end_read_request] Apr 11 00:53:06 kernel: raid1: sdd1: rescheduling sector 3758104 Apr 11 01:20:06 kernel: sd 2:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdc, sector 6545375 Apr 11 01:20:06 kernel: read error, md2, sdc3 index [2], sector 6545383 [raid5_end_read_request] Apr 11 01:20:06 kernel: raid5: Disk failure on sdd3, disabling device. Operation continuing on 3 devices Apr 11 01:20:06 kernel: drivers/md/raid5.c[1485]:syno_error_for_internal: disk error on sdc3 Apr 11 01:20:06 kernel: drivers/md/raid5.c[1485]:syno_error_for_internal: disk error on sdb3 Apr 11 01:20:06 kernel: ext3_quota_write 2869: Hit bug#2406! err=[-5] Apr 11 01:20:06 kernel: VFS: dquota write failed on dev md2 Apr 11 01:20:06 kernel: ext3_quota_write 2869: Hit bug#2406! err=[-5] Apr 11 01:20:06 kernel: VFS: dquota write failed on dev md2 Apr 11 01:20:06 kernel: sd 1:0:0:0: timing out command, waited 60s Apr 11 01:20:06 kernel: sd 2:0:0:0: timing out command, waited 60s Apr 11 01:20:06 kernel: sd 3:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdd, sector 3758167 Apr 11 01:20:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdb, sector 1953519815 Apr 11 01:20:06 kernel: md: super_written gets error=-5, uptodate=0 Apr 11 01:20:06 kernel: drivers/md/raid5.c[1485]:syno_error_for_internal: disk error on sdb3 Apr 11 01:20:06 kernel: sd 2:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdc, sector 1953519815 Apr 11 01:20:06 kernel: md: super_written gets error=-5, uptodate=0 Apr 11 01:20:06 kernel: drivers/md/raid5.c[1485]:syno_error_for_internal: disk error on sdc3 Apr 11 01:20:06 kernel: sd 1:0:0:0: timing out command, waited 60s Apr 11 01:20:06 kernel: sd 2:0:0:0: timing out command, waited 60s Apr 11 01:20:06 kernel: sd 3:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdd, sector 3758167 Apr 11 01:20:06 kernel: raid1: Disk failure on sdd1, disabling device. Apr 11 01:20:06 kernel: ^IOperation continuing on 3 devices Apr 11 01:20:06 kernel: raid1: sdb1: redirecting sector 3758104 to another mirror Apr 11 01:20:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdb, sector 1953519815 Apr 11 01:20:06 kernel: md: super_written gets error=-5, uptodate=0 Apr 11 01:20:06 kernel: drivers/md/raid5.c[1485]:syno_error_for_internal: disk error on sdb3 Apr 11 01:20:06 kernel: sd 2:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdc, sector 1953519815 Apr 11 01:20:06 kernel: md: super_written gets error=-5, uptodate=0 Apr 11 01:20:06 kernel: drivers/md/raid5.c[1485]:syno_error_for_internal: disk error on sdc3 Apr 11 01:20:06 kernel: RAID5 conf printout: Apr 11 01:20:06 kernel: --- rd:4 wd:3 Apr 11 01:20:06 kernel: disk 0, o:1, dev:sda3 Apr 11 01:20:06 kernel: disk 1, o:1, dev:sdb3 Apr 11 01:20:06 kernel: disk 2, o:1, dev:sdc3 Apr 11 01:20:06 kernel: disk 3, o:0, dev:sdd3 Apr 11 01:20:06 kernel: Buffer I/O error on device md2, logical block 3094 Apr 11 01:20:06 kernel: lost page write due to I/O error on md2 Apr 11 01:20:06 kernel: Aborting journal on device md2. Apr 11 01:20:06 kernel: Buffer I/O error on device md2, logical block 695 Apr 11 01:20:06 kernel: lost page write due to I/O error on md2 Apr 11 01:20:06 kernel: RAID5 conf printout:Apr 11 01:20:06 kernel: disk 1, o:1, dev:sdb3 Apr 11 01:20:06 kernel: --- rd:4 wd:3 Apr 11 01:20:06 kernel: disk 0, o:1, dev:sda3 Apr 11 01:20:06 kernel: disk 1, o:1, dev:sdb3 Apr 11 01:20:06 kernel: disk 2, o:1, dev:sdc3 Apr 11 01:20:06 kernel: sd 2:0:0:0: timing out command, waited 60s Apr 11 01:20:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdb, sector 3758167 Apr 11 01:20:06 kernel: read error, md0, sdb1 index [1], sector 3758175 [raid1_end_read_request] Apr 11 01:20:06 kernel: raid1: sdb1: rescheduling sector 3758104 Apr 11 01:20:06 kernel: sd 1:0:0:0: timing out command, waited 60s Apr 11 01:20:06 kernel: sd 2:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdc, sector 4979903 Apr 11 01:20:06 kernel: md: super_written gets error=-5, uptodate=0 Apr 11 01:20:06 kernel: raid1: Disk failure on sdc1, disabling device. Apr 11 01:20:06 kernel: ^IOperation continuing on 2 devices Apr 11 01:20:06 kernel: sd 2:0:0:0: timing out command, waited 60s Apr 11 01:20:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 01:20:06 kernel: end_request: I/O error, dev sdb, sector 4979903 Apr 11 01:20:06 kernel: md: super_written gets error=-5, uptodate=0 Apr 11 01:20:06 kernel: raid1: Disk failure on sdb1, disabling device. Apr 11 01:20:06 kernel: ^IOperation continuing on 1 devices Apr 11 01:20:06 kernel: RAID1 conf printout: Apr 11 01:20:06 kernel: --- wd:1 rd:4 Apr 11 01:20:06 kernel: disk 0, wo:0, o:1, dev:sda1 Apr 11 01:20:06 kernel: disk 1, wo:1, o:0, dev:sdb1 Apr 11 01:20:06 kernel: disk 2, wo:1, o:0, dev:sdc1 Apr 11 01:20:06 kernel: disk 3, wo:1, o:0, dev:sdd1 Apr 11 01:20:06 kernel: RAID1 conf printout: Apr 11 01:20:06 kernel: --- wd:1 rd:4 Apr 11 01:20:06 kernel: disk 0, wo:0, o:1, dev:sda1 Apr 11 01:20:06 kernel: disk 2, wo:1, o:0, dev:sdc1 Apr 11 01:20:06 kernel: disk 3, wo:1, o:0, dev:sdd1 Apr 11 01:20:06 kernel: RAID1 conf printout: Apr 11 01:20:06 kernel: --- wd:1 rd:4 Apr 11 01:20:06 kernel: disk 0, wo:0, o:1, dev:sda1 Apr 11 01:20:06 kernel: disk 2, wo:1, o:0, dev:sdc1 Apr 11 01:20:06 kernel: disk 3, wo:1, o:0, dev:sdd1 Apr 11 01:20:06 kernel: RAID1 conf printout: Apr 11 01:20:06 kernel: --- wd:1 rd:4 Apr 11 01:20:06 kernel: disk 0, wo:0, o:1, dev:sda1 Apr 11 01:20:06 kernel: disk 3, wo:1, o:0, dev:sdd1 Apr 11 01:20:06 kernel: RAID1 conf printout: Apr 11 01:20:06 kernel: --- wd:1 rd:4 Apr 11 01:20:06 kernel: disk 0, wo:0, o:1, dev:sda1 Apr 11 01:20:06 kernel: disk 3, wo:1, o:0, dev:sdd1 Apr 11 01:20:06 kernel: RAID1 conf printout: Apr 11 01:20:06 kernel: --- wd:1 rd:4 Apr 11 01:20:06 kernel: disk 0, wo:0, o:1, dev:sda1 Apr 11 01:20:06 kernel: raid1: sda1: redirecting sector 3758104 to another mirror Apr 11 01:20:08 findhostd: si_pid=[4022], process=[/bin/sh] Apr 11 01:20:08 findhostd: si_ppid=[4021], process=[sh] Apr 11 01:20:08 findhostd: findhostd.c:52(FHOSTDExit) exit on signal[10] Apr 11 01:20:08 root: /usr/syno/etc/rc.d/S98findhostd.sh stop findhostd Apr 11 01:21:06 kernel: sd 1:0:0:0: timing out command, waited 60s Apr 11 01:21:06 kernel: sd 2:0:0:0: timing out command, waited 360s Apr 11 01:21:06 kernel: end_request: I/O error, dev sdc, sector 1953519815 Apr 11 01:21:06 kernel: md: super_written gets error=-5, uptodate=0 Apr 11 01:21:06 kernel: drivers/md/raid5.c[1485]:syno_error_for_internal: disk error on sdc3 Apr 11 01:27:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 01:27:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 01:27:06 kernel: end_request: I/O error, dev sdb, sector 1953519815 Apr 11 01:27:06 kernel: md: super_written gets error=-5, uptodate=0 Apr 11 01:27:06 kernel: drivers/md/raid5.c[1485]:syno_error_for_internal: disk error on sdb3 Apr 11 01:27:06 scemd: smartctl_marvell_command_interface.c:93 marvell ioctl SCSI_IOCTL_SEND_COMMAND error Apr 11 01:33:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 01:33:06 kernel: end_request: I/O error, dev sdb, sector 4994614 Apr 11 01:33:06 kernel: read error, md1, sdb2 index [1], sector 4994622 [raid1_end_read_request] Apr 11 01:33:06 kernel: raid1: sdb2: rescheduling sector 14464 Apr 11 01:33:06 kernel: read error, md1, sdb2 index [1], sector 4994630 [raid1_end_read_request] Apr 11 01:33:06 kernel: raid1: sdb2: rescheduling sector 14472 Apr 11 01:33:06 kernel: read error, md1, sdb2 index [1], sector 4994638 [raid1_end_read_request] Apr 11 01:33:06 kernel: raid1: sdb2: rescheduling sector 14480 Apr 11 01:33:06 kernel: read error, md1, sdb2 index [1], sector 4994646 [raid1_end_read_request] Apr 11 01:33:06 kernel: raid1: sdb2: rescheduling sector 14488 Apr 11 01:33:06 scemd: smartctl_marvell_command_interface.c:93 marvell ioctl SCSI_IOCTL_SEND_COMMAND error Apr 11 01:33:06 kernel: sd 2:0:0:0: timing out command, waited 360s Apr 11 01:39:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 01:39:06 kernel: end_request: I/O error, dev sdb, sector 4994614 Apr 11 01:39:06 scemd: smartctl_marvell_command_interface.c:93 marvell ioctl SCSI_IOCTL_SEND_COMMAND error Apr 11 01:39:06 kernel: sd 3:0:0:0: timing out command, waited 360s Apr 11 01:45:06 kernel: sd 2:0:0:0: timing out command, waited 360s Apr 11 01:45:06 kernel: end_request: I/O error, dev sdc, sector 4994614 Apr 11 01:51:06 kernel: sd 3:0:0:0: timing out command, waited 360s Apr 11 01:51:06 kernel: end_request: I/O error, dev sdd, sector 4994614 Apr 11 01:57:06 kernel: sd 3:0:0:0: timing out command, waited 360s Apr 11 01:57:06 kernel: end_request: I/O error, dev sdd, sector 4994614 Apr 11 01:57:06 kernel: raid1: Disk failure on sdd2, disabling device. Apr 11 01:57:06 kernel: ^IOperation continuing on 3 devices Apr 11 02:03:06 kernel: sd 2:0:0:0: timing out command, waited 360s Apr 11 02:03:06 kernel: end_request: I/O error, dev sdc, sector 4994614 Apr 11 02:03:06 kernel: raid1: Disk failure on sdc2, disabling device. Apr 11 02:03:06 kernel: ^IOperation continuing on 2 devices Apr 11 02:09:06 kernel: sd 1:0:0:0: timing out command, waited 360s Apr 11 02:09:06 kernel: end_request: I/O error, dev sdb, sector 4994614 Apr 11 02:09:06 kernel: raid1: Disk failure on sdb2, disabling device. Apr 11 02:09:06 kernel: ^IOperation continuing on 1 devices Apr 11 02:09:06 kernel: raid1: sda2: redirecting sector 14464 to another mirror Apr 11 02:09:06 kernel: raid1: sda2: redirecting sector 14472 to another mirror Apr 11 02:09:06 kernel: raid1: sda2: redirecting sector 14480 to another mirror Apr 11 02:09:06 kernel: raid1: sda2: redirecting sector 14488 to another mirror Apr 11 02:09:06 kernel: RAID1 conf printout: Apr 11 02:09:06 kernel: --- wd:1 rd:4 Apr 11 02:09:06 kernel: disk 0, wo:0, o:1, dev:sda2 Apr 11 02:09:06 kernel: disk 1, wo:1, o:0, dev:sdb2 Apr 11 02:09:06 kernel: disk 2, wo:1, o:0, dev:sdc2 Apr 11 02:09:06 kernel: disk 3, wo:1, o:0, dev:sdd2 Apr 11 02:09:06 kernel: RAID1 conf printout: Apr 11 02:09:06 kernel: --- wd:1 rd:4 Apr 11 02:09:06 kernel: disk 0, wo:0, o:1, dev:sda2 Apr 11 02:09:06 kernel: disk 2, wo:1, o:0, dev:sdc2 Apr 11 02:09:06 kernel: disk 3, wo:1, o:0, dev:sdd2 Apr 11 02:09:06 kernel: RAID1 conf printout: Apr 11 02:09:06 kernel: --- wd:1 rd:4 Apr 11 02:09:06 kernel: disk 0, wo:0, o:1, dev:sda2 Apr 11 02:09:06 kernel: disk 2, wo:1, o:0, dev:sdc2 Apr 11 02:09:06 kernel: disk 3, wo:1, o:0, dev:sdd2 Apr 11 02:09:06 kernel: RAID1 conf printout: Apr 11 02:09:06 kernel: --- wd:1 rd:4 Apr 11 02:09:06 kernel: disk 0, wo:0, o:1, dev:sda2 Apr 11 02:09:06 kernel: disk 3, wo:1, o:0, dev:sdd2 Apr 11 02:09:06 kernel: RAID1 conf printout: Apr 11 02:09:06 kernel: --- wd:1 rd:4 Apr 11 02:09:06 kernel: disk 0, wo:0, o:1, dev:sda2 Apr 11 02:09:06 kernel: disk 3, wo:1, o:0, dev:sdd2 Apr 11 02:09:06 kernel: RAID1 conf printout: Apr 11 02:09:06 kernel: --- wd:1 rd:4 Apr 11 02:09:06 kernel: disk 0, wo:0, o:1, dev:sda2 Alors pourquoi ce caca nerveux ???? mais bon le matin à 6h voila ce qui c'est passé : Apr 11 06:01:17 kernel: Synology Hardware Version: DS408v10-j Apr 11 06:01:17 kernel: Internal HD num: 4 Apr 11 06:01:17 kernel: Internal netif num: 1 Apr 11 06:01:17 kernel: Found initrd at 0xbfefc000:0xbffac6ff Apr 11 06:01:17 kernel: Zone PFN ranges: Apr 11 06:01:17 kernel: DMA 0 -> 131072 Apr 11 06:01:17 kernel: Normal 131072 -> 131072 Apr 11 06:01:17 kernel: Movable zone start PFN for each node Apr 11 06:01:17 kernel: early_node_map[1] active PFN ranges Apr 11 06:01:17 kernel: 0: 0 -> 131072 Apr 11 06:01:17 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Apr 11 06:01:17 kernel: PID hash table entries: 2048 (order: 11, 8192 bytes) Apr 11 06:01:17 kernel: Mount-cache hash table entries: 512 Apr 11 06:01:17 kernel: PCI: 0001:01:00.0: class b20 doesn't match header type 01. Ignoring class. Apr 11 06:01:17 kernel: PCI: Cannot allocate resource region 0 of device 0001:02:00.0 Apr 11 06:01:17 kernel: Freeing initrd memory: 705k freed Apr 11 06:01:17 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Apr 11 06:01:17 kernel: RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize Apr 11 06:01:17 kernel: Driver 'sd' needs updating - please use bus_type methods Apr 11 06:01:17 kernel: PCI: Enabling device 0001:02:00.0 (0000 -> 0003) Apr 11 06:01:17 kernel: Delay 10 seconds to wait for disk 1 ready. Apr 11 06:01:17 kernel: Delay 10 seconds to wait for disk 2 ready. Apr 11 06:01:17 kernel: Delay 10 seconds to wait for disk 3 ready. Apr 11 06:01:17 kernel: Delay 10 seconds to wait for disk 4 ready. Apr 11 06:01:17 kernel: Amd/Fujitsu Extended Query Table at 0x0040 Apr 11 06:01:17 kernel: SYNOMTD-0: Swapping erase regions for broken CFI table. Apr 11 06:01:17 kernel: Mac0: 00:11:32:02:25:22 Apr 11 06:01:17 kernel: : 87E9N00516 Apr 11 06:01:17 kernel: raid6: int32x1 125 MB/s Apr 11 06:01:17 kernel: raid6: int32x2 210 MB/s Apr 11 06:01:17 kernel: raid6: int32x4 277 MB/s Apr 11 06:01:17 kernel: raid6: int32x8 222 MB/s Apr 11 06:01:17 kernel: raid6: using algorithm int32x4 (277 MB/s) Apr 11 06:01:17 kernel: md: sda2 has different UUID to sda1 Apr 11 06:01:17 kernel: md: sda3 has different UUID to sda1 Apr 11 06:01:17 kernel: md: sdb2 has different UUID to sda1 Apr 11 06:01:17 kernel: md: sdb3 has different UUID to sda1 Apr 11 06:01:17 kernel: md: sdc2 has different UUID to sda1 Apr 11 06:01:17 kernel: md: sdc3 has different UUID to sda1 Apr 11 06:01:17 kernel: md: sdd2 has different UUID to sda1 Apr 11 06:01:17 kernel: md: sdd3 has different UUID to sda1 Apr 11 06:01:17 kernel: md: kicking non-fresh sdb1 from array! Apr 11 06:01:17 kernel: md: kicking non-fresh sdc1 from array! Apr 11 06:01:17 kernel: md: kicking non-fresh sdd1 from array! Apr 11 06:01:17 kernel: md: sda3 has different UUID to sda2 Apr 11 06:01:17 kernel: md: sdb3 has different UUID to sda2 Apr 11 06:01:17 kernel: md: sdc3 has different UUID to sda2 Apr 11 06:01:17 kernel: md: sdd3 has different UUID to sda2 Apr 11 06:01:17 kernel: md: kicking non-fresh sdb2 from array! Apr 11 06:01:17 kernel: md: kicking non-fresh sdc2 from array! Apr 11 06:01:17 kernel: md: kicking non-fresh sdd2 from array! Apr 11 06:01:17 kernel: md: kicking non-fresh sdb3 from array! Apr 11 06:01:17 kernel: md: kicking non-fresh sdc3 from array! Apr 11 06:01:17 kernel: md: kicking non-fresh sdd3 from array! Apr 11 06:01:17 kernel: raid5: raid level 5 set md2 active with 1 out of 4 devices, algorithm 2 Apr 11 06:01:17 kernel: RAID5 conf printout: Apr 11 06:01:17 kernel: --- rd:4 wd:1 Apr 11 06:01:17 kernel: disk 0, o:1, dev:sda3 Apr 11 06:01:17 kernel: VFS: Mounted root (ext2 filesystem). Apr 11 06:01:17 kernel: ds508_synobios: module license 'Synology Inc.' taints kernel. Apr 11 06:01:17 kernel: Brand: Synology Apr 11 06:01:17 kernel: Model: DS-408 Apr 11 06:01:17 kernel: synobios: unload Apr 11 06:01:17 kernel: VFS: Mounted root (ext3 filesystem). Apr 11 06:01:17 kernel: Freeing unused kernel memory: 152k init Apr 11 06:01:17 kernel: Brand: Synology Apr 11 06:01:17 kernel: Model: DS-408 Apr 11 06:01:17 s00_synocheckfstab: s00_synocheckfstab_main(240): /etc/fstab format error. szBuf=/dev/md2 /volume1 ext3 defaults 0 0 Apr 11 06:01:17 fsck.ext3: EXT2_ET_BAD_MAGIC(190), 6E20 Apr 11 06:01:17 fsck.ext3: EXT2_ET_BAD_MAGIC(190), 0 Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:17 kernel: VFS: Can't find ext3 filesystem on dev md2. Apr 11 06:01:23 scemd: scemd.c:97 fan_type=3, led_type=1, raid_type=1, dual_power_type=1, auto_poweron_type=1 Apr 11 06:01:23 scemd: modules/raid_sys_volume_check.c:146 MD0 active disks 1, designed disks 4 Apr 11 06:01:23 scemd: modules/raid_sys_volume_check.c:146 MD1 active disks 1, designed disks 4 Apr 11 06:01:23 scemd: modules/disk_hibernation.c:86 Force hibernation enable, idle minutes 20 Apr 11 06:01:23 synoprint: printer_device_open.c:16 bad parameter. Apr 11 06:01:23 synousbdisk: RCClean succeeded Apr 11 06:01:24 synocheckshare: Fix shares in smb.conf. Apr 11 06:01:24 synocheckshare: service_user_home.c:276 SYNOShareRSectionRemove failed. synoerr=[0x2000] Apr 11 06:01:24 ddnsd: main(ddnsd.c:1729): not enable DDNS, shutdown daemon Apr 11 06:01:32 syno_hdd_util: Model:[ST31000340AS], Firmware:[SD1A], S/N:[6QJ00ZKJ] in [/dev/sdd] is not ssd Apr 11 06:01:32 syno_hdd_util: Model:[ST31000340AS], Firmware:[SD1A], S/N:[5QJ0W4RS] in [/dev/sdc] is not ssd Apr 11 06:01:32 syno_hdd_util: Model:[ST31000340AS], Firmware:[SD1A], S/N:[5QJ0X2ZK] in [/dev/sdb] is not ssd Apr 11 06:01:32 syno_hdd_util: Model:[ST31000340AS], Firmware:[SD1A], S/N:[5QJ0Z64W] in [/dev/sda] is not ssd Apr 11 06:01:34 upsd[3703]: Can't connect to UPS. Try to re-start driver Apr 1id r1 06:01:34 upsd[3827]: not listening on 0.0.0.0 port 3493 Apr 11 06:01:36 usbhid-ups[3872]: Startup successful Apr 11 06:01:36 upsd[3874]: Startup successful Apr 11 06:01:42 scemd: modules/raid_data_volume_check.c:889 /volume1 state changes from 0 to 3. Fin de l'histoire plus de raid ... par contre comment utiliser mdadm --assemble ? le problème viendrait de l'hibernation couplé avec l'arret automatique ? Lien vers le commentaire Partager sur d’autres sites More sharing options...
nobobo Posté(e) le 11 avril 2009 Partager Posté(e) le 11 avril 2009 Bonjour, As tu pris les précautions nécessaires (en autre, sauvegarde de tes données ...) et aux préconisations Synology (désactivation des applications, ...) avant maj du firmware ? Il semblerait qu'il y a eu un problème lors de ta maj en 839. Pour ma part, j'ai effectué récemment la maj en 839 de mon Syno DS-408 sans aucun souci et tout fonctionne correctement. Pour information, hibernation et arrêt/relance automatique sont activés sur mon Syno et je n'ai aucun souci de fonctionnement. Bon courage. Lien vers le commentaire Partager sur d’autres sites More sharing options...
naseke Posté(e) le 12 avril 2009 Auteur Partager Posté(e) le 12 avril 2009 Bonjour, As tu pris les précautions nécessaires (en autre, sauvegarde de tes données ...) et aux préconisations Synology (désactivation des applications, ...) avant maj du firmware ? Il semblerait qu'il y a eu un problème lors de ta maj en 839. Pour ma part, j'ai effectué récemment la maj en 839 de mon Syno DS-408 sans aucun souci et tout fonctionne correctement. Pour information, hibernation et arrêt/relance automatique sont activés sur mon Syno et je n'ai aucun souci de fonctionnement. Bon courage. Bonjour, Merci pour ta réponse ... Malheureusement les sauvegarde commence à être difficile au delà de 1To... et c 'est plutôt du coté matériel que je prévoyez une panne pas du côté OS bon enfin pour le deuxième photostation et download station étaient activés ... ça à peut être joué... mais je suis le seul dessus donc pas d'activité ... Lien vers le commentaire Partager sur d’autres sites More sharing options...
Messages recommandés
Archivé
Ce sujet est désormais archivé et ne peut plus recevoir de nouvelles réponses.