File system corrupt?

[xburchartz]

Sinds een paar dagen heb ik problemen met m'n DS107+. Ik merkte op een gegeven moment dat ik bestanden in mijn /volume1 niet meer kon hernoemen/verwijderen. Ik krijg dan de melding 'read-only file system'. Na een reboot gaat het weer even, tot het probleem op een gegeven moment weer optreedt.

Ik dacht dat het aan de firmware kon liggen (had nog 571) dus heb die zojuist geupgrade naar 598. Het probleem bestaat nog steeds. Ik heb op zowel het Nederlandse als het Engelse forum niks kunnen vinden. Wel heb ik via google gezien dat er geadviseerd werd om naar de logs te kijken. Ik zal de output van dmesg en tail -100 /var/log/messages hieronder weergeven. Ik schrik wel van de meldingen dat er file system errors zijn. Er wordt gezegd dat ik e2fsck moet draaien. Maar ik heb geen idee hoe dat moet. Als ik dat zonder opties intyp, gebeurt er niks, en mijn gokje dat ik dan e2fsck dba3 moest doen, resulteerde in een foutmelding. Verder durf ik niets te doen want eigenlijk weet ik niet waar ik mee bezig ben.

Iemand tips?

Output dmesg:

Code: [Selecteer]

, size   1MB
PCI0_MEM ....base e8000000, size 128MB
PCI0_IO ....base f2100000, size   1MB
INTER_REGS ....base f1000000, size   1MB
DEVICE_CS0 ....base fa000000, size   2MB
DEVICE_CS1 ....base f8000000, size  32MB
DEVICE_CS2 ....base fa800000, size   1MB
DEV_BOOCS ....base ffc00000, size   4MB
Marvell USB EHCI Host controller #0: c0bf3e00
PCI: bus0: Fast back to back transfers enabled
PCI: bus1: Fast back to back transfers enabled
SCSI subsystem initialized
use IDMA acceleration in copy to/from user buffers. used channels 2 and 3
Done.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver $Revision: 1.3 $ 2 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 3) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Marvell Gigabit Ethernet Driver 'egiga':
  o Ethernet descriptors in DRAM
  o DRAM SW cache-coherency
  o Checksum offload enabled
  o Loading network interface 'egiga0' as eth0
  o Radom MAC address 00:8a:b4:08:11:a0

libata version 1.20 loaded.
sata_sil 0000:01:07.0: version 0.9
drivers/scsi/sata_sil.c (124) Delay 20 seconds to wait for disk ready.
sata_sil 0000:01:07.0: Applying R_ERR on DMA activate FIS errata fix
ata1: SATA max UDMA/100 cmd 0xC8800080 ctl 0xC880008A bmdma 0xC8800000 irq 36
ata2: SATA max UDMA/100 cmd 0xC88000C0 ctl 0xC88000CA bmdma 0xC8800008 irq 36
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023 88:207f
ata1: dev 0 ATA-7, max UDMA/133, 976773168 sectors: LBA48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
  Vendor: ATA       Model: ST3500830AS       Rev: 3.AA
  Type:   Direct-Access                      ANSI SCSI revision: 05
drivers/scsi/sd.c (1707) Internal disk with bus id: 0
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi disk sda
physmap flash device: 400000 at ffc00000
DS406-0: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
DS406-0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Searching for RedBoot partition table in DS406-0 at offset 0x3b0000
6 RedBoot partitions found on MTD device DS406-0
DS406 flash bank 0: Using RedBoot partition definition
Creating 6 MTD partitions on "DS406-0":
0x003c0000-0x00400000 : "RedBoot"
0x00000000-0x00200000 : "zImage"
0x00200000-0x00380000 : "rd.gz"
0x00380000-0x00390000 : "vendor"
eth0: mac address changed
Mac1: 00:11:32:01:a3:6c
vender Mac1 checksum error ucSum:0x00 Buf:0x00 Sum:0.
Vender partition MacNum:1 retlen:64
Serial Number: 75DDN00500
0x00390000-0x003b0000 : "RedBoot Config"
0x003b0000-0x003c0000 : "FIS directory"
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1     29 MB/s
raid6: int32x2     45 MB/s
raid6: int32x4     51 MB/s
raid6: int32x8     48 MB/s
raid6: using algorithm int32x4 (51 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :   429.200 MB/sec
   8regs     :   369.200 MB/sec
   32regs    :   513.600 MB/sec
raid5: using function: 32regs (513.600 MB/sec)
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
ds107+_synobios: module license 'Synology Inc.' taints kernel.
synobios: load, major number 201
Brand: Synology
Model: DS-107+
synobios: unload
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning (device sda3): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device sda3): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sda3, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning (device sda3): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device sda3): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Trying to move old root to /initrd ... okay
Freeing init memory: 108K
Adding 393584k swap on /dev/hda2.  Priority:-1 extents:1 across:393584k
NET: Registered protocol family 5
NTFS driver 2.1.27 [Flags: R/O DEBUG MODULE].
sd 0:0:0:0: Attached scsi generic sg0 type 0
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usbcore: registered new driver snd-usb-audio
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
synobios: load, major number 201
Brand: Synology
Model: DS-107+
eth0: link down
eth0: link up<5>, full duplex<5>, speed 100 Mbps<5>
kjournald starting.  Commit interval 5 seconds
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with writeback data mode.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sda3, internal journal
ehci_platform ehci_platform.4523: (Synology) 88F518x EHCI Host Controller
ehci_platform ehci_platform.4523: new USB bus registered, assigned bus number 1
ehci_platform ehci_platform.4523: irq 17, io mem 0x00000000
ehci_platform ehci_platform.4523: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
usb 1-1: new high speed USB device using ehci_platform and address 2
Got empty serial number. Generate serial number from product.
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
USB Universal Host Controller Interface driver v2.3
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver

Output tail -100 /var/log/messages

Code: [Selecteer]

DiskStation> tail -100 /var/log/messages
Apr 21 14:06:47 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Apr 21 14:06:47 kernel: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Apr 21 14:06:47 kernel: Marvell Gigabit Ethernet Driver 'egiga':
Apr 21 14:06:47 kernel:   o Ethernet descriptors in DRAM
Apr 21 14:06:47 kernel:   o DRAM SW cache-coherency
Apr 21 14:06:47 kernel:   o Checksum offload enabled
Apr 21 14:06:47 kernel:   o Loading network interface 'egiga0' as eth0
Apr 21 14:06:47 kernel:   o Radom MAC address 00:ec:62:7c:55:81
Apr 21 14:06:47 kernel:
Apr 21 14:06:47 kernel: drivers/scsi/sata_sil.c (124) Delay 20 seconds to wait for disk ready.
Apr 21 14:06:47 kernel: drivers/scsi/sd.c (1707) Internal disk with bus id: 0
Apr 21 14:06:47 kernel:  Amd/Fujitsu Extended Query Table at 0x0040
Apr 21 14:06:47 kernel: DS406-0: Swapping erase regions for broken CFI table.
Apr 21 14:06:47 kernel: Mac1: 00:11:32:01:a3:6c
Apr 21 14:06:47 kernel: vender Mac1 checksum error ucSum:0x00 Buf:0x00 Sum:0.
Apr 21 14:06:47 kernel: Vender partition MacNum:1 retlen:64
Apr 21 14:06:47 kernel: Serial Number: 75DDN00500
Apr 21 14:06:47 kernel: raid6: int32x1     29 MB/s
Apr 21 14:06:47 kernel: raid6: int32x2     45 MB/s
Apr 21 14:06:47 kernel: raid6: int32x4     51 MB/s
Apr 21 14:06:47 kernel: raid6: int32x8     48 MB/s
Apr 21 14:06:47 kernel: raid6: using algorithm int32x4 (51 MB/s)
Apr 21 14:06:47 kernel:    arm4regs  :   429.200 MB/sec
Apr 21 14:06:47 kernel:    8regs     :   369.200 MB/sec
Apr 21 14:06:47 kernel:    32regs    :   513.600 MB/sec
Apr 21 14:06:47 kernel: raid5: using function: 32regs (513.600 MB/sec)
Apr 21 14:06:47 kernel: IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
Apr 21 14:06:47 kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Apr 21 14:06:47 kernel: TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
Apr 21 14:06:47 kernel: VFS: Mounted root (ext2 filesystem).
Apr 21 14:06:47 kernel: ds107+_synobios: module license 'Synology Inc.' taints kernel.
Apr 21 14:06:47 kernel: Brand: Synology
Apr 21 14:06:47 kernel: Model: DS-107+
Apr 21 14:06:47 kernel: synobios: unload
Apr 21 14:06:47 kernel: EXT3-fs warning (device sda3): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Apr 21 14:06:47 kernel: EXT3-fs warning (device sda3): ext3_clear_journal_err: Marking fs in need of filesystem check.
Apr 21 14:06:47 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 21 14:06:47 kernel: EXT3-fs warning (device sda3): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Apr 21 14:06:47 kernel: EXT3-fs warning (device sda3): ext3_clear_journal_err: Marking fs in need of filesystem check.
Apr 21 14:06:47 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 21 14:06:47 kernel: VFS: Mounted root (ext3 filesystem).
Apr 21 14:06:47 kernel: Brand: Synology
Apr 21 14:06:47 kernel: Model: DS-107+
Apr 21 14:06:48 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 21 14:08:26 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 21 14:08:33 synousbdisk: RCClean succeeded
Apr 21 14:08:42 kernel: Got empty serial number. Generate serial number from product.
Apr 21 14:09:38 synoindexd: pgsql.c (133) Failed to re-connect to (null), user: admin, db:mediaserver. (could not connect to server: No such file or directory ^IIs the server running locally and accepting ^Iconnections on Unix domain socket "/tmp/.s.PGSQL.5432"? )
Apr 21 14:09:38 synoindexd: database.c (76) Failed to connect to database
Apr 21 14:09:38 synoindexd: database.c (1071) Failed to exec [VACUUM FULL ANALYZE].
Apr 21 14:09:38 synoindexd: synoindexd.c (353) vaccuum mediaserver failed.
Apr 21 14:09:38 synoindexd: pgsql.c (133) Failed to re-connect to (null), user: admin, db:photo. (could not connect to server: No such file or directory ^IIs the server running locally and accepting ^Iconnections on Unix domain socket "/tmp/.s.PGSQL.5432"? )
Apr 21 14:09:38 synoindexd: database.c (120) Failed to connect to database
Apr 21 14:09:38 synoindexd: database.c (1090) Failed to exec [VACUUM FULL ANALYZE].
Apr 21 14:09:38 synoindexd: synoindexd.c (356) vaccuum photodb failed.
Apr 21 14:09:41 synorcd: hw_raytac.c (126) failed to open /dev/usb/hiddev5 (No such device).
Apr 21 14:10:19 afpd[2272]: DiskStation:AFPServer@* started on 65280.86:128 (2.0.1)
Apr 21 14:11:31 kernel: EXT3-fs error (device sda3): ext3_new_block: Allocating block in system zone - block = 113901577
Apr 21 14:11:31 kernel: Aborting journal on device sda3.
Apr 21 14:11:31 kernel: EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
Apr 21 14:11:31 kernel: ext3_abort called.
Apr 21 14:11:31 kernel: EXT3-fs error (device sda3): ext3_journal_start_sb: Detected aborted journal
Apr 21 14:11:31 kernel: Remounting filesystem read-only
Apr 21 14:18:26 findhostd: si_pid=[2773], process=[/bin/sh]
Apr 21 14:18:26 findhostd: si_ppid=[2772], process=[sh]
Apr 21 14:18:26 findhostd: findhostd.c:51(FHOSTDExit) exit on signal[10]
Apr 21 14:18:26 root: /usr/syno/etc/rc.d/S98findhostd.sh stop findhostd
Apr 21 14:18:28 rsyncd[2069]: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(163)
Apr 21 14:18:29 kernel: fs/dquot.c (458) Read only filesystem. Just skip quota sync.
Apr 21 14:18:29 kernel: fs/dquot.c (458) Read only filesystem. Just skip quota sync.
Apr 21 14:19:15 kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Apr 21 14:19:15 kernel: TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
Apr 21 14:19:15 kernel: VFS: Mounted root (ext2 filesystem).
Apr 21 14:19:15 kernel: ds107+_synobios: module license 'Synology Inc.' taints kernel.
Apr 21 14:19:15 kernel: Brand: Synology
Apr 21 14:19:15 kernel: Model: DS-107+
Apr 21 14:19:15 kernel: synobios: unload
Apr 21 14:19:15 kernel: EXT3-fs warning (device sda3): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Apr 21 14:19:15 kernel: EXT3-fs warning (device sda3): ext3_clear_journal_err: Marking fs in need of filesystem check.
Apr 21 14:19:15 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 21 14:19:15 kernel: EXT3-fs warning (device sda3): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Apr 21 14:19:15 kernel: EXT3-fs warning (device sda3): ext3_clear_journal_err: Marking fs in need of filesystem check.
Apr 21 14:19:15 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 21 14:19:15 kernel: VFS: Mounted root (ext3 filesystem).
Apr 21 14:19:15 kernel: Brand: Synology
Apr 21 14:19:15 kernel: Model: DS-107+
Apr 21 14:19:16 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 21 14:20:53 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 21 14:21:00 synousbdisk: RCClean succeeded
Apr 21 14:21:09 kernel: Got empty serial number. Generate serial number from product.
Apr 21 14:22:05 synoindexd: pgsql.c (133) Failed to re-connect to (null), user: admin, db:mediaserver. (could not connect to server: No such file or directory ^IIs the server running locally and accepting ^Iconnections on Unix domain socket "/tmp/.s.PGSQL.5432"? )
Apr 21 14:22:05 synoindexd: database.c (76) Failed to connect to database
Apr 21 14:22:05 synoindexd: database.c (1071) Failed to exec [VACUUM FULL ANALYZE].
Apr 21 14:22:05 synoindexd: synoindexd.c (353) vaccuum mediaserver failed.
Apr 21 14:22:05 synoindexd: pgsql.c (133) Failed to re-connect to (null), user: admin, db:photo. (could not connect to server: No such file or directory ^IIs the server running locally and accepting ^Iconnections on Unix domain socket "/tmp/.s.PGSQL.5432"? )
Apr 21 14:22:05 synoindexd: database.c (120) Failed to connect to database
Apr 21 14:22:05 synoindexd: database.c (1090) Failed to exec [VACUUM FULL ANALYZE].
Apr 21 14:22:05 synoindexd: synoindexd.c (356) vaccuum photodb failed.
Apr 21 14:22:08 synorcd: hw_raytac.c (126) failed to open /dev/usb/hiddev5 (No such device).
Apr 21 14:22:46 afpd[2272]: DiskStation:AFPServer@* started on 65280.208:128 (2.0.1)
DiskStation>


[xburchartz]

Even een update zodat anderen er ook iets aan hebben:

Nadat ik bovenstaande vraag op het engelse forum heb geplaatst, werd me verzocht contact op te nemen met support.

Zij gaven aan dat ik een fsck.ext3 moest uitvoeren op /dev/hda3

Dit lukte eerst niet, want na een umount -f /dev/hda3 bleef ik onderstaande foutmelding krijgen als ik fchk.ext3 -pfv /dev/hda3 wilde uitvoeren:

fsck.ext3: Device or resource busy while trying to open /dev/hda3
Filesystem mounted or opened exclusively by another program?

Als reactie werd gesteld dat ik het volgende moest uitvoeren:

Code: [Selecteer]

# /usr/syno/etc/rc.d/S80samba.sh stop
# /usr/syno/etc/rc.d/S25download.sh stop
# /usr/syno/etc/rc.d/S20pgsql.sh stop
# umount -f /dev/hda3  
# fsck.ext3 -pfv /dev/hda3

In mijn geval lukte het toen nog niet helemaal, waarschijnlijk omdat ik ook nfs had draaien. Ik heb daar dus nog aan toegevoegd:

Code: [Selecteer]

# /usr/syno/etc/rc.d/S83nfsd.sh stop
Vanaf dat moment kon ik de schijf checken en de fouten herstellen. Probleem dus weer opgelost

[marck8000]

Hallo,

Ik had ook het vermoeden dat m'n filesysteem corrupt was geraakt. Omdat een filesysteem niet (goed) gecontroleerd kan worden als het gebruikt wordt (dwz. als de Synology draait), heb ik een andere methode gebruikt: ik heb de harddisk van m'n DS107+ aan m'n PC gehangen en via Ubuntu op fouten gecontroleerd (en fouten gevonden en opgelost).

Hieronder is een gedetailleerde beschrijving (sorry, in het Engels):

- Remove all cables of Synology
- Open the Synology (see manual)
- Disconnect SATA cable
- Power down PC and open it
- Connect the Synology HDD to a spare SATA slot in your PC using a SATA cable (I bought one)
- Connect the power cable of the Synology
- Power on the Synology (press power button)
- Power on the PC and boot to Ubuntu (if you don't have Ubuntu, I guess the live cd of Ubuntu will also work)
- In Ubuntu's terminal, check which partitions are from the Synology

Code: [Selecteer]

  sudo fdisk -l
- Check the Synology partitions (excl. the swap partition)

Code: [Selecteer]

  sudo fsck.ext3 -pfv /dev/sdc1     (-p = auto repair)
   sudo fsck.ext3 -pfv /dev/sdc3     (-p = auto repair)

- now all problems should be fixed
- power down the PC
- power down the Synology (power button)
- remove cables
- reconnect the SATA cable of the Synology again
- put the Synology back together and reconnect the cables
[/list]

Ik hoop dat dit nog mensen kan helpen.


Groeten,

Marc