No Volumes No Shares - Superblock Issue?

[NigelBrownless]

My Lacie 2Big has lost all the Shares and has no Volume!
I can still see the unit on the Lacie Admin Page.
I've used the FVDW-SL Terminal to access the drive, and tried to Assemble and Mount the disks.
When trying to mount I get an error "mount: /dev/md4: can't read superblock"
Is there a way to restore the Superblock, I understood there were backups kept?
Thanks.

[fvdw]

some info for that can be found here https://plugout.net/viewtopic.php?f=26&t=3472&hilit=superblock&start=240#p35327

[NigelBrownless]

After reading through the suggested Post, Am I right in thinking that an XFS_Repair might be the next step?
I've tried it with the -n option and it gives the same issue with the Superblock. Running it without the -n I'm thinking it will try and recover the Superblock from a Backup version?

I tried:

Code: Select all

xfs_repair /dev/md4

and received the following:

Code: Select all

Phase 1 - find and verify superblock...

fatal error -- couldn't allocate block map, size = 121968988

[NigelBrownless]

So following other Posts, I understand I need to create a Swap on an external USB?
I've plugged one in to the 2Big, how do I see that it has been seen on the fvdw-sl console?

[fvdw]

in the disk setup menu you should see it and you can, if necessary, format it.

[NigelBrownless]

On the LAcie Web Interface I can see it as an External USB Drive - KINGSTON (USB) 115.6Gb. Currently formatted as FAT32.
How do I identify the ID to use on the fvdw-sl console for the mkswap command?
And is it worth you reviewing any of the Stats on the disks before I start the xfs_repair?

[fvdw]

the fvdw-sl console loads a standalone kernel that runs from ram. So no webinterface. If the usb device is plugged in it should get sdc as disk id assigned. You could check which disks are found by using the command

Code: Select all

fdisk -l

To use the usb disk you must mount it.
Assuming it is known as sdc you can do that as follow:

Code: Select all

mkdir /sdc
mount /dev/sdc /sdc

If you want to use it as swap then no mounting is needed
then you can use /dev/sdc as id.

As long as array is not assembled there is no possibility to check the file system.

You could run mdadm --examine but probably it will give dame info no superblock found

Code: Select all

mdadm --examine /dev/sda2
mdadm --examine /dev/sdb2
mdadm --detail /dev/md4

[NigelBrownless]

Code: Select all

mdadm --examine /dev/sda2
/dev/sda2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 86017f48:72ee573c:fee6b018:d9ae7a6f
  Creation Time : Sat Nov  6 10:25:07 2010
     Raid Level : raid1
  Used Dev Size : 1951503808 (1861.10 GiB 1998.34 GB)
     Array Size : 1951503808 (1861.10 GiB 1998.34 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 4

    Update Time : Fri Nov 22 11:21:57 2024
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : a372b38b - correct
         Events : 2988895


      Number   Major   Minor   RaidDevice State
this     0       8        2        0      active sync   /dev/sda2

   0     0       8        2        0      active sync   /dev/sda2
   1     1       8       18        1      active sync   /dev/sdb2


Code: Select all

mdadm --examine /dev/sdb2

/dev/sdb2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 86017f48:72ee573c:fee6b018:d9ae7a6f
  Creation Time : Sat Nov  6 10:25:07 2010
     Raid Level : raid1
  Used Dev Size : 1951503808 (1861.10 GiB 1998.34 GB)
     Array Size : 1951503808 (1861.10 GiB 1998.34 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 4

    Update Time : Fri Nov 22 11:21:57 2024
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : a372b39d - correct
         Events : 2988895


      Number   Major   Minor   RaidDevice State
this     1       8       18        1      active sync   /dev/sdb2

   0     0       8        2        0      active sync   /dev/sda2
   1     1       8       18        1      active sync   /dev/sdb2


After Assembling...

Code: Select all

mdadm --detail /dev/md4

/dev/md4:
        Version : 0.90
  Creation Time : Sat Nov  6 10:25:07 2010
     Raid Level : raid1
     Array Size : 1951503808 (1861.10 GiB 1998.34 GB)
  Used Dev Size : 1951503808 (1861.10 GiB 1998.34 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 4
    Persistence : Superblock is persistent

    Update Time : Fri Nov 22 11:21:57 2024
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 86017f48:72ee573c:fee6b018:d9ae7a6f
         Events : 0.2988895

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2


I could not see a sdc2 disk with the USB plugged in...Although see some worrying messages regaridng partition tables?

Code: Select all

fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1         250     2008093+  f Win95 Ext'd (LBA)
/dev/sda2             251      243201  1951503907+ 83 Linux
/dev/sda5               1          32      256977  83 Linux
/dev/sda6              33          33        8001  83 Linux
/dev/sda7              34          34        8001  83 Linux
/dev/sda8              35         140      851413+ 83 Linux
/dev/sda9             141         249      875511  83 Linux
/dev/sda10            250         250        8001  83 Linux

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         250     2008093+  5 Extended
/dev/sdb2             251      243201  1951503907+ 83 Linux
/dev/sdb5               1          32      256977  82 Linux swap
/dev/sdb6              33          33        8001  83 Linux
/dev/sdb7              34          34        8001  83 Linux
/dev/sdb8              35         140      851413+ 83 Linux
/dev/sdb9             141         249      875511  83 Linux
/dev/sdb10            250         250        8001  83 Linux

Disk /dev/md4: 1998.3 GB, 1998339899392 bytes
2 heads, 4 sectors/track, 487875952 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md4 doesn't contain a valid partition table


[fvdw]

your raid seems to be ok, both disk seems to have a readable superblock.What happens if you give this command

Code: Select all

mdadm --verbose --assemble --force /dev/md4 /dev/sda2 /dev/sdb2

about sdc, it must contain a valid partition table to be able to mount it or used it as swap.

[NigelBrownless]

Code: Select all

mdadm --verbose --assemble --force /dev/md4 /dev/sda2 /dev/sdb2

Gives the following output...

Code: Select all

mdadm: looking for devices for /dev/md4
mdadm: /dev/sda2 is identified as a member of /dev/md4, slot 0.
mdadm: /dev/sdb2 is identified as a member of /dev/md4, slot 1.
mdadm: added /dev/sdb2 to /dev/md4 as 1
mdadm: added /dev/sda2 to /dev/md4 as 0
mdadm: /dev/md4 has been started with 2 drives.


Trying to perform the mount command (After creating the /mountpoint dir):

Code: Select all

mount -o ro /dev/md4 /mountpoint

I still get the following response:

Code: Select all

mount: /dev/md4: can't read superblock