[Seagate] USB SSD SERIOUS issues!
1 Attachment(s)
This Seagate 1.82TiB USB SSD, is somewhy untouchable at all (any partitions touched are going to be I/O error), unmountable (ext4 partitions), even though uncheckable (e2fsck), and always disconnects somewhy
|
You may need to provide more details to get help. What I get from your post is that you have a new SSD which has multiple partitions with at least one having an ext4 filesystem and that you get I/O error when performing some function. You also make a comment about them being unmountable and that you cannot run a fs check.
How many partitions? Did you create them? Are they all ext4? What exactly were you attempting to do that gave you an I/O error. How did you try to mount any of these partitions, exact command and output? How did you run fsck and which parameters? |
1 Attachment(s)
And i’m waiting for capturing its GPartEd screenshots, but miserably it’s too instant to be crashed, but too long to be notified again after re-plugging from the last crashes, and the needed screenshots are below ...
Attempting to run E2FSCK still gets those partitions crashed somewhy, uncheckable at all, otherwise to be crashed then to be re-plugged, then finally every times attempting to run E2FSCK is getting them crashed somewhy, before being checkable. Quote:
|
Distro is Artix-runit with kernel 5.6.14, GPartEd edition is 1.1.0-1, desktop is Plasma 5.18.5 with Frameworks 5.70 and Qt 5.14.2
|
Code:
[hd_scania@hd-scania ~]$ sudo gdisk -l /dev/sdc |
And I have FOUR more USB drives, one is WD 1.82T USB mechanical drive, THREE are at largest 596GiB 2.5’’ formerly internal SSD’s to be connected again over USB ...
But NONE THOSE above drives are suffering like this |
What does sudo smartctl -a /dev/sdc say about the drive's health?
Are you sure this is an SSD? All the Seagate Backup Slim drives I've seen so far have been mechanical drives. And if it's one of the infamous "Rosewood" drives... |
Miserably, NO SMART data are available.
Code:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.6.14-artix1-1] (local build) |
2 Attachment(s)
GSMARTcontrol shows that drive to be everything ‘‘unknown’’, as for /dev/sdb
With compared from the normal internal SSD named /dev/sda |
First, you said the drive was /dev/sdc. Now it's apparently /dev/sdb. Which is it?
Did you run smartctl -a on the right device? |
That was an USB drive sometimes sdb but also sometimes sdc, and there was just ONE device plugged on my laptop.
Quote:
Code:
[hd_scania@hd-scania ~]$ sudo smartctl -a /dev/sdb |
This could be because the drive is behind a USB-to-SATA bridge, but smartctl has quite good support for various chipsets.
The other possibility is that the drive is simply not responding because it's broken. This is a fairly common occurrence with mechanical drives, but perhaps even more so with old and totally worn-out SSDs. What is the exact product name and number of this drive? Because it really sounds a lot like a 2 Tb Seagate Rosewood. |
Quote:
To be fair, unless he has set up persistant device naming, both could be correct on different boots. sdX is assigned dynamically in most cases, not persistently. |
SRD0VN2
Quote:
|
Quote:
If you absolutely need the data back, you should disconnect the drive immediately and contact a professional recovery service. |
All times are GMT -5. The time now is 12:29 AM. |