View previous topic :: View next topic |
Author |
Message |
hoacker Guru
Joined: 04 Aug 2007 Posts: 505 Location: Bürstadt, Germany
|
Posted: Sat Aug 06, 2016 12:04 pm Post subject: [solved] Need help: Recover data from Seagate NAS |
|
|
Hi there.
This week my wifes NAS stopped working, which reminded me that a backup plan was still on my todo list. Maybe someone can help me recovering the files?
NAS:
SEAGATE business storage 2-bay NAS (SRN02D) with 2 x 2TB HDDs
RAID 1
After switching on the NAS this Thursday the NAS did not serve a network share and had a different name. I tried to login to web admin interface but all i got was a page with only the "disk manager" showing no other admin options. The disk list showed two disks but no raid configuration.
I removed the disks from case and attached them to my gentoo machine. Both seem to have identical partitioning.
Code: | # ls /dev | grep sdc
sdc
sdc1
|
Code: | # fdisk -l /dev/sdc
Festplatte /dev/sdc: 1,8 TiB, 2000398934016 Bytes, 3907029168 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: D7A4472F-86DE-4A8B-9ECD-989A32CBF972
Gerät Anfang Ende Sektoren Größe Typ
/dev/sdc1 41 1953 1913 956,5K Microsoft Basisdaten
/dev/sdc2 2048 1953791 1951744 953M Microsoft Basisdaten
/dev/sdc3 1953792 3905535 1951744 953M Microsoft Basisdaten
/dev/sdc4 3905536 3926015 20480 10M Microsoft Basisdaten
/dev/sdc5 3926016 5879807 1953792 954M Microsoft Basisdaten
/dev/sdc6 5879808 5900287 20480 10M Microsoft Basisdaten
/dev/sdc7 5900288 5922815 22528 11M Microsoft Basisdaten
/dev/sdc8 5922816 6504447 581632 284M Microsoft Basisdaten
/dev/sdc9 6504448 8503295 1998848 976M Microsoft Basisdaten
/dev/sdc10 8503296 3907027254 3898523959 1,8T Microsoft Basisdaten
|
So, partition sdc10 seems to be the data partition, but only sdc1 shows up in /dev. How come?
Currently I dd a raid disk to an other HDD so I can try to recover files from the copy.
Anyone has an idea how I can mount the data partition?
Last edited by hoacker on Sun Aug 07, 2016 4:55 pm; edited 1 time in total |
|
Back to top |
|
|
frostschutz Advocate
Joined: 22 Feb 2005 Posts: 2977 Location: Germany
|
Posted: Sat Aug 06, 2016 1:20 pm Post subject: |
|
|
What does it look like in dmesg? mdadm --examine /dev/sdc*?
Perhaps your kernel is missing EFI/GPT support? zgrep PARTITION /proc/config.gz
You can map the partition with a loop device ( losetup --find --show --read-only --offset $((512*startsectornumber)) /dev/sdc ) |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54098 Location: 56N 3W
|
Posted: Sat Aug 06, 2016 1:42 pm Post subject: |
|
|
hoacker,
With Code: | Festplattenbezeichnungstyp: gpt | you also get a free protective MSDOS partition table that has a single partition of type 0xee.
This serves to warn that GPT is in use. Its all the kernel will see if you don't have GPT support. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
hoacker Guru
Joined: 04 Aug 2007 Posts: 505 Location: Bürstadt, Germany
|
Posted: Sat Aug 06, 2016 3:33 pm Post subject: |
|
|
Thank you! Indeed I'm missing GPT support in my kernel. Adding GPT and waiting for dd to finish... |
|
Back to top |
|
|
hoacker Guru
Joined: 04 Aug 2007 Posts: 505 Location: Bürstadt, Germany
|
Posted: Sun Aug 07, 2016 4:08 pm Post subject: |
|
|
All partitions show up and the data partition seems to be intact. This is what mdadm says:
Code: | # mdadm -E /dev/sdc10
/dev/sdc10:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 890d1adc:b9216237:2dffd17d:96cb7b61
Name : BA-0010755E84B4:8
Creation Time : Sat Jun 21 10:55:58 2014
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 3898521911 (1858.96 GiB 1996.04 GB)
Array Size : 1949260819 (1858.96 GiB 1996.04 GB)
Used Dev Size : 3898521638 (1858.96 GiB 1996.04 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=273 sectors
State : clean
Device UUID : c1ae1257:ab598b0a:29752c46:2aff8f3d
Update Time : Wed Aug 3 15:58:27 2016
Checksum : d72c6be5 - correct
Events : 2
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
|
I set up a raid array with this partition...
Code: | # cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdc10[0]
1949260819 blocks super 1.2 [2/1] [U_]
unused devices: <none> |
.. but I cannot mount.
Code: | # mount /dev/md0 /mnt/tmp
mount: unbekannter Dateisystemtyp »LVM2_member« |
This is what lvs tells me:
Code: | # lvs
/run/lvm/lvmetad.socket: connect failed: Datei oder Verzeichnis nicht gefunden
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv8 vg8 -wi-a----- 1,82t |
So I do
Code: | # vgchange -ay vg8
/run/lvm/lvmetad.socket: connect failed: Datei oder Verzeichnis nicht gefunden
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
1 logical volume(s) in volume group "vg8" now active
# mount /dev/vg8/lv8 /mnt/tmp
mount: Falscher Dateisystemtyp, ungültige Optionen, der
Superblock von /dev/mapper/vg8-lv8 ist beschädigt, fehlende
Kodierungsseite oder ein anderer Fehler
# tail /var/log/messages
Aug 7 18:04:02 fanny kernel: EXT4-fs (dm-0): bad block size 65536
|
What to do now? |
|
Back to top |
|
|
hoacker Guru
Joined: 04 Aug 2007 Posts: 505 Location: Bürstadt, Germany
|
Posted: Sun Aug 07, 2016 4:55 pm Post subject: |
|
|
Got it! Fetched os-fuse-umfuse-ext2 from github and mounted the volume.
Code: | # fuse-ext2 -o rw+ /dev/vg8/lv8 /mnt/tmp
fuse-umfuse-ext2: version:'0.4+pexip2', fuse_version:'29' [main (fuse-ext2.c:343)]
fuse-umfuse-ext2: enter [do_probe (do_probe.c:31)]
fuse-umfuse-ext2: leave [do_probe (do_probe.c:61)]
fuse-umfuse-ext2: opts.device: /dev/vg8/lv8 [main (fuse-ext2.c:370)]
fuse-umfuse-ext2: opts.mnt_point: /mnt/tmp [main (fuse-ext2.c:371)]
fuse-umfuse-ext2: opts.volname: [main (fuse-ext2.c:372)]
fuse-umfuse-ext2: opts.options: rw+ [main (fuse-ext2.c:373)]
fuse-umfuse-ext2: parsed_options: rw,fsname=/dev/vg8/lv8 [main (fuse-ext2.c:374)]
fuse-umfuse-ext2: mounting read-write [main (fuse-ext2.c:388)]
|
Solved! |
|
Back to top |
|
|
|