Network Space Max will boot, but shows no volumes.

KillaHurtz
Posts: 33
Joined: Thu May 19, 2011 3:55 am

Re: Network Space Max will boot, but shows no volumes.

Post by KillaHurtz » Mon May 11, 2015 7:51 pm

So what else can I do ?

I have a sata connector, original nas hardware, both HDDs.

KillaHurtz
Posts: 33
Joined: Thu May 19, 2011 3:55 am

Re: Network Space Max will boot, but shows no volumes.

Post by KillaHurtz » Mon May 11, 2015 10:34 pm

Anybody ?

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Network Space Max will boot, but shows no volumes.

Post by Mijzelf » Tue May 12, 2015 6:57 am

Try the other disk, to see if it shows up. Did you power the disk?

KillaHurtz
Posts: 33
Joined: Thu May 19, 2011 3:55 am

Re: Network Space Max will boot, but shows no volumes.

Post by KillaHurtz » Tue May 12, 2015 11:01 pm

root@ubuntu:/home/killahurtz# cat /proc/partitions
major minor #blocks name

2 0 4 fd0
8 0 20971520 sda
8 1 19921920 sda1
8 2 1 sda2
8 5 1046528 sda5
11 0 1048575 sr0
11 1 1048575 sr1
8 16 1953512448 sdb
8 17 1 sdb1
8 18 1951503907 sdb2
8 21 256977 sdb5
8 22 8001 sdb6
8 23 8001 sdb7
8 24 851413 sdb8
8 25 875511 sdb9
8 26 8001 sdb10
root@ubuntu:/home/killahurtz#

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Network Space Max will boot, but shows no volumes.

Post by Mijzelf » Wed May 13, 2015 7:31 am

OK, this disk shows up. When your system was in raid1, it should be possible to assemble&mount it.

Code: Select all

sudo su
mdadm --assemble /dev/md0 /dev/sdb2 --run
If that doesn't error out, you can mount the array:

Code: Select all

mkdir -p /tmp/mountpoint
mount -o ro /dev/md0 /tmp/mountpoint
Now you can access your data using the GUI in /tmp/mountpoint.

If it does error out, please post the error message, and the output of

Code: Select all

dmesg | tail
mdadm --examine /dev/sdb2

KillaHurtz
Posts: 33
Joined: Thu May 19, 2011 3:55 am

Re: Network Space Max will boot, but shows no volumes.

Post by KillaHurtz » Thu May 14, 2015 8:01 pm

mdadm: no recogniseable superblock on /dev/sdb2
mdadm: /dev/sdb2 has no superblock - assembly aborted

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Network Space Max will boot, but shows no volumes.

Post by Mijzelf » Sat May 16, 2015 3:07 pm

Hm. Can you post the output of

Code: Select all

sudo file -s /dev/sdb2

KillaHurtz
Posts: 33
Joined: Thu May 19, 2011 3:55 am

Re: Network Space Max will boot, but shows no volumes.

Post by KillaHurtz » Sun Apr 17, 2016 12:53 pm

/dev/sda: DOS/MBR boot sector

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Network Space Max will boot, but shows no volumes.

Post by Mijzelf » Sun Apr 17, 2016 5:24 pm

Wow. That took you a year?

Anyway, 'file' tells us that /dev/sda starts with a DOS/MBR boot sector. But the question is, what is inside /dev/sdb2. (Assuming the NAS disk is still sdb, after all that time.)

KillaHurtz
Posts: 33
Joined: Thu May 19, 2011 3:55 am

Re: Network Space Max will boot, but shows no volumes.

Post by KillaHurtz » Mon Apr 18, 2016 3:50 am

8 34 1951503907 sdc2
8 37 256977 sdc5
8 38 8001 sdc6
8 39 8001 sdc7
8 40 851413 sdc8
8 41 875511 sdc9
8 42 8001 sdc10
root@InfectedHardware:/home/killahurz# sudo file -s /dev/sdc2
/dev/sdc2: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs)
root@InfectedHardware:/home/killahurz#

Yes, sorry for the late reply. I got married, and have been working a lot more. I appreciate your help sir !

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Network Space Max will boot, but shows no volumes.

Post by Mijzelf » Mon Apr 18, 2016 10:42 am

KillaHurtz wrote:I got married
Congratulations!
root@InfectedHardware:/home/killahurz# sudo file -s /dev/sdc2
/dev/sdc2: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs)
The partition seems to contain a valid filesystem (XFS). So you can try to mount it directly:

Code: Select all

# Create mountpoint
mkdir /tmp/sdc2
# Mount it (read only)
sudo mount -o ro /dev/sdc2 /tmp/sdc2
If you get no blocking errors, the files should be readable in /tmp/sdc2/

KillaHurtz
Posts: 33
Joined: Thu May 19, 2011 3:55 am

Re: Network Space Max will boot, but shows no volumes.

Post by KillaHurtz » Mon Apr 18, 2016 12:37 pm

mount: unknown filesystem type 'linux_raid_member'

&


root@InfectedHardware:/home/killahurz# mdadm --assemble --run /dev/md0 /dev/sdb2mdadm: no recogniseable superblock on /dev/sdb2
mdadm: /dev/sdb2 has no superblock - assembly aborted

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Network Space Max will boot, but shows no volumes.

Post by Mijzelf » Mon Apr 18, 2016 2:13 pm

Try

Code: Select all

sudo mount -o ro -t xfs /dev/sdc2 /tmp/sdc2

KillaHurtz
Posts: 33
Joined: Thu May 19, 2011 3:55 am

Re: Network Space Max will boot, but shows no volumes.

Post by KillaHurtz » Mon Apr 18, 2016 2:21 pm

Mijzelf wrote:Try

Code: Select all

sudo mount -o ro -t xfs /dev/sdc2 /tmp/sdc2
Will do, just ran XFS_Repair - N to the drive and it's looking for a superblock duplicate on the drive.

*Edit*
So far the superblock search has yielded 2 results, and both failed. Is there a way around the superblock issue ?

Mijzelf
Posts: 6224
Joined: Mon Jun 16, 2008 10:45 am

Re: Network Space Max will boot, but shows no volumes.

Post by Mijzelf » Mon Apr 18, 2016 7:45 pm

That's bad. There is definitely something wrong with that disk. The raid header at the end of the partition seems to be unreadable, and the superblocks of the XFS filesystem are damaged too.
If we knew the size of the raid header, we could shrink the partition for that size. That *might* help xfs_repair, as now it's assuming the wrong partition size, I think. Unfortunately that headersize is not fixed.

I think now your best chance is to do low level recovery on that disk. A tool like PhotoRec can recover files from raw disk space, without any knowledge/help of the filesystem. The only condition is that the files have recognizable headers, and are not fragmented.

To run PhotoRec you'll need to connect another disk to write the rescued files to.

BTW, PhotoRec can also run from Windows, if you prefer that.

Post Reply