Firmwareupdate, anschließend Raid 5 entladen

    Hallo


    Ich bin nun seit 4 Tagen am versuchen mein Raid wieder zum Laufen zu bekommen!
    Ich bekomme annähernd die selben Meldungen meines Qnap wie in diesem Post:


    http://forum.qnapclub.de/viewtopic.php?f=25&t=36921


    weshalb ich auch vermute das die Config sich zerlegt hat.


    Leider funktioniert bei mir das Mounten in die config aus dem Post nicht, weshalb ich die ulinux nicht wiedeerherstellen kann.


    Zu meinem System:
    QTS 4.2.0
    TS 439 Pro
    4 x 3Tb WD hdd


    Backup der wichtigsten Daten hätte ich, aber da mein Raid ja eigentlich noch da ist würde ich dies auch gerne wieder herstellen

    Ausgabe von fdisk:

    Code
    Disk /dev/sdx: 128 MB, 128057344 bytes8 heads, 32 sectors/track, 977 cylindersUnits = cylinders of 256 * 512 = 131072 bytes   Device Boot      Start         End      Blocks   Id  System/dev/sdx1               1           8        1008   83  Linux/dev/sdx2               9         440       55296   83  Linux/dev/sdx3             441         872       55296   83  Linux/dev/sdx4             873         977       13440    5  Extended/dev/sdx5             873         913        5232   83  Linux/dev/sdx6             914         977        8176   83  LinuxYou must set cylinders.You can do this from the extra functions menu.Disk /dev/sda: 0 MB, 0 bytes255 heads, 63 sectors/track, 0 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes   Device Boot      Start         End      Blocks   Id  System/dev/sda1               1      267350  2147483647+  ee  EFI GPTPartition 1 has different physical/logical beginnings (non-Linux?):     phys=(0, 0, 1) logical=(0, 0, 2)Partition 1 has different physical/logical endings:     phys=(1023, 254, 63) logical=(267349, 89, 4)Disk /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 tableYou must set cylinders.You can do this from the extra functions menu.Disk /dev/sdb: 0 MB, 0 bytes255 heads, 63 sectors/track, 0 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes   Device Boot      Start         End      Blocks   Id  System/dev/sdb1               1      267350  2147483647+  ee  EFI GPTPartition 1 has different physical/logical beginnings (non-Linux?):     phys=(0, 0, 1) logical=(0, 0, 2)Partition 1 has different physical/logical endings:     phys=(1023, 254, 63) logical=(267349, 89, 4)You must set cylinders.You can do this from the extra functions menu.Disk /dev/sdc: 0 MB, 0 bytes255 heads, 63 sectors/track, 0 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes   Device Boot      Start         End      Blocks   Id  System/dev/sdc1               1      267350  2147483647+  ee  EFI GPTPartition 1 has different physical/logical beginnings (non-Linux?):     phys=(0, 0, 1) logical=(0, 0, 2)Partition 1 has different physical/logical endings:     phys=(1023, 254, 63) logical=(267349, 89, 4)You must set cylinders.You can do this from the extra functions menu.Disk /dev/sdd: 0 MB, 0 bytes255 heads, 63 sectors/track, 0 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes   Device Boot      Start         End      Blocks   Id  System/dev/sdd1               1      267350  2147483647+  ee  EFI GPTPartition 1 has different physical/logical beginnings (non-Linux?):     phys=(0, 0, 1) logical=(0, 0, 2)Partition 1 has different physical/logical endings:     phys=(1023, 254, 63) logical=(267349, 89, 4)Disk /dev/sds: 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/sds1               1      243202  1953512448    7  HPFS/NTFSDisk /dev/sdt: 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/sdt1               1      243202  1953512448   83  LinuxDisk /dev/sdv: 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/sdv1               1      243202  1953512448   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, 542851072 bytes2 heads, 4 sectors/track, 132532 cylindersUnits = cylinders of 8 * 512 = 4096 bytesDisk /dev/md4 doesn't contain a valid partition tableDisk /dev/md0: 0 MB, 0 bytes2 heads, 4 sectors/track, 0 cylindersUnits = cylinders of 8 * 512 = 4096 bytesDisk /dev/md0 doesn't contain a valid partition table


    meine uLinux.conf:

    Wenn das wirklich alles von der uLinux.conf ist, dann ist sie wirklich hinüber.
    Die Befehle für die Wiederherstellung:

    Code
    mount -t ext2 /dev/sdx6 /tmp/config
cp /mnt/HDA_ROOT/.config/uLinux.conf /mnt/HDA_ROOT/.config/uLinux.bak
cp /tmp/config/uLinux.conf /mnt/HDA_ROOT/.config/uLinux.conf
umount /tmp/config
reboot

    Danke schon mal


    Das Kopieren der uLinux hat schon mal geklappt.
    Er hängt nun im reboot seit 20 Min., hoffe das klappt noch :)


    na mal schauen, ich melde mich!


    --- ModEdit ---


    In der SSH beim erneuten eingeben von reboot gibt er mir folgendes zurück:

    Code
    reboot: relocation error: reboot: symbol ▒▒▒▒▒▒H▒▒▒                            ▒, version GLIBC_2.0 not defined in file libc.so.6 with link time reference


    In der Grafischen Oberfläche meckert er wegen eines Downgrades, wie soll ich weitermachen?

    Einmal editiert, zuletzt von dr_mike () aus folgendem Grund: Mehrfach-Posts vermeiden, siehe Forenregeln! Bitte den 'Ändern' Button verwenden.

    Der Befehl reboot kann nur einmal ausgeführt werden. Wenn das NAS noch nicht neu gestartet hat und sich auch nichts mehr tut (keinerlei Festplattenaktivitäten), dann das NAS hart abschalten und neu starten.

    Reboot habe ich hart durchgeführt!


    Leider ist mein Raid immer noch entladen :cursing:


    Hoffentlich noch ne idee


    Hier noch die aktuelle uLinux:


    nicht das hier doch noch ein Fehler drin Steckt

    Das ist immernoch keine vollständige uLinux.conf. Diese wäre wesentlich grösser (ca 8 - 10kB).
    Poste bitte mal die Ausgabe von

    Code
    cat /proc/mdstat
cat /proc/mounts
cat /etc/config/mdadm.conf
cat /etc/config/raidtab

    Oh, ok


    also zu mdstat:

    Code
    Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]md0 : active raid5 sda3[0] sdd3[4] sdc3[2] sdb3[1]                 8786092608 blocks super 1.0 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]                 bitmap: 0/11 pages [0KB], 131072KB chunkmd4 : active raid1 sdd2[4](S) sdc2[3](S) sdb2[2] sda2[0]                 530128 blocks super 1.0 [2/2] [UU]md13 : active raid1 sda4[0] sdd4[3] sdc4[2] sdb4[1]                 458880 blocks [4/4] [UUUU]                 bitmap: 1/57 pages [4KB], 4KB chunkmd9 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]                 530048 blocks [4/4] [UUUU]                 bitmap: 0/65 pages [0KB], 4KB chunkunused devices: <none>


    zu mounts:

    Code
    rootfs / rootfs rw 0 0/dev/root / ext2 rw,relatime,errors=continue 0 0/proc /proc proc rw,relatime 0 0none /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0sysfs /sys sysfs rw,relatime 0 0tmpfs /tmp tmpfs rw,relatime,size=65536k 0 0tmpfs /dev/shm tmpfs rw,relatime 0 0none /proc/bus/usb usbfs rw,relatime 0 0/dev/sda4 /mnt/ext ext3 rw,relatime,errors=continue,barrier=1,data=writeback 0 0/dev/md9 /mnt/HDA_ROOT ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0tmpfs /mnt/rf/nd tmpfs rw,relatime,size=1024k 0 0/dev/mapper/sdt1 /share/external/sdt1 ext4 rw,relatime,data=ordered 0 0/dev/sdv1 /share/external/sdv1 ext4 rw,relatime,data=ordered 0 0/dev/sds1 /share/external/sds1 ufsd rw,relatime,nls=utf8,fmask=111,dmask=0,force 0 0


    zu mdadm:

    Code
    ARRAY /dev/md0 devices=/dev/sda3,/dev/sdb3,/dev/sdc3,/dev/sdd3


    zu raidtab:

    Ja des iss ja grad des :cry:


    zu dmesg:

    Code
    MSI/MSI-X[  130.711633] e1000e 0000:01:00.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:08:9b:8c:f6:40[  130.716668] e1000e 0000:01:00.0: eth0: Intel(R) PRO/1000 Network Connection[  130.721117] e1000e 0000:01:00.0: eth0: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF[  130.733062] e1000e 0000:02:00.0: Disabling ASPM L0s L1[  130.737980] e1000e 0000:02:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode[  130.742787] e1000e 0000:02:00.0: irq 47 for MSI/MSI-X[  130.742811] e1000e 0000:02:00.0: irq 48 for MSI/MSI-X[  130.742832] e1000e 0000:02:00.0: irq 49 for MSI/MSI-X[  130.849924] e1000e 0000:02:00.0: eth1: (PCI Express:2.5GT/s:Width x1) 00:08:9b:8c:f6:41[  130.855273] e1000e 0000:02:00.0: eth1: Intel(R) PRO/1000 Network Connection[  130.860145] e1000e 0000:02:00.0: eth1: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF[  130.875957] jnl: driver (lke_9.2.0 QNAP, LBD=ON) loaded at f8836000[  130.886957] ufsd: module license 'Commercial product' taints kernel.[  130.892129] Disabling lock debugging due to kernel taint[  130.901877] ufsd: driver (lke_9.2.0 QNAP, build_host("BuildServer37"), acl, ioctl, bdi, sd2(0), fua, bz, rsrc) loaded at f8933000[  130.901886] NTFS support included[  130.901889] Hfs+/HfsJ support included[  130.901892] optimized: speed[  130.901895] Build_for__QNAP_Atom_x86_k3.4.6_2014-12-15_lke_9.2.0_r245986_b56[  130.901900][  130.982391] fnotify: Load file notify kernel module.[  132.088772] usbcore: registered new interface driver snd-usb-audio[  132.103206] usbcore: registered new interface driver snd-usb-caiaq[  132.121538] Linux video capture interface: v2.00[  132.158587] usbcore: registered new interface driver uvcvideo[  132.164903] USB Video Class driver (1.1.1)[  132.355054] 8021q: 802.1Q VLAN Support v1.8[  145.415779] kjournald starting.  Commit interval 5 seconds[  145.423524] EXT3-fs (md9): using internal journal[  145.428546] EXT3-fs (md9): mounted filesystem with ordered data mode[  151.231624] md: bind<sda2>[  151.240119] md/raid1:md4: active with 1 out of 1 mirrors[  151.246607] md4: detected capacity change from 0 to 542851072[  152.259089]  md4: unknown partition table[  154.379882] Adding 530124k swap on /dev/md4.  Priority:-1 extents:1 across:530124k[  159.405072] md: bind<sdb2>[  159.429604] RAID1 conf printout:[  159.429614]  --- wd:1 rd:2[  159.429624]  disk 0, wo:0, o:1, dev:sda2[  159.429632]  disk 1, wo:1, o:1, dev:sdb2[  159.429800] md: recovery of RAID array md4[  159.435271] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.[  159.440337] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.[  159.445840] md: using 128k window, over a total of 530128k.[  162.030371] md: bind<sdc2>[  164.378876] md: bind<sdd2>[  165.179403] md: md0 stopped.[  165.202390] md: md0 stopped.[  165.282723] md: bind<sdb3>[  165.287873] md: bind<sdc3>[  165.292888] md: bind<sdd3>[  165.297815] md: bind<sda3>[  165.304049] md/raid:md0: device sda3 operational as raid disk 0[  165.308708] md/raid:md0: device sdd3 operational as raid disk 3[  165.313221] md/raid:md0: device sdc3 operational as raid disk 2[  165.317655] md/raid:md0: device sdb3 operational as raid disk 1[  165.340069] md/raid:md0: allocated 67792kB[  165.344554] md/raid:md0: raid level 5 active with 4 out of 4 devices, algorithm 2[  165.348943] RAID conf printout:[  165.348951]  --- level:5 rd:4 wd:4[  165.348960]  disk 0, o:1, dev:sda3[  165.348966]  disk 1, o:1, dev:sdb3[  165.348972]  disk 2, o:1, dev:sdc3[  165.348978]  disk 3, o:1, dev:sdd3[  165.349284] created bitmap (11 pages) for device md0[  165.356208] md0: bitmap initialized from disk: read 1/1 pages, set 0 of 22345 bits[  165.392284] md0: detected capacity change from 0 to 8996958830592[  166.751398]  md0: unknown partition table[  170.624682] md: md4: recovery done.[  170.684334] RAID1 conf printout:[  170.684343]  --- wd:2 rd:2[  170.684353]  disk 0, wo:0, o:1, dev:sda2[  170.684361]  disk 1, wo:0, o:1, dev:sdb2[  170.707680] RAID1 conf printout:[  170.707688]  --- wd:2 rd:2[  170.707696]  disk 0, wo:0, o:1, dev:sda2[  170.707705]  disk 1, wo:0, o:1, dev:sdb2[  170.707711] RAID1 conf printout:[  170.707717]  --- wd:2 rd:2[  170.707724]  disk 0, wo:0, o:1, dev:sda2[  170.707732]  disk 1, wo:0, o:1, dev:sdb2[  176.102347] EXT4-fs (md0): Mount option "noacl" will be removed by 3.5[  176.102353] Contact linux-ext4@vger.kernel.org if you think we should keep it.[  176.102357][  176.226493] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 11136 failed (50625!=58107)[  176.230844] EXT4-fs (md0): group descriptors corrupted![  179.936278] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)[  179.942030] bonding: MII link monitoring set to 100 ms[  180.072528] bonding: bond0: setting mode to 802.3ad (4).[  180.079822] 8021q: adding VLAN 0 to HW filter on device bond0[  180.175987] 8021q: adding VLAN 0 to HW filter on device eth0[  180.181076] bonding: bond0: enslaving eth0 as a backup interface with a down link.[  180.268926] 8021q: adding VLAN 0 to HW filter on device eth1[  180.274141] bonding: bond0: enslaving eth1 as a backup interface with a down link.[  183.267091] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None[  183.279063] bonding: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex.[  183.319089] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None[  183.383057] bonding: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex.[  197.499064] bonding: bond0: link status definitely down for interface eth0, disabling it[  197.606078] bonding: bond0: link status definitely down for interface eth1, disabling it[  200.545192] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None[  200.587069] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond[  200.607825] bonding: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex.[  200.686121] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None[  200.713050] bonding: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex.[  225.711865] warning: `proftpd' uses 32-bit capabilities (legacy support in use)[  244.416166] FAT-fs (sdt1): bogus number of reserved sectors[  244.423079] FAT-fs (sdt1): Can't find a valid FAT filesystem[  244.438779] FAT-fs (sdt1): bogus number of reserved sectors[  244.445729] FAT-fs (sdt1): Can't find a valid FAT filesystem[  246.808917] rule type=2, num=0[  248.397135] Loading iSCSI transport class v2.0-871.[  248.643661] iscsi: registered transport (tcp)[  248.980580] iscsid (8604): /proc/8604/oom_adj is deprecated, please use /proc/8604/oom_score_adj instead.[  251.638562] ext4_init_reserve_inode_table0: dm-0, 14905[  251.645750] ext4_init_reserve_inode_table2: dm-0, 14905, 0, 0, 4096[  251.661096] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)[  261.609708] sysRequest.cgi[10693]: segfault at 18 ip b6fe6c2e sp bf9954b4 error 6 in libc-2.6.1.so[b6f5d000+12d000][  270.697558] EXT4-fs (sdv1): warning: mounting fs with errors, running e2fsck is recommended[  270.712313] ext4_init_reserve_inode_table0: sdv1, 14905[  270.718116] ext4_init_reserve_inode_table2: sdv1, 14905, 0, 0, 4096[  270.724360] EXT4-fs (sdv1): mounted filesystem with ordered data mode. Opts: (null)[  291.253817] ufsd: "mount" (sds1): is mounted as NTFS (without journal)[  571.360061] EXT4-fs (sdv1): error count: 1[  571.365961] EXT4-fs (sdv1): initial error at 1397955701: ext4_iget:3868: inode 111810033[  571.371911] EXT4-fs (sdv1): last error at 1397955701: ext4_iget:3868: inode 111810033


    zu ll /share/

    Ich glaube das ich eigentlich ext3 hatte!


    Aber 100% kann ich es nicht sagen!
    Erstellt worden ist das Raid gegen Ende 2012 falls das zum einschränken hilft.


    Ich habe bei den Reparaturversuchen des Raid in den letzten Tagen evtl. auf ext4 umgestellt _hurted:

    Ausgabe zu mdadm:

    Ich hab sehr vieles Probiert die letzten 4 Tage, vom Mounten bis Assembly erstellen, Superblock checken, ..........
    Ja ich glaube auch dieser Befehl war mit darunter


    Was meinst du mit zusammengesetzt, ich habe nie eines neu erstellt!
    Ich habe mehr versucht zu schauen ob was beschädigt ist und bin dann die Empfehlungen durchgegangen.

    Zitat von "Zelkin"

    Das bedeutet alles auf 0?

    Jup.

    Zitat von "Zelkin"

    eine Datenwiederherstellung noch irgendwie möglich?

    Keine Chance.