On 2021-03-15 at 01:51:21 Samuel Sieb wrote:
On 3/14/21 9:36 PM, Erik P. Olsen wrote:
> On 2021-03-14 at 14:58:50 Samuel Sieb wrote:
>
>> On 3/14/21 2:44 PM, Erik P. Olsen wrote:
>>> I've had this 1 TB drive for about 1 year and have been using it
succesfully for
>>> backups of my anf my wife's systems and suddenly yesterday morning I was
unable to
>>> mount it. Neither fdisk nor gparted can see it but lsusb can:
>>>
>>> Bus 002 Device 003: ID 0bc2:ab26 Seagate RSS LLC Backup Plus Slim Portable
Drive 1
>>> TB
>>>
>>> On trying to mount I get this error message:
>>>
>>> mount: /backupdev: cannot read the superblock on /dev/sdc1
>>>
>>> Is the drive a brick or can I perhaps regenerate the superblock somehow?
>>
>> That's a very bad sign. Check the journal to see if it's an I/O error
>> or corruption. Which filesystem is it? What does "file -s /dev/sdc1"
show?
>
> From journal:
>
> blk_update_request: I/O error, dev sdc, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1
> prio class 0 Buffer I/O error on dev sdc, logical block 5, async page read
> sd 4:0:0:0: [sdc] tag#20 timing out command, waited 180s
> sd 4:0:0:0: [sdc] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> cmd_age=201s sd 4:0:0:0: [sdc] tag#20 Sense Key : Not Ready [current]
>
> Filesystem is ext4.
>
> "file -s /dev/sdc1" just hangs, no output, have to close terminal to stop
the hang.
If you waited long enough, it probably would have stopped, but it looks
like every read attempt was taking 180 seconds to timeout. I'm pretty
sure your drive is toast, but you could try taking it out of the case
and connecting it directly to a SATA interface somewhere and see if it
works at all. It should at least timeout faster, I think.
OK, I accept it's now a coaster. The damn box is glued together, no screws, so
it's not
easy to take apart - and not worth the bother :-(
Thanks for your support.
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5