Unmountable: Unsupported or no file system

[sloob]

I had a power failure and one of my disk now says Unmountable: Unsupported or no file system. I've tried replacing the drive and it rebuilds in the same state. unsure how to proceed. I've attached a log.

unraid-diagnostics-20230415-1324.zip

[itimpi]

Have you tried the process for handling Unmountable Disks in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

[sloob]

1 hour ago, itimpi said:

Have you tried the process for handling Unmountable Disks in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

I attempted to, but I do not have the Check Filesystem Status section for that disk. I have it for every other disks but not this one. running the command gives me this error

Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

 

and then runs forever without ever finding anything

[itimpi]

1 minute ago, sloob said:

I attempted to, but I do not have the Check Filesystem Status section for that disk. I have it for every other disks but not this one. running the command gives me this error

Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

 

and then runs forever without ever finding anything

Is the file system explicitly set for that drive (rather than auto)?    If not setting that should make the check option appear.
 

When you say you ran the command, what was the exact command you ran?   Getting it slightly wrong can produce the symptoms you got.

[sloob]

9 minutes ago, itimpi said:

Is the file system explicitly set for that drive (rather than auto)?    If not setting that should make the check option appear.
 

When you say you ran the command, what was the exact command you ran?   Getting it slightly wrong can produce the symptoms you got.

The command I tried was "xfs_repair /dev/md8"

 

Setting the FS did make the section appear! but so far it's doing the same thing:

 

Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

 

It's only been running for a few minutes this time tho, should I let it run for a few hours or it shouldn't take that long?

[itimpi]

10 minutes ago, sloob said:

The command I tried was "xfs_repair /dev/md8"

 

Setting the FS did make the section appear! but so far it's doing the same thing:

 

Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

 

It's only been running for a few minutes this time tho, should I let it run for a few hours or it shouldn't take that long?

OK that command looks correct.    If that command does not find the superblock at the start of the drive it may take it hours to find a copy later on the drive.

[sloob]

Just now, itimpi said:

OK that command looks correct.    If that command does not find the superblock at the start of the drive it may take it hours to find a copy later on the drive.

Ok, I will let it run overnight

[sloob]

15 hours ago, itimpi said:

OK that command looks correct.    If that command does not find the superblock at the start of the drive it may take it hours to find a copy later on the drive.

Alright, it has been running more than 12 hours now and it still hasn't found anything. it now says exiting now.

 

One thing that I should mention it that I can't be 100% sure that disk was every truly part of the array. What happened was I installed the disk to the array (array had 7 disk before, added this one as the 8th) it started to initialize it and I let it run alone and went about my day. I'm not sure I ever saw that disk online, initialized and part of the array. I only remember it saying Unmountable: Unsupported or no file system. so the failure might have occurred while the disk was being initialized.

 

I've posted a new diagnostic

unraid-diagnostics-20230416-0752.zip

[itimpi]

7 minutes ago, sloob said:

Alright, it has been running more than 12 hours now and it still hasn't found anything. it now says exiting now.

 

One thing that I should mention it that I can't be 100% sure that disk was every truly part of the array. What happened was I installed the disk to the array (array had 7 disk before, added this one as the 8th) it started to initialize it and I let it run alone and went about my day. I'm not sure I ever saw that disk online, initialized and part of the array. I only remember it saying Unmountable: Unsupported or no file system. so the failure might have occurred while the disk was being initialized.

 

I've posted a new diagnostic

unraid-diagnostics-20230416-0752.zip 190.13 kB · 0 downloads

What do you mean by ‘initialise’?   Did you mean format?  The drive needs to be formatted once it has been added to the array to create an empty file system.

[sloob]

11 minutes ago, itimpi said:

What do you mean by ‘initialise’?   Did you mean format?  The drive needs to be formatted once it has been added to the array to create an empty file system.

Yes, sorry, format it what I mean.

[sloob]

3 hours ago, itimpi said:

What do you mean by ‘initialise’?   Did you mean format?  The drive needs to be formatted once it has been added to the array to create an empty file system.

Should I format the drive? Is there a way to see if I'll lose data if I do so? I'm guessing if that drive never made it to the array that means it contained no data

[sloob]

Anyone?

[itimpi]

14 hours ago, sloob said:

Should I format the drive?

I do not see what else you can do.

 

14 hours ago, sloob said:

Is there a way to see if I'll lose data if I do so?

If the drive never got formatted then there would be no data to lose.  If it formatted and then something went wrong this is always a possibility but not much you can do about it at this point as far as I can see.

 

Make sure before you do the format that it is only the drive you expect listed as about to be formatted - you do not want another drive which DOES have data on it to be formatted by accident.

[JorgeB]

Are you sure disk8 was ever formatted? It doesn't appear to have a valid filesystem,. post the output of:

blkid

 

[sloob]

13 hours ago, JorgeB said:

Are you sure disk8 was ever formatted? It doesn't appear to have a valid filesystem,. post the output of:

blkid

 

Here is the output

 

/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/sdf1: UUID="c0ee8f00-ac85-4429-b5d8-88d34c051dff" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="fc78c683-3ba7-4102-be1b-c212445fc81b"
/dev/nvme0n1p1: UUID="c18f6710-9ec2-483c-81a6-c7deac32d0ba" UUID_SUB="3874402b-fc82-44bc-bb02-527c75fb804c" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdb1: UUID="7f1e82ce-7080-4992-b551-353df6501f1c" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="1becd917-01"
/dev/sdk1: UUID="a5bd460c-eb00-4f3d-a950-fdf48a2b01df" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="1becd915-01"
/dev/sdi1: UUID="cbec1d86-292e-4613-8a9e-c4e690c89bff" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="1becd91b-01"
/dev/sdg1: UUID="6efb0319-0e15-4c0e-829c-28d0aa0903dc" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="861719a4-b949-36c8-40c8-76be2832510d"
/dev/loop0: TYPE="squashfs"
/dev/sde1: UUID="8be95965-635e-4f81-a519-15adc525b5e2" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="b47a4e39-e902-4b6d-aa04-64cf297a6374"
/dev/sdj1: UUID="3fa58017-2146-498f-a76f-232ce4351270" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="e67564e4-dea8-4690-95e6-6d9baeeec3db"
/dev/md6: UUID="3fa58017-2146-498f-a76f-232ce4351270" BLOCK_SIZE="512" TYPE="xfs"
/dev/md4: UUID="6efb0319-0e15-4c0e-829c-28d0aa0903dc" BLOCK_SIZE="512" TYPE="xfs"
/dev/md2: UUID="cbec1d86-292e-4613-8a9e-c4e690c89bff" BLOCK_SIZE="512" TYPE="xfs"
/dev/md7: UUID="7f1e82ce-7080-4992-b551-353df6501f1c" BLOCK_SIZE="512" TYPE="xfs"
/dev/md5: UUID="c0ee8f00-ac85-4429-b5d8-88d34c051dff" BLOCK_SIZE="512" TYPE="xfs"
/dev/md3: UUID="a5bd460c-eb00-4f3d-a950-fdf48a2b01df" BLOCK_SIZE="512" TYPE="xfs"
/dev/md1: UUID="8be95965-635e-4f81-a519-15adc525b5e2" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdd1: PARTUUID="234fbfeb-63f9-4ce3-a966-de04d57cf69c"
/dev/loop2: UUID="512b0675-05b0-46e2-972f-c7ce0fa5c066" UUID_SUB="37250b6a-f4df-437c-b20a-a2435317c12c" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdc1: PARTUUID="33a77cd4-f4f3-48bd-abca-c8aed03d1d14"
/dev/loop3: UUID="3c98e999-4985-49ef-b99d-7b46dcdddf9e" UUID_SUB="0881c0f6-f8b3-4003-a57c-0b35d1e4d75f" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdh1: PARTUUID="edab0d4b-f755-4f4f-b896-ea4654b155af"

[JorgeB]

Disk8 doesn't have a filesystem, that and the fact that xfs_repair didn't find any superblock suggests it was never formatted after it was added to the array.