Dashboard opens with blank only

[Jocko]

Perhaps we should recreate it with a command such as below?

Code: Select all

mdadm --create --chunk=64 --level=5 --raid-devices=5 /dev/md4 /dev/sd[abcde]2

Do not do that !
If I understand rightly, you already have a clean raid and with such a command you will destroy your data if they are still present.

So your issue is the file system on the raid which seems to be corrupted and I am afraid not to be recoverable

... Sorry, could not valid secondary superblock
Exiting now.

I have to deepen more

But please to post

Code: Select all

cat /proc/mdstat

[fariaslcfs]

But please to post

Code: Select all

cat /proc/mdstat

Result:

Code: Select all

root@fvdw-sta-kirkwood:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid5 sda2[0] sde2[5] sdd2[3] sdc2[2] sdb2[1]
      7805490688 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
     
unused devices: <none>


[fvdw]

@jocko
As there seems to be no superblocks found,
could there be an LVM layer on the raid?
I am not a raid expert but I saw this in the past on a cloudbox
Something like this:

Code: Select all

| / | /var | /usr | /home  |
 --------------------------
|       LVM Volume         |
 --------------------------
|       RAID Volume        |
 --------------------------
| Disk 1 | Disk 2 | Disk 3 |

[fariaslcfs]

I not sure. Actually, I don't know how to check that. All the info we have is that we get using the Util-Linux you provided.

[Jocko]

Hi

AFAIK, on lacie OS there is no Logical volume with a 5big2. Only cloudbox set it.

[Jocko]

Hi

AFAIK, on lacie OS there is no Logical volume with a 5big2. Only cloudbox set it.

Code: Select all

md4 : active raid5 sda2[0] sde2[5] sdd2[3] sdc2[2] sdb2[1]

So I confirm your raid is clean and nothing should be deepen on this side

[fariaslcfs]

By "clean" you mean empty? So, all previous data is lost, and there is nothing left to solve that?

[fvdw]

I think it is not empty, you reported this

Code: Select all

root@fvdw-sta-kirkwood:/ # mdadm -D /dev/md4
/dev/md4:
        Version : 1.2
  Creation Time : Thu Jan  1 01:15:34 1970
     Raid Level : raid5
     Array Size : 7805490688 (7443.90 GiB 7992.82 GB)
  Used Dev Size : 1951372672 (1860.97 GiB 1998.21 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent


so about 1.7 TB used of the 7.3

[fvdw]

I found this on the internet

OK, post the result from this command. Change the device as necessary: sudo xfsdump -f /dev/sdb1 | grep -i superblock

I want to note my personal experience, that Ubuntu hasn’t had good XFS support for a while, and you might find it very helpful to download an old copy of warty warthog, and use a livecd with that.

You might get a response that looks like:

Couldn't find valid filesystem superblock.

if so, don't give up yet. You can try sudo mkfs.xfs -N /dev/sdb1 which will list the details about the filesystem, without writeing any changes. Hopefully you will see something at the end of that list like: ... superblock backups: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

That is a list (examples: yours may vary) of alternative superblocks. you can then use in a trial and error type method, the list of superblocks, to reconstruct your XFS filesystem using mkfs, fsck, and mknode.

Before I go writing a long answer, post back details from xfsdump, and mkfs.xfs

@Jocko, do you think this is useful to try. mkfs.xfs is included in standalone kernel tools

[Jocko]

I need to read some more information but i tink you will lose the data if you run mkfs.xfs (for example you will get a new inode table).

however I read photorec may recover some files even if fs is missing