[Seagate] USB SSD SERIOUS issues!

hd_scania · 05-24-2020, 05:09 AM

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

yancek · 05-24-2020, 05:27 AM

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?

hd_scania · 05-24-2020, 05:48 AM

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:

Originally Posted by yancek

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?

hd_scania · 05-24-2020, 05:50 AM

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

hd_scania · 05-24-2020, 05:52 AM

Code:

[hd_scania@hd-scania ~]$ sudo gdisk -l /dev/sdc
GPT fdisk (gdisk) version 1.0.5
Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 3907029167 sectors, 1.82 TiB
Model: BUP Slim        
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 0C5548F8-0618-4138-A088-C2F86448D29B
Partition table is held up to 128 entries
Main partition table is begun at sector 2 and is ended at sector 33
First usable sector is 34, last usable sector is 3907029133
Partitions will be aligned on 8-sector boundaries
Total free space is 6 sectors (3.0 KiB)
Number  Start (sector)    End (sector)  Size       Code  Name
   1              40       805306407   384.0 GiB   8300  
   2       805306408      2550136871   832.0 GiB   0700  cn1drv
   3      2550136872      3907029133   647.0 GiB   8300  
[hd_scania@hd-scania ~]$

hd_scania · 05-24-2020, 06:02 AM

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

Ser Olmy · 05-24-2020, 06:34 AM

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...

hd_scania · 05-24-2020, 06:53 AM

Miserably, NO SMART data are available.

Code:

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.6.14-artix1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error unsupported field in scsi command
=== START OF INFORMATION SECTION ===
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Sun May 24 19:49:12 2020 HKT
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

hd_scania · 05-24-2020, 07:05 AM

GSMARTcontrol shows that drive to be everything ‘‘unknown’’, as for /dev/sdb
With compared from the normal internal SSD named /dev/sda

Ser Olmy · 05-25-2020, 06:19 AM

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?

hd_scania · 05-26-2020, 06:30 AM

That was an USB drive sometimes sdb but also sometimes sdc, and there was just ONE device plugged on my laptop.

Quote:

Originally Posted by Ser Olmy

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?

Code:

[hd_scania@hd-scania ~]$ sudo smartctl -a /dev/sdb
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.6.14-artix1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error unsupported field in scsi command
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
[hd_scania@hd-scania ~]$ sudo smartctl -a
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.6.14-artix1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
ERROR: smartctl requires a device name as the final command-line argument.
Use smartctl -h to get a usage summary
[hd_scania@hd-scania ~]$

Ser Olmy · 05-26-2020, 12:19 PM

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.

Roken · 05-26-2020, 04:08 PM

Quote:

Originally Posted by Ser Olmy

First, you said the drive was /dev/sdc. Now it's apparently /dev/sdb. Which is it?

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.

hd_scania · 05-27-2020, 08:31 PM

SRD0VN2

Quote:

Originally Posted by Ser Olmy

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.

Ser Olmy · 05-29-2020, 02:07 AM

Quote:

Originally Posted by hd_scania

SRD0VN2

Then it's not an SSD, and you're dealing with a mechanical Seagate drive, most likely one of the infamous Rosewoods.

If you absolutely need the data back, you should disconnect the drive immediately and contact a professional recovery service.