Hi all.

I have WD20EARS drive that was previously part of the array. I have now finished updating my array and want to mount this drive in an external enclosure.

The drive is XFS formatted, GPT partition. I am pretty sure the jumper has been removed.

Trying to mount the drive, I am getting:

 

Aug 30 22:27:33 Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdg1' '/mnt/disks/WD20EARS'
Aug 30 22:27:33 Mount of '/dev/sdg1' failed. Error message: mount: wrong fs type, bad option, bad superblock on /dev/sdg1,
missing codepage or helper program, or other error

 

Any ideas? Thanks.

Can you post the output of both:

 

sfdisk -l /dev/sdg

 

blkid /dev/sdg1

 

 

Here you go:

 

root@Toaster:~# sfdisk -l /dev/sdg

Disk /dev/sdg: 1.8 TiB, 2000365289472 bytes, 3906963456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdg1          64 3907029167 3907029104  1.8T 83 Linux
root@Toaster:~#

 

-----------------------------

 

root@Toaster:~# blkid /dev/sdg1
/dev/sdg1: UUID="61c3f227-9211-4994-9ddc-820b92362e7e" TYPE="xfs"
 

As suspected, I removed the jumper when I upgraded the entire array to Unraid 6.

I actually don't need the data on the drive, I'm more curious as to why it can't be read. But at the end of the day I will format the drive as NTFS and use it as a backup.

 

Thanks.

 

Edited August 31, 20178 yr by johnieutah

Everything looks normal, except maybe the physical sector size, I never had any of those WD models with jumper, but aren't they Adavced Format? If yes it should be reported as:

 

Sector size (logical/physical): 512 bytes / 4096 bytes

 

 

No I think it was one of the last non-Advanced Format drives. Hence the need to use a jumper to put the drive in to a particular mode, I think something to do with the starting sector 63/64...

IIRC the jumper was used to have better performance on non aligned OSs, like XP, if it needs the jumper to use sector 64 instead of 63 for better performance then it should be advanced format, if not don't see the point in having it, but like I said never had any so could be wrong.

Apparently some disks report 512, others 4096:

 

https://community.wd.com/t/wd20ears-differences-why/16102/4

 

In that case no idea on why it isn't mounting, I believe @bjp999 had a similar issues with the same disks??

Yes you are correct, that was the reason.

So no jumper is definitely the right way forward.

 

I might just format it is as NTFS with Unassigned Devices...

Just to add, I used this drive as a primary data drive for the last 2 years with no issues whatsoever.

All I've done is yanked it out and put it into an enclosure... I can't imagine the enclosure having any influences, can it?

7 minutes ago, johnieutah said:

I can't imagine the enclosure having any influences, can it?

 

If it's a USB enclosure it can make a difference.

Aye it is. It's a WD Elements desktop drive that I stripped a 5TB blue drive from for the server...

Any ideas?

It may not be the enclosure but try mounting after connecting it on a SATA port.

Sounds very similar to the issue here:

 

2 hours ago, johnnie.black said:

Apparently some disks report 512, others 4096:

 

https://community.wd.com/t/wd20ears-differences-why/16102/4

 

In that case no idea on why it isn't mounting, I believe @bjp999 had a similar issues with the same disks??

 

Not me.

Will I at least be able to format it through Unraid or should I move to my windows laptop?

Cheers.

Not sure but to format NTFS I believe you need to use Windows.

Could it be something to do with the UUID of the enclosure?

I'd previously connected the 5TB elements in the enclosure to pre-clear it.

Now I am re-purposing it for the WD20EARs drive, maybe that is confusing things?!?