Hallo,
nach bisher Problemlosen Betrieb hat es mich jetzt wohl erwischt...
Das System (TS-419P+, 3.7.1, HDD: 2 TB Seagate ST2000DL004 (sda) und Samsung HD204UI (sdb) im RAID 1) ist gestern nicht sauber heruntergefahren ist (ca. 20min "shuting down" bevor ich über den Power-Schalter ausgeschaltet habe) habe ich keinen Zugriff mehr auf die Daten auf /dev/md0.
Außerdem ist auch kein Zugriff mehr auf die Konfiguratinonsoberfläche mehr möglich - das System hat die Quickkonfiguration gestartet
und veschickt folgende Warnung
Server Name: NAS-TS-419P IP Address: 192.168.1.10 Date/Time: 2012/08/04 10:53:06 Level: Warning Folders(Public, Usb, Web, Multimedia) for default network shares do not exist. Restore default network shares or format your disk volume.
Der Zugriff mit PuTTY auf 192.168.1.10 funktioniert jedoch noch.
dmesg:
[~] # dmesgrom 0 to 542769152[ 47.490000] md9: unknown partition table[ 49.830000] kjournald starting. Commit interval 5 seconds[ 49.840000] EXT3-fs (md9): using internal journal[ 49.840000] EXT3-fs (md9): mounted filesystem with writeback data mode[ 50.070000] md: md13 stopped.[ 50.110000] md: bind<sdb4>[ 50.110000] md: bind<sda4>[ 50.110000] raid1: raid set md13 active with 2 out of 4 mirrors[ 50.140000] md13: bitmap initialized from disk: read 4/4 pages, set 94209 bits[ 50.140000] created bitmap (57 pages) for device md13[ 50.180000] md13: detected capacity change from 0 to 469893120[ 50.190000] md13: unknown partition table[ 51.560000] kjournald starting. Commit interval 5 seconds[ 51.610000] EXT3-fs (md9): using internal journal[ 51.610000] EXT3-fs (md9): mounted filesystem with writeback data mode[ 51.890000] kjournald starting. Commit interval 5 seconds[ 51.900000] EXT3-fs (md9): using internal journal[ 51.900000] EXT3-fs (md9): mounted filesystem with writeback data mode[ 51.980000] kjournald starting. Commit interval 5 seconds[ 51.980000] EXT3-fs (md13): warning: mounting fs with errors, running e2fsck is recommended[ 52.140000] EXT3-fs (md13): using internal journal[ 52.140000] EXT3-fs (md13): mounted filesystem with writeback data mode[ 56.850000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 56.900000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 56.900000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 57.170000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 57.340000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 57.360000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 57.560000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 57.720000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 57.870000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 58.250000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 60.590000] xor: measuring software checksum speed[ 60.640000] arm4regs : 1428.800 MB/sec[ 60.690000] 8regs : 1096.800 MB/sec[ 60.740000] 32regs : 1230.400 MB/sec[ 60.740000] xor: using function: arm4regs (1428.800 MB/sec)[ 60.920000] raid6: int32x1 112 MB/s[ 61.090000] raid6: int32x2 155 MB/s[ 61.260000] raid6: int32x4 162 MB/s[ 61.430000] raid6: int32x8 151 MB/s[ 61.430000] raid6: using algorithm int32x4 (162 MB/s)[ 61.510000] md: raid6 personality registered for level 6[ 61.510000] md: raid5 personality registered for level 5[ 61.510000] md: raid4 personality registered for level 4[ 61.550000] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com[ 61.640000] cryptodev: driver 0.9 loaded.[ 62.010000] generic-usb 0003:051D:0002.0001: claimed by neither input, hiddev nor hidraw[ 62.010000] usbcore: registered new interface driver usbhid[ 62.010000] usbhid: USB HID core driver[ 62.030000] usbcore: registered new interface driver usblp[ 62.040000] sysinfo: Module loaded.[ 62.140000] fnotify: module license 'non-GPL' taints kernel.[ 62.140000] Disabling lock debugging due to kernel taint[ 62.150000] fnotify: Load file notify kernel module.[ 62.160000] fnotify: Global_Private_Data_List_Init()[ 62.160000] fnotify: Launch the fnotify thread: 1051[ 62.160000] fnotify: The fnotify thread starts...[ 62.200000] Enable WDT...[ 63.930000] eth0: mac address changed[ 63.960000] eth0: link down[ 63.960000] eth0: started[ 64.000000] eth1: mac address changed[ 64.020000] eth1: started[ 65.270000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended[ 66.990000] eth0: link up, full duplex, speed 1 Gbps[ 68.230000] kjournald starting. Commit interval 5 seconds[ 68.240000] EXT3-fs (md9): using internal journal[ 68.240000] EXT3-fs (md9): mounted filesystem with writeback data mode[ 70.090000] active port 0 :139[ 70.090000] active port 1 :445[ 70.090000] active port 2 :20[ 72.210000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended[ 75.920000] md: bind<sda2>[ 75.920000] raid1: raid set md4 active with 1 out of 1 mirrors[ 75.920000] md4: detected capacity change from 0 to 542769152[ 76.930000] md4: unknown partition table[ 79.030000] Adding 530040k swap on /dev/md4. Priority:-1 extents:1 across:530040k[ 84.880000] EXT4-fs (sda3): mounted filesystem with ordered data mode[ 86.200000] md: bind<sdb2>[ 86.220000] RAID1 conf printout:[ 86.220000] --- wd:1 rd:2[ 86.220000] disk 0, wo:0, o:1, dev:sda2[ 86.220000] disk 1, wo:1, o:1, dev:sdb2[ 86.230000] md: recovery of RAID array md4[ 86.230000] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.[ 86.230000] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.[ 86.230000] md: using 128k window, over a total of 530048 blocks.[ 89.970000] EXT4-fs (sdb3): mounted filesystem with ordered data mode[ 96.490000] md: md4: recovery done.[ 96.520000] RAID1 conf printout:[ 96.520000] --- wd:2 rd:2[ 96.520000] disk 0, wo:0, o:1, dev:sda2[ 96.520000] disk 1, wo:0, o:1, dev:sdb2[ 103.160000] eth0: stopped[ 103.160000] eth1: stopped[ 104.730000] eth0: link down[ 104.730000] eth0: started[ 104.850000] eth1: started[ 108.030000] eth0: link up, full duplex, speed 1 Gbps[ 121.490000] eth0: stopped[ 121.510000] eth0: link down[ 121.510000] eth0: started[ 121.580000] eth1: stopped[ 121.600000] eth1: started[ 123.790000] active port 0 :139[ 123.790000] active port 1 :445[ 123.790000] active port 2 :20[ 124.550000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 124.700000] eth0: link up, full duplex, speed 1 Gbps[ 127.780000] EXT3-fs error (device md13): ext3_add_entry: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=3889967107, rec_len=0, name_len=83[ 131.430000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended[ 141.600000] rule type=2, num=0[ 141.900000] MAC:00:08:9B:C2:DD:1B[ 141.910000] eth0: link down[ 141.910000] page 3, reg 18 = 4a85[ 141.910000] eth0: link up, full duplex, speed 1 Gbps[ 141.910000] WOL enable[ 141.940000] MAC:00:08:9B:C2:DD:1C[ 141.940000] page 3, reg 18 = 4a85[ 141.940000] WOL enable[ 141.970000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended[ 145.410000] Loading iSCSI transport class v2.0-871.[ 145.860000] iscsi: registered transport (tcp)
fdisk -l
[~] # fdisk -lDisk /dev/sda: 2000.3 GB, 2000398934016 bytes255 heads, 63 sectors/track, 243201 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/sda1 1 66 530125 83 Linux/dev/sda2 67 132 530142 83 Linux/dev/sda3 133 243138 1951945693 83 Linux/dev/sda4 243139 243200 498012 83 LinuxDisk /dev/sda4: 469 MB, 469893120 bytes2 heads, 4 sectors/track, 114720 cylindersUnits = cylinders of 8 * 512 = 4096 bytesDisk /dev/sda4 doesn't contain a valid partition tableDisk /dev/sdb: 2000.3 GB, 2000398934016 bytes255 heads, 63 sectors/track, 243201 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/sdb1 1 66 530125 83 Linux/dev/sdb2 67 132 530142 83 Linux/dev/sdb3 133 243138 1951945693 83 Linux/dev/sdb4 243139 243200 498012 83 LinuxDisk /dev/md9: 542 MB, 542769152 bytes2 heads, 4 sectors/track, 132512 cylindersUnits = cylinders of 8 * 512 = 4096 bytesDisk /dev/md9 doesn't contain a valid partition tableDisk /dev/md4: 542 MB, 542769152 bytes2 heads, 4 sectors/track, 132512 cylindersUnits = cylinders of 8 * 512 = 4096 bytesDisk /dev/md4 doesn't contain a valid partition table
mdadm --examine /dev/sda3
/dev/sda3: Magic : a92b4efc Version : 00.90.00 UUID : 23b751bf:a01ecccc:dbc9f540:476b988e Creation Time : Sat Aug 13 13:40:46 2011 Raid Level : raid1 Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB) Array Size : 1951945600 (1861.52 GiB 1998.79 GB) Raid Devices : 2 Total Devices : 2Preferred Minor : 0 Update Time : Fri Aug 3 19:05:47 2012 State : cleanInternal Bitmap : present Active Devices : 2Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : a303b8aa - correct Events : 0.582688 Number Major Minor RaidDevice Statethis 0 8 3 0 active sync /dev/sda3 0 0 8 3 0 active sync /dev/sda3 1 1 8 19 1 active sync /dev/sdb3
mdadm --examine /dev/sdb3
/dev/sdb3: Magic : a92b4efc Version : 00.90.00 UUID : 23b751bf:a01ecccc:dbc9f540:476b988e Creation Time : Sat Aug 13 13:40:46 2011 Raid Level : raid1 Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB) Array Size : 1951945600 (1861.52 GiB 1998.79 GB) Raid Devices : 2 Total Devices : 2Preferred Minor : 0 Update Time : Fri Aug 3 19:05:47 2012 State : cleanInternal Bitmap : present Active Devices : 2Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Checksum : a303b8bc - correct Events : 0.582688 Number Major Minor RaidDevice Statethis 1 8 19 1 active sync /dev/sdb3 0 0 8 3 0 active sync /dev/sda3 1 1 8 19 1 active sync /dev/sdb3
cat /proc/mdstat - hier fehlt md0
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]md4 : active raid1 sdb2[1] sda2[0] 530048 blocks [2/2] [UU]md13 : active raid1 sda4[0] sdb4[1] 458880 blocks [4/2] [UU__] bitmap: 47/57 pages [188KB], 4KB chunkmd9 : active raid1 sda1[0] sdb1[1] 530048 blocks [4/2] [UU__] bitmap: 65/65 pages [260KB], 4KB chunk
So wie es für mich aussieht, gibt es ein Problem mit dem Superblock
[~] # mdadm --assemble /dev/md0 /dev/sda3 /dev/sdb3
mdadm: cannot open device /dev/sda3: Device or resource busy
mdadm: /dev/sda3 has no superblock - assembly aborted
Ich wäre jetzt für Hinweise dankbar, wie ich a) wieder an die Daten komme und b) die ursprüngliche Konfiguration am besten wiederherstellen kann.
Das Backup ist nicht mehr ganz aktuell, daher möchte ich nach Möglichkeit an die Daten vom RAID herankommen...
Holger
P.S. Eine 2 TB Ersatzfestplatte ist auch noch vorhanden