raid5 credo di aver combinato un disastro, aiuto!!!!!!

Discussioni sulle funzioni di RAID0/ RAID1/ Q-RAID1/RAID5/ dei NAS.
Rispondi
softgallo
Messaggi: 10
Iscritto il: 08 ago 2016, 19:55

raid5 credo di aver combinato un disastro, aiuto!!!!!!

Messaggio da softgallo »

Ciao a tutti.

ho un qnap ts-439 pro, incautamente mi taglierei le mani, alla voce sicurezza ho ripristinato il certificato predefinto e chiave privata.

risultato, in gestione archivi il raid5 e presente, ma me lo da in stato non montato....... aiutooooooooooooooo

ho provato a collegarmi in ssh al nas:

cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
5855836800 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

md4 : active raid1 sdd2[4](S) sdc2[3](S) sdb2[2] sda2[0]
530128 blocks super 1.0 [2/2] [UU]

md13 : active raid1 sdc4[0] sda4[3] sdd4[2] sdb4[1]
458880 blocks [4/4] [UUUU]
bitmap: 0/57 pages [0KB], 4KB chunk

md9 : active raid1 sdc1[0] sda1[3] sdd1[2] sdb1[1]
530048 blocks [4/4] [UUUU]
bitmap: 1/65 pages [4KB], 4KB chunk

unused devices: <none>

ho provato a fare il mount:

mount -t ext4 /dev/md0 /share/MD0_DATA
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

inviando il comando:
dmesg
120
[ 46.858311] md13: unknown partition table
[ 48.207269] kjournald starting. Commit interval 5 seconds
[ 48.251435] EXT3-fs (md9): using internal journal
[ 48.255620] EXT3-fs (md9): mounted filesystem with writeback data mode
[ 73.881985] kjournald starting. Commit interval 5 seconds
[ 73.956201] EXT3-fs (md9): using internal journal
[ 73.960419] EXT3-fs (md9): mounted filesystem with ordered data mode
[ 124.255138] kjournald starting. Commit interval 5 seconds
[ 124.333219] EXT3-fs (md13): using internal journal
[ 124.337477] EXT3-fs (md13): mounted filesystem with writeback data mode
[ 148.157231] cryptodev: driver 0.9 loaded.
[ 148.191599] usbcore: registered new interface driver usbhid
[ 148.196524] usbhid: USB HID core driver
[ 148.210001] Register ICH/PCH RTC driver.
[ 148.224398] iTCO_vendor_support: vendor-support=0
[ 148.233159] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[ 148.239535] iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x0860)
[ 148.245592] iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
[ 148.258406] usbcore: registered new interface driver usblp
[ 148.275571] e1000e: Intel(R) PRO/1000 Network Driver - 2.4.14-NAPI
[ 148.281201] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 148.285974] e1000e 0000:01:00.0: Disabling ASPM L0s L1
[ 148.290535] e1000e 0000:01:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 148.295132] e1000e 0000:01:00.0: irq 44 for MSI/MSI-X
[ 148.295155] e1000e 0000:01:00.0: irq 45 for MSI/MSI-X
[ 148.295177] e1000e 0000:01:00.0: irq 46 for MSI/MSI-X
[ 148.401988] e1000e 0000:01:00.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:08:9b:bd:95:24
[ 148.406999] e1000e 0000:01:00.0: eth0: Intel(R) PRO/1000 Network Connection
[ 148.411483] e1000e 0000:01:00.0: eth0: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 148.422581] e1000e 0000:02:00.0: Disabling ASPM L0s L1
[ 148.427288] e1000e 0000:02:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 148.432111] e1000e 0000:02:00.0: irq 47 for MSI/MSI-X
[ 148.432134] e1000e 0000:02:00.0: irq 48 for MSI/MSI-X
[ 148.432156] e1000e 0000:02:00.0: irq 49 for MSI/MSI-X
[ 148.544409] e1000e 0000:02:00.0: eth1: (PCI Express:2.5GT/s:Width x1) 00:08:9b:bd:95:25
[ 148.550474] e1000e 0000:02:00.0: eth1: Intel(R) PRO/1000 Network Connection
[ 148.556400] e1000e 0000:02:00.0: eth1: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
[ 148.567449] jnl: driver (lke_9.2.0 QNAP, LBD=ON) loaded at f8836000
[ 148.577736] ufsd: module license 'Commercial product' taints kernel.
[ 148.582549] Disabling lock debugging due to kernel taint
[ 148.590737] ufsd: driver (lke_9.2.0 QNAP, build_host("BuildServer47-1"), acl, ioctl, bdi, sd2(0), fua, bz, rsrc) loaded at f8933000
[ 148.590746] NTFS support included
[ 148.590750] Hfs+/HfsJ support included
[ 148.590753] optimized: speed
[ 148.590756] Build_for__QNAP_Atom_x86_k3.4.6_2014-12-15_lke_9.2.0_r245986_b56
[ 148.590761]
[ 148.673380] fnotify: Load file notify kernel module.
[ 149.796495] usbcore: registered new interface driver snd-usb-audio
[ 149.810809] usbcore: registered new interface driver snd-usb-caiaq
[ 149.830211] Linux video capture interface: v2.00
[ 149.866600] usbcore: registered new interface driver uvcvideo
[ 149.873111] USB Video Class driver (1.1.1)
[ 150.061394] 8021q: 802.1Q VLAN Support v1.8
[ 163.112996] kjournald starting. Commit interval 5 seconds
[ 163.121180] EXT3-fs (md9): using internal journal
[ 163.126214] EXT3-fs (md9): mounted filesystem with ordered data mode
[ 168.380805] md: bind<sda2>
[ 168.389246] md/raid1:md4: active with 1 out of 1 mirrors
[ 168.395754] md4: detected capacity change from 0 to 542851072
[ 169.428905] md4: unknown partition table
[ 171.563181] Adding 530124k swap on /dev/md4. Priority:-1 extents:1 across:530124k
[ 176.206037] md: bind<sdb2>
[ 176.229886] RAID1 conf printout:
[ 176.229896] --- wd:1 rd:2
[ 176.229905] disk 0, wo:0, o:1, dev:sda2
[ 176.229914] disk 1, wo:1, o:1, dev:sdb2
[ 176.230118] md: recovery of RAID array md4
[ 176.235321] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.
[ 176.240672] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
[ 176.245940] md: using 128k window, over a total of 530128k.
[ 178.778390] md: bind<sdc2>
[ 180.977508] md: bind<sdd2>
[ 182.977064] md: md0 stopped.
[ 183.001740] md: md0 stopped.
[ 183.226696] md: bind<sdb3>
[ 183.231920] md: bind<sdc3>
[ 183.237061] md: bind<sdd3>
[ 183.242125] md: bind<sda3>
[ 183.248408] md/raid:md0: device sda3 operational as raid disk 0
[ 183.253075] md/raid:md0: device sdd3 operational as raid disk 3
[ 183.257598] md/raid:md0: device sdc3 operational as raid disk 2
[ 183.262038] md/raid:md0: device sdb3 operational as raid disk 1
[ 183.284102] md/raid:md0: allocated 67792kB
[ 183.288603] md/raid:md0: raid level 5 active with 4 out of 4 devices, algorithm 2
[ 183.293020] RAID conf printout:
[ 183.293026] --- level:5 rd:4 wd:4
[ 183.293034] disk 0, o:1, dev:sda3
[ 183.293040] disk 1, o:1, dev:sdb3
[ 183.293046] disk 2, o:1, dev:sdc3
[ 183.293051] disk 3, o:1, dev:sdd3
[ 183.293131] md0: detected capacity change from 0 to 5996376883200
[ 184.415275] md0: unknown partition table
[ 186.144882] md: md4: recovery done.
[ 186.231445] RAID1 conf printout:
[ 186.231454] --- wd:2 rd:2
[ 186.231463] disk 0, wo:0, o:1, dev:sda2
[ 186.231470] disk 1, wo:0, o:1, dev:sdb2
[ 186.250227] RAID1 conf printout:
[ 186.250234] --- wd:2 rd:2
[ 186.250240] disk 0, wo:0, o:1, dev:sda2
[ 186.250246] disk 1, wo:0, o:1, dev:sdb2
[ 186.250250] RAID1 conf printout:
[ 186.250255] --- wd:2 rd:2
[ 186.250260] disk 0, wo:0, o:1, dev:sda2
[ 186.250266] disk 1, wo:0, o:1, dev:sdb2
[ 188.292546] 8021q: adding VLAN 0 to HW filter on device eth0
[ 188.418774] 8021q: adding VLAN 0 to HW filter on device eth1
[ 191.817095] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 210.962643] e1000e 0000:01:00.0: eth0: changing MTU from 1500 to 8996
[ 214.673096] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 249.697587] Initiate iscsi target log successfully.
[ 249.724849] iscsi_log_rcv_msg: get log pid = 7081.
[ 257.211662] rule type=2, num=0
[ 257.547924] Loading iSCSI transport class v2.0-871.
[ 257.636214] iscsi: registered transport (tcp)
[ 257.706124] iscsid (7746): /proc/7746/oom_adj is deprecated, please use /proc/7746/oom_score_adj instead.
[ 260.062075] tun: Universal TUN/TAP device driver, 1.6
[ 260.068458] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 260.131404] PPP generic driver version 2.4.2
[ 260.253084] nf_conntrack version 0.5.0 (16089 buckets, 64356 max)
[ 260.360071] PPP MPPE Compression module registered
[ 260.389899] PPP BSD Compression module registered
[ 260.422106] PPP Deflate Compression module registered
[ 260.433097] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 270.829424] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 270.837541] NFSD: starting 90-second grace period
[ 292.806518] sysRequest.cgi[9750]: segfault at 18 ip b6f9fc2e sp bf92bbe4 error 6 in libc-2.6.1.so[b6f16000+12d000]
[ 1718.436940] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 1760.898861] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 1872.234822] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 2351.949132] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 2439.429208] EXT3-fs (md0): error: can't find ext3 filesystem on dev md0.
[ 2447.380937] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 3641.542190] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 3648.464399] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[~] #

il log del problema..

aiuto vi prego, c'e' qualche possibilita di recuperare il contenuto degli HD in raid5, o ancora esiste un modo per riprare e fare di nuovo il mount del RAID5???????

Grazie a tutti.
mi sa che ho fatto un casino..........
Grazie ciao.
Gianluca : Andry :
softgallo
Messaggi: 10
Iscritto il: 08 ago 2016, 19:55

Re: raid5 credo di aver combinato un disastro, aiuto!!!!!!

Messaggio da softgallo »

Ciao a tutti.
Risolto il problema..... in sostanza avevo spazzato via la chiave di criptazione sotituita con quelle standard di sistema......

fortuna vuole che ho recuperato la password della chiave standard, ed ho potuto sbloccare il nas....

a quel punto il raid si e rimontato e tutti i 5tb sono tornati online.. ora backup a mani basse...... prima di ogni altra cosa.....

saluti e buon ferragosto a tutti.

ciao.
wozxyz
Messaggi: 1589
Iscritto il: 13 mag 2010, 12:30

Re: raid5 credo di aver combinato un disastro, aiuto!!!!!!

Messaggio da wozxyz »

Meno male che è finito tutto bene!
Grazie per la condivisione.
TS-459 Pro - TS-221 - TS-212 - HS-210 Squeezebox Touch & Duet - WD Live Hub
Rispondi