TheBackShed.com

Forum Index : Microcontroller and PC projects : LINUX: Volume issues....

Author

Message

Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9059

Posted: 08:08am 18 Oct 2021

Copy link to clipboard

Print this post

Hi all.

1) 2TB ext4 volume, perfectly accessible, e2fsck -f /dev/sdd1 completes without any errors at all.

2) Move this volume OUT of the PC, and plop it into an external USB3 dock.

3) Linux REFUSES to ACCESS it at all, no matter what. I CAN see the drive in disks, but as an unformatted 2TB volume, which I know is wrong.

Not being dumb enough to just reformat the volume, I put it back in the Linux PC, and it can be accessed fine.

So, my question is: HOW MANY USB3 EXTERNAL DRIVE DOCKS are actually Linux aware?
It would seem I have one that flatly refuses to talk to Linux volumes.
It can see Windoze volumes just fine - even if I plop one into it under Linux, it sees it as an NTFS volume, but the ext4 drive from the Linux PC - "Sorry, I can't see you. :("

Anyone else seen this?

Smoke makes things work. When the smoke gets out, it stops!

JohnS
Guru

Joined: 18/11/2011
Location: United Kingdom
Posts: 3650

Posted: 09:21am 18 Oct 2021

Copy link to clipboard

Print this post

I don't have any such docks but maybe dmesg when you plug it in will help?

John

Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9059

Posted: 07:56am 19 Oct 2021

Copy link to clipboard

Print this post

I tried the same dock under Linux Mint, but the same result.
The system DOES see the drive, but as an unformatted 2TB volume.

The drive is an WD Red NAS drive with "NASware 3.0" firmware.
Could it be possible that these drives simply don't support or allow connection to a dock or other USB adaptor, and that they MUST be connected to a SATA host on a mainboard?

That's about all I can think of now.

Smoke makes things work. When the smoke gets out, it stops!

JohnS
Guru

Joined: 18/11/2011
Location: United Kingdom
Posts: 3650

Posted: 04:12pm 20 Oct 2021

Copy link to clipboard

Print this post

I can't see why (or why not - sorry).

What does dmesg show?

After plugging thee drive in you can do something like
dmesg | tail -12

just to get the few lines about the drive.

I've more ideas but they depend on that...

John
Edited 2021-10-21 02:13 by JohnS

Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9059

Posted: 07:16am 21 Oct 2021

Copy link to clipboard

Print this post

Hi John.

Thanks for your continued interest.
I would have posted the results of a dmesg, but as of tonight, I built a new temporary Puppy Linux Bionic x64 box, connected the problem drive, and Puppy sees it just fine, so I am in the process of copying everything from it, to the new 4TB drive in another server box.

Once complete, I can certainly put the drive back into an external dock, and run that command and see what is reported.

Smoke makes things work. When the smoke gets out, it stops!

JohnS
Guru

Joined: 18/11/2011
Location: United Kingdom
Posts: 3650

Posted: 07:59am 21 Oct 2021

Copy link to clipboard

Print this post

Hey no worries - especially if it's working :)

John

Print this page

To reply to this topic, you need to log in.