Disk crashed

Smeat · 22. Okt 2011

Moin!

Ich habe das Problem, dass meine DS mir ständig meldet, meine Festplatte wäre abgestürzt.
Sie ist sogar noch im rw Modus eingehängt, da der Remount scheitert.
Im DSM steht unter Status "Crashed" und unter Suggestion:

"Unable to use this volume. The data in the volume may be crashed. Please try to back up the data before removing the volume. When you remove hard disks, please note that at least one system disk [Disk 1] should be kept for the system to function normally."

Es handelt sich hierbei um eine einzige Festplatte in einer DS209.
Hier meine /var/log/messages:

Rich (BBCode):

Oct 22 20:47:00 syslogd started: BusyBox v1.16.1
Oct 22 20:47:00 kernel: [    0.400000] Warning PCI-E is Powered Off
Oct 22 20:47:00 kernel: [    0.410000] bio: create slab <bio-0> at 0
Oct 22 20:47:00 kernel: [    0.580000] raid6: int32x1     97 MB/s
Oct 22 20:47:00 kernel: [    0.750000] raid6: int32x2    111 MB/s
Oct 22 20:47:00 kernel: [    0.920000] raid6: int32x4    124 MB/s
Oct 22 20:47:00 kernel: [    1.090000] raid6: int32x8    108 MB/s
Oct 22 20:47:00 kernel: [    1.090000] raid6: using algorithm int32x4 (124 MB/s)
Oct 22 20:47:00 kernel: [    1.100000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Oct 22 20:47:00 kernel: [    1.170000] Delay 10 seconds to wait for disk 1 ready.
Oct 22 20:47:00 kernel: [   13.210000] SPI Serial flash detected @ 0xf8000000, 4096KB (64sec x 64KB)
Oct 22 20:47:00 kernel: [   13.270000] vender Mac1 checksum error ucSum:0x00 Buf:0x00 Sum:0.
Oct 22 20:47:00 kernel: [   13.270000] Serial Number: 94F6N02533
Oct 22 20:47:00 kernel: [   13.290000] Loading Marvell Ethernet Driver:
Oct 22 20:47:00 kernel: [   13.290000]   o Cached descriptors in DRAM
Oct 22 20:47:00 kernel: [   13.300000]   o DRAM SW cache-coherency
Oct 22 20:47:00 kernel: [   13.300000]   o 2 Giga ports supported
Oct 22 20:47:00 kernel: [   13.310000]   o Single RX Queue support - ETH_DEF_RXQ=0
Oct 22 20:47:00 kernel: [   13.310000]   o Single TX Queue support - ETH_DEF_TXQ=0
Oct 22 20:47:00 kernel: [   13.320000]   o TCP segmentation offload (TSO) supported
Oct 22 20:47:00 kernel: [   13.320000]   o Receive checksum offload supported
Oct 22 20:47:00 kernel: [   13.330000]   o Transmit checksum offload supported
Oct 22 20:47:00 kernel: [   13.330000]   o Rx descripors: q0=128
Oct 22 20:47:00 kernel: [   13.340000]   o Tx descripors: q0=532
Oct 22 20:47:00 kernel: [   13.340000]   o Loading network interface(s):
Oct 22 20:47:00 kernel: [   13.350000]     o  register under mv88fx_eth platform
Oct 22 20:47:00 kernel: [   13.350000]     o eth0, ifindex = 2, GbE port = 0
Oct 22 20:47:00 kernel: [   13.360000]     o eth0, phy chipid = 1410e40, Support WOL = 0
Oct 22 20:47:00 kernel: [   13.360000] 
Oct 22 20:47:00 kernel: [   13.500000] md: sda2 has different UUID to sda1
Oct 22 20:47:00 kernel: [   13.510000] md: md0: set sda1 to auto_remap [0]
Oct 22 20:47:00 kernel: [   13.540000] md: md1: set sda2 to auto_remap [0]
Oct 22 20:47:00 kernel: [   13.740000] VFS: Mounted root (ext2 filesystem) on device 1:0.
Oct 22 20:47:00 kernel: [   13.760000] ds209_synobios: module license 'Synology Inc.' taints kernel.
Oct 22 20:47:00 kernel: [   13.770000] Disabling lock debugging due to kernel taint
Oct 22 20:47:00 kernel: [   13.850000] Brand: Synology
Oct 22 20:47:00 kernel: [   13.850000] Model: DS-209
Oct 22 20:47:00 kernel: [   13.870000] synobios: unload
Oct 22 20:47:00 kernel: [   20.770000] VFS: Mounted root (ext3 filesystem) on device 9:0.
Oct 22 20:47:00 kernel: [   21.900000] cesadev_init(bf126000)
Oct 22 20:47:00 kernel: [   21.940000] mvCesaInit: sessions=10240, queue=64, pSram=f0000000
Oct 22 20:47:00 kernel: [   22.070000] encryptfs using the OCF package.
Oct 22 20:47:00 kernel: [   22.740000] Brand: Synology
Oct 22 20:47:00 kernel: [   22.750000] Model: DS-209
Oct 22 20:47:00 kernel: [   25.600000] md: md2: set sda3 to auto_remap [0]
Oct 22 20:47:11 scemd: scemd.c:118 fan_type=7, raid_type=1, led_type=1, thermal_type=1, fanctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=1, fan_number=1, ebox_type=1, pis_type=1, rtc_type=1
Oct 22 20:47:11 scemd: modules/fan_speed_adjust_common.c:161 Type: INTERNAL Fan Mode: HIGH (suitable for 3.5'' HD)
Oct 22 20:47:12 scemd: modules/raid_sys_volume_check.c:160 MD0 active disks 1, designed disks 2 
Oct 22 20:47:12 scemd: modules/raid_sys_volume_check.c:160 MD1 active disks 1, designed disks 2 
Oct 22 20:47:12 scemd: modules/disk_hibernation.c:94 Force hibernation enable, idle minutes 60
Oct 22 20:47:12 synoprint: printer_device_open.c:16 bad parameter.
Oct 22 20:47:14 synocheckshare: synocheckshare.c:658 Failed to enable PGSQL [0x8300] 
Oct 22 20:47:14 synousbdisk: RCClean succeeded
Oct 22 20:47:15 inetd[1465]: sane-port/tcp: unknown service
Oct 22 20:47:15 ddnsd: main(ddnsd.c:2692):  not enable DDNS, shutdown daemon
Oct 22 20:47:16 synoindexd: pgsql.c (133) Failed to re-connect to (null), user: admin, db:mediaserver. (could not connect to server: No such file or directory  Is the server running locally and accepting     connections on Unix domain socket "/tmp/.s.PGS
Oct 22 20:47:16 synoindexd: database.c (106) Failed to connect to database
Oct 22 20:47:16 synoindexd: database.c (1615) Failed to exec [VACUUM FULL ANALYZE].
Oct 22 20:47:16 synoindexd: synoindexd.c (460) vaccuum mediaserver failed.
Oct 22 20:47:16 synoindexd: pgsql.c (133) Failed to re-connect to (null), user: admin, db:photo. (could not connect to server: No such file or directory        Is the server running locally and accepting     connections on Unix domain socket "/tmp/.s.PGSQL.543
Oct 22 20:47:16 synoindexd: database.c (189) Failed to connect to database
Oct 22 20:47:16 synoindexd: database.c (1634) Failed to exec [VACUUM FULL ANALYZE].
Oct 22 20:47:16 synoindexd: synoindexd.c (463) vaccuum photodb failed.
Oct 22 20:47:20 kernel: [   45.660000] Got empty serial number. Generate serial number from product.
Oct 22 20:47:21 xinetd[1970]: Protocol udp4 not in /etc/protocols [file=/opt/etc/xinetd.d/tftp] [line=8]
Oct 22 20:47:21 xinetd[1970]: Error parsing attribute protocol - DISABLING SERVICE [file=/opt/etc/xinetd.d/tftp] [line=8]
Oct 22 20:47:22 sshd[2066]: error: Bind to port 22 on :: failed: Address already in use.
Oct 22 20:47:22 sshd[2066]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Oct 22 20:47:22 sshd[2066]: fatal: Cannot bind any address.
Oct 22 20:47:24 syno_hdd_util: Model:[WD15EADS-00S2B0], Firmware:[04.05G04], S/N:[WD-WCAVY0412243] in [/dev/sda] is not ssd
Oct 22 20:47:24 rsyncd[2011]: rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(585) [receiver=3.0.4]
Oct 22 20:47:31 scemd: ScemRefreshDiskLed(528)Disk 1 fail
Oct 22 20:47:31 scemd: modules/raid_data_volume_check.c:882 Volume /volume1 crashed, mount it read-only
Oct 22 20:47:38 scemd: volume_remount.c:40 Failed to remount '/volume1' to 'ro', WEXITSTATUS(err) = 255, err = 65280
Oct 22 20:47:38 scemd: volume_crashed_handler.c:43 Failed to remount '/volume1' to read-only
Oct 22 20:47:40 synoindexd: pgsql.c (133) Failed to re-connect to (null), user: admin, db:mediaserver. (could not connect to server: No such file or directory  Is the server running locally and accepting     connections on Unix domain socket "/tmp/.s.PGS
Oct 22 20:47:40 synoindexd: database.c (106) Failed to connect to database
Oct 22 20:47:40 synoindexd: database.c (1615) Failed to exec [VACUUM FULL ANALYZE].
Oct 22 20:47:40 synoindexd: synoindexd.c (460) vaccuum mediaserver failed.
Oct 22 20:47:40 synoindexd: pgsql.c (133) Failed to re-connect to (null), user: admin, db:photo. (could not connect to server: No such file or directory        Is the server running locally and accepting     connections on Unix domain socket "/tmp/.s.PGSQL.543
Oct 22 20:47:40 synoindexd: database.c (189) Failed to connect to database
Oct 22 20:47:40 synoindexd: database.c (1634) Failed to exec [VACUUM FULL ANALYZE].
Oct 22 20:47:40 synoindexd: synoindexd.c (463) vaccuum photodb failed.
Oct 22 20:47:43 scemd: modules/raid_data_volume_check.c:955 /volume1 state changes from 0 to 3.

Den erweiteren S.M.A.R.T-Test besteht die Platte auch.
e2fsck habe ich auch schon ausgeführt. Beim ersten Durchlauf wurden auch einige Fehler korrigiert.
Jetzt ergibt ein e2fsck folgendes:

Rich (BBCode):

DS> e2fsck -v -f -y -C0 /dev/md2
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure                                           
Pass 3: Checking directory connectivity                                        
Pass 4: Checking reference counts                                              
Pass 5: Checking group summary information                                     
                                                                               
  176756 inodes used (0.19%)
   39270 non-contiguous files (22.2%)
     138 non-contiguous directories (0.1%)
         # of inodes with ind/dind/tind blocks: 40798/6450/79
347943128 blocks used (95.20%)
       0 bad blocks
     119 large files

  153133 regular files
   17345 directories
      13 character device files
      27 block device files
      18 fifos
     876 links
    6208 symbolic links (5414 fast symbolic links)
       3 sockets
--------
  177623 files

Gibt es vielleicht irgendwo noch Logfiles vom scemd? Diese Meldungen sind ja eher minimal.
Kann man also irgendwo nachsehen, warum die Festplatte als abgestürzt angezeigt wird?
Weiß sonst jemand Rat? Ich würde die Festplatte ungern formatieren.
Vielen dank für alle Antworten

mfg Kevin

amarthius · 23. Okt 2011

Was hindert dich daran eine neue zu beschaffen, diese einzubauen und das Backup aufzuspielen?

Smeat · 23. Okt 2011

Ja klar, das könnte ich auch machen. Aber ist das wirklich eine Lösung?
Dann weiß ich immer noch nicht, warum die Festplatte als "Crashed" angezeigt wird. Das muss ja einen Grund haben.
Irgendwie muss man doch feststellen können, oder nicht?
Ein Dateisystemcheck läuft, wie gesagt, durch und der S.M.A.R.T.-Test wird auch bestanden.
Kann es sein, das irgendwo so etwas, wie ein "Crashed" Flag gesetzt wird, dass man nach einem Fehler deaktivieren muss? (e2fsck hat ja Fehler gefunden und beseitigt)
Ich bin da mehr oder weniger ratlos, da die Festplatte ja ohne Einschränkungen funktioniert.

mfg Kevin

Suche

Disk crashed

Smeat

Benutzer

amarthius

Super-Moderator

Smeat

Benutzer

Kaffeautomat