No Volumes No Shares - Superblock Issue?

[NigelBrownless]

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

I moved the USB Drive to my PC and added a txt file. Then put it back in the NAS. When using the native Lacie Web Interface I can see it there in the Admin Console.

However when using the FVDW-SL Console, I can not see the USB registered as a disk.

Code: Select all

fdisk -l

gives the following output...

Code: Select all

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


Some of the output from

Code: Select all

dmesg

Code: Select all

[   30.240289] Freeing unused kernel memory: 1932K (c0767000 - c094a000)
[   34.325363] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   34.335700] ehci-orion: EHCI orion driver
[   34.339927] orion-ehci orion-ehci.0: EHCI Host Controller
[   34.345358] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   34.353077] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   34.376221] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   34.382275] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   34.389077] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   34.396303] usb usb1: Product: EHCI Host Controller
[   34.401179] usb usb1: Manufacturer: Linux 3.14.2 ehci_hcd
[   34.406587] usb usb1: SerialNumber: orion-ehci.0
[   34.411913] hub 1-0:1.0: USB hub found
[   34.415727] hub 1-0:1.0: 1 port detected
[   34.426477] usbcore: registered new interface driver usb-storage
[   86.104664] random: nonblocking pool is initialized
[  143.501323] md: md4 stopped.
[  143.507473] md: bind<sdb2>
[  143.510842] md: bind<sda2>
[  143.517041] md/raid1:md4: active with 2 out of 2 mirrors
[  143.522472] md4: detected capacity change from 0 to 1998339899392
[  287.229366]  md4: unknown partition table
[  287.509585] XFS (md4): unknown mount option [-ro].
[  350.893138] XFS (md4): Mounting Filesystem
[  351.108041] XFS (md4): Starting recovery (logdev: internal)
[  351.216085] XFS (md4): xlog_recover_process_data: bad clientid 0x0
[  351.222315] XFS (md4): log mount/recovery failed: error 5
[  351.227922] XFS (md4): log mount failed


[fvdw]

Maybe this is still a try worth
Assemble the array.

Then list all backup superblocks
The -N option causes the file system parameters to be printed out without really creating the file system

Code: Select all

mkfs.xfs -N /dev/md4


This should produce a list of backup superblocks

Now try to mount the array by using one of these blocks

Code: Select all

mount -o sb=alternative-superblock /dev/md4 /mnt-point

[NigelBrownless]

Code: Select all

mkfs.xfs -N /dev/md4

Gave the following response...

Code: Select all

mkfs.xfs: /dev/md4 appears to contain an existing filesystem (xfs).
mkfs.xfs: Use the -f option to force overwrite.

I wanted to check first that I would need to then run the following, but with the -N it won't overwrite?

Code: Select all

mkfs.xfs -f -N /dev/md4

[fvdw]

strange the command with -N ootion should list meta data of the file system :scratch
Do not use the -f option it may destroy your filesystem
I need to look if in other posts I can find position of superblock

[fvdw]

lets try to copy the superblock content and look what is inside

Code: Select all

dd bs=1 count=512 if=/dev/md4 of=md4-512.img

open the created file with a hex editor post the content or put de img file in a tar archive and attach it
If the superblock contains content we might be able to see what is wrong and to find locations of backup superblocks

[NigelBrownless]

Attached is the img fil in a rar.

[fvdw]

The good news is that the superblock is nit empty.

Code: Select all

00000000h: 58 46 53 42 00 00 10 00 00 00 00 00 1D 14 65 70 ; XFSB..........ep
00000010h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000020h: 2E 7A CF 91 9B 55 48 8E AC F2 C7 A1 EB D5 69 EA ; .zÏ‘›UHŽ¬òÇ¡ëÕiê
00000030h: 00 00 00 00 10 00 00 04 00 00 00 00 00 00 00 80 ; ...............€
00000040h: 00 00 00 00 00 00 00 81 00 00 00 00 00 00 00 82 ; ..............‚
00000050h: 00 00 00 01 07 45 19 5C 00 00 00 04 00 00 00 00 ; .....E.\........
00000060h: 00 00 80 00 A4 F4 02 00 01 00 00 10 00 00 00 00 ; ..€.¤ô..........
00000070h: 00 00 00 00 00 00 00 00 0C 09 08 04 1B 00 00 05 ; ................
00000080h: 00 00 00 00 00 0B F0 00 00 00 00 00 00 00 19 D4 ; ......ð........Ô
00000090h: 00 00 00 00 03 CD 16 A3 00 00 00 00 00 00 00 00 ; .....Í.£........
000000a0h: 00 00 00 00 00 00 00 83 00 00 00 00 00 00 00 84 ; .......ƒ.......„
000000b0h: 00 3F 00 00 00 00 00 02 00 00 00 00 00 00 00 00 ; .?..............
000000c0h: 00 00 00 00 00 00 00 01 00 00 00 08 00 00 00 08 ; ................
000000d0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
000000e0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
000000f0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000100h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000110h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000120h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000130h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000140h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000150h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000160h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000170h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000180h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
00000190h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
000001a0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
000001b0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
000001c0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
000001d0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
000001e0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................
000001f0h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ; ................

Looks pretty normal
(I translated the hex values to decimal for easy use)
Here we can see it is an xfs file system with block size of 4096 bytes.
It has 487875952 blocks so total size 1.998.339.899.392 bytes (1.8 TB)
The AG size is 121968988 blocks so 499.584.974.848 bytes and there are 4 AG's which matches total size als calculated
At beginning of each AG a backup superblock should be present.
So we could try to read a backup block

Code: Select all

dd bs=4096 skip=121968988 count=1 if=/dev/md4 of=md4-backup1.img

There is one entry in the superblock that I am unsure about and that is the position of the first journal block, it mentions at block 268.435.460 that is more then 2 times the AG size. Maybe it is wrong and might be the reason of the problem. But I could be wrong.
There is a possibility to clear the log by using

Code: Select all

xfs_repair -L /dev/md4

This will zero the log, it could be a last resort to try but doing that may lead to more data corruption or data loss.
So lets first try to see what is in the backup superblock

[NigelBrownless]

Code: Select all

 dd bs=4096 skip=121968988 count=1 if=/dev/md4 of=md4-backup1.img

Gave the following output....

Code: Select all

1+0 records in
1+0 records out
4096 bytes (4.0KB) copied, 0.285475 seconds, 14.0KB/s


The file is attached.

[fvdw]

that does not contain a superblock, lets copy a few blocks around that point could be that it is in the next or previous block

Code: Select all

dd bs=4096 skip=121968986 count=4 if=/dev/md4 of=md4-backup1-4.img

ps the good news is that there seems to be data on the disk, I can see some file names (json)

[NigelBrownless]

Code: Select all

dd bs=4096 skip=121968986 count=4 if=/dev/md4 of=md4-backup1-4.img

Gave the following output:

Code: Select all

4+0 records in
4+0 records out
16384 bytes (16.0KB) copied, 0.280591 seconds, 57.0KB/s

The file is attached.