NAS MD86517 Datenverlust

Karl_K — Mon, 15 Jun 2020 09:56:23 GMT

Hallo,

vielleicht kann hier jemand weiterhelfen. Ein Freund von mir hat dieses Heimnetzlaufwerk seit ca. 10 Jahren und lief bis jetzt einwandfrei.

Letzte Woche kam zum ersten Mal die rote Warnlampe. Im Browsertool wurde noch Daten angezeigt (ca. 270 GB).

Unter "Speicher - Volumen - internes Volumen" kann man einen Check der Platte durchführen.

Der brachte dann auch Fehler, aber laut Protokoll sollte diese behoben sein.

Nur leider sind jetzt die Daten weg.

Ich hatte dieses NAS gestern an mein Heimnetzwerk angebunden.

Der Staus wird als OK angezeigt, aber leider als leer.

Zeigte so keinen Fehler (rote Warnlampe).

Erst als ich diesen Check wiederholt hatte, wurde sie angezeigt.

1.) Gibt es eine Möglichkeit, diese eventuell wieder herzustellen ohne irgendwelche Zusatzsoftware wie Recuva?

2.) Kann man die Platte überhaupt aus dem Gehäuse ausbauen und als USB am PC anschließen, falls es keine andere

Möglichkeit gibt?

Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
xfs_repair: read failed: Input/output error
XFS: empty log check failed
zero_log: cannot find log head/tail (xlog_find_tail=5) zeroing it anyway
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
imap claims a free inode 170 is in use correcting imap and clearing inode
cleared inode 170
imap claims a free inode 171 is in use correcting imap and clearing inode
cleared inode 171
imap claims a free inode 172 is in use correcting imap and clearing inode
cleared inode 172
correcting nblocks for inode 175 was 322 - counted 0
correcting nblocks for inode 176 was 1259 - counted 1
imap claims a free inode 182 is in use correcting imap and clearing inode
cleared inode 182
imap claims a free inode 183 is in use correcting imap and clearing inode
cleared inode 183
imap claims a free inode 184 is in use correcting imap and clearing inode
cleared inode 184
imap claims a free inode 185 is in use correcting imap and clearing inode
cleared inode 185
imap claims a free inode 186 is in use correcting imap and clearing inode
cleared inode 186
- agno = 1
data fork in ino 1073742747 claims free block 67240175
data fork in regular inode 1073742747 claims used block 67240176
bad data fork in inode 1073742747
cleared inode 1073742747
corrupt block 0 in directory inode 1073742750
will junk block
no . entry for directory 1073742750
no .. entry for directory 1073742750
problem with directory contents in inode 1073742750
cleared inode 1073742750
data fork in regular inode 1075842305 claims used block 67240174
bad data fork in inode 1075842305
cleared inode 1075842305
imap claims a free inode 1075842328 is in use correcting imap and clearing inode
cleared inode 1075842328
imap claims a free inode 1075842329 is in use correcting imap and clearing inode
cleared inode 1075842329
imap claims a free inode 1075842330 is in use correcting imap and clearing inode
cleared inode 1075842330
imap claims a free inode 1075842331 is in use correcting imap and clearing inode
cleared inode 1075842331
imap claims a free inode 1075842332 is in use correcting imap and clearing inode
cleared inode 1075842332
imap claims a free inode 1075842333 is in use correcting imap and clearing inode
cleared inode 1075842333
imap claims a free inode 1075842334 is in use correcting imap and clearing inode
cleared inode 1075842334
imap claims a free inode 1075842339 is in use correcting imap and clearing inode
cleared inode 1075842339
imap claims a free inode 1075842340 is in use correcting imap and clearing inode
cleared inode 1075842340
imap claims a free inode 1075842341 is in use correcting imap and clearing inode
cleared inode 1075842341
imap claims a free inode 1075842342 is in use correcting imap and clearing inode
cleared inode 1075842342
imap claims a free inode 1075842343 is in use correcting imap and clearing inode
cleared inode 1075842343
correcting nblocks for inode 1075842346 was 1 - counted 0
correcting nblocks for inode 1075842347 was 3 - counted 0
- agno = 2
- agno = 3
imap claims a free inode 3221228866 is in use correcting imap and clearing inode
cleared inode 3221228866
imap claims a free inode 3221228867 is in use correcting imap and clearing inode
cleared inode 3221228867
imap claims a free inode 3221228868 is in use correcting imap and clearing inode
cleared inode 3221228868
imap claims a free inode 3221228869 is in use correcting imap and clearing inode
cleared inode 3221228869
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
entry twonkymedia in shortform directory 132 references free inode 1073742750
junking entry twonkymedia in directory inode 132
entry $RECYCLE.BIN in shortform directory 133 references free inode 1075842330
junking entry $RECYCLE.BIN in directory inode 133
entry System Volume Information in shortform directory 133 references free inode 3221228866
- agno = 1
junking entry System Volume Information in directory inode 133
- agno = 2
entry clidump.gui at block 0 offset 96 in directory inode 1073741952 references free inode 1073742747
clearing inode number in entry at offset 96...
entry bea7820e1dbb357f0ec5a51eead2f636_A.usbzync at block 0 offset 424 in directory inode 1073741952 references free inode 1075842328
clearing inode number in entry at offset 424...
entry md0_B.usbzync at block 0 offset 536 in directory inode 1073741952 references free inode 1075842329
clearing inode number in entry at offset 536...
entry core.zyshd.0.0.11 at block 0 offset 560 in directory inode 1073741952 references free inode 1075842344
clearing inode number in entry at offset 560...
entry .. at block 0 offset 32 in directory inode 2148009940 references free inode 1073742750
clearing inode number in entry at offset 32...
no .. entry for directory 2148009940
- agno = 3
data fork in ino 1073742746 claims dup extent off - 5 start - 67240176 cnt 1
bad data fork in inode 1073742746
cleared inode 1073742746
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
entry Instruction Manual for Safety and Comfort.pdf in directory inode 133 not consistent with .. value (2148009940) in inode 175
entry storage.txt in directory inode 1073741952 points to free inode 1073742746
entry clidump_backup.zyshd in dir inode 1073741952 inconsistent with .. value (2148009940) in ino 1075842346
bad hash table for directory inode 1073741952 (no data entry): rebuilding
rebuilding directory inode 1073741952
bad hash table for directory inode 2148009940 (no data entry): rebuilding
rebuilding directory inode 2148009940
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 1073742751 moving to lost+found
disconnected inode 1075842304 moving to lost+found
disconnected inode 1075842308 moving to lost+found
disconnected inode 1075842309 moving to lost+found
disconnected inode 1075842315 moving to lost+found
disconnected dir inode 2148009940 moving to lost+found
Phase 7 - verify and correct link counts...
resetting inode 132 nlinks from 8 to 7
resetting inode 133 nlinks from 4 to 2
resetting inode 176 nlinks from 1 to 2
resetting inode 1075842347 nlinks from 1 to 2
Note - quota info will be regenerated on next quota mount.
done
xfs_repair return value:0

Recht herzlichen Dank !

Karl

Re: NAS MD86517 Datenverlust

Andi — Wed, 17 Jun 2020 12:56:08 GMT

Hallo @Karl_K und herzlich willkommen in der Community.

Ich vermute hier auch einen Defekt der HDD. Die Platte kann man ausbauen und an einen PC anschließen. Soviel ich weiß, verwendet der NAS aber ein Linux-Betriebssytem. Es kann daher sein, dass die Platte unter Windows nicht lesbar ist und du einen Linux-PC verwenden müsstest.

Gruß - Andi

Re: NAS MD86517 Datenverlust

Andi — Wed, 16 Dec 2020 08:02:28 GMT

Hallo @Karl_K.

Was ist eigentlich aus dieser Sache geworden? Konntest du eine Lösung finden?

Gruß - Andi

Thema "Re: NAS MD86517 Datenverlust" in Netzwerk / Speicher

NAS MD86517 Datenverlust

Re: NAS MD86517 Datenverlust

Re: NAS MD86517 Datenverlust