4:44 p.m.
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?
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5
4:58 p.m.
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?
11:36 p.m.
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.
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5
3:51 a.m.
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.
10:55 a.m.
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
11:26 a.m.
On Mon, 15 Mar 2021 16:55:01 +0100
Erik P. Olsen wrote:
not
easy to take apart - and not worth the bother :-(
I always take apart old dead disks to retrieve the magnets, allowing
me to kill time by building things like this:
https://tomhorsley.com/hardware/solidoodle/solidoodle-kitchen-mag.html
(an iFixit tool kit comes in handy for the weird screws on disk drives).
11:57 a.m.
On 2021-03-15 at 12:26:49 Tom Horsley wrote:
I always take apart old dead disks to retrieve the magnets
Maybe I should. The disk contains 8 months of backups that I can't get at and has to
be
demolished anyhow - or else my sledgehammer will do it :-)
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5
12:56 p.m.
On Mon, Mar 15, 2021 at 11:58 AM Erik P. Olsen <epodata(a)gmail.com> wrote:
On 2021-03-15 at 12:26:49 Tom Horsley wrote:
> I always take apart old dead disks to retrieve the magnets
Maybe I should. The disk contains 8 months of backups that I can't get at and has to
be
demolished anyhow - or else my sledgehammer will do it :-)
I would take it out of the usb case. It is always possible that
something is wrong with the usb hw and/or power supply and that it
might work directly connected.
The torx/screwdriver tool to disassemble it is $10 or so, and usually
has small allen, standard, and phillips bits also. And once
disassembled destroying the platters is easy.
And the magnets as Tom says have all sorts of uses, they are really
strong magnets.
2:23 p.m.
On Mon, 15 Mar 2021 at 14:56, Roger Heflin <rogerheflin(a)gmail.com> wrote:
On Mon, Mar 15, 2021 at 11:58 AM Erik P. Olsen
<epodata(a)gmail.com> wrote:
>
> On 2021-03-15 at 12:26:49 Tom Horsley wrote:
>
> > I always take apart old dead disks to retrieve the magnets
>
> Maybe I should. The disk contains 8 months of backups that I can't get
at and has to be
> demolished anyhow - or else my sledgehammer will do it :-)
>
I would take it out of the usb case. It is always possible that
something is wrong with the usb hw and/or power supply and that it
might work directly connected.
I agree. The drives are the most reliable component and will often
work fine with a new cable and or USB interface. You may find
some overheated components on the interface board.
--
George N. White III
1:25 p.m.
On Mon, 15 Mar 2021 at 13:27, Tom Horsley <horsley1953(a)gmail.com> wrote:
On Mon, 15 Mar 2021 16:55:01 +0100
Erik P. Olsen wrote:
> not
> easy to take apart - and not worth the bother :-(
I always take apart old dead disks to retrieve the magnets, allowing
me to kill time by building things like this:
https://tomhorsley.com/hardware/solidoodle/solidoodle-kitchen-mag.html
(an iFixit tool kit comes in handy for the weird screws on disk drives).
They are very useful magnets. I keep a couple on the column of the my
drill
press to hold drill bits (the same drill press I use to make holes in
drives
being discarded) and others to hold tuna cans for parts while working on
bikes.
--
George N. White III
5:05 p.m.
On Sun, 14 Mar 2021 22:44:26 +0100
Erik P. Olsen wrote:
Is the drive a brick or can I perhaps regenerate the superblock
somehow?
There are lots of copies of the superblock. I had a drive go bad
like that once and was able to use tools (the names of which I no longer
remember - sorry) to print info about where all the superblock copies
were located, then use mount options to try and mount using each
superblock till I got to one that worked (also mounting read only, of course).
Managed to recover some files, but a lot of the data was as corrupt as the
superblock.
5:45 p.m.
On Sun, Mar 14, 2021 at 4:44 PM Erik P. Olsen <epodata(a)gmail.com> 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?
Run "smartctl --all /dev/sdc" and see what it reports.
11:13 p.m.
On 2021-03-14 at 17:45:27 Roger Heflin wrote:
On Sun, Mar 14, 2021 at 4:44 PM Erik P. Olsen
<epodata(a)gmail.com> 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?
>
Run "smartctl --all /dev/sdc" and see what it reports.
[erik@Erik-PC ~]$ sudo smartctl --all -T verypermissive -s on /dev/sdc
smartctl 7.2 2021-01-17 r5171 [x86_64-linux-5.10.22-200.fc33.x86_64] (local build)
Copyright (C) 2002-20, 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: Mon Mar 15 05:11:16 2021 CET
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.
Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Unknown - Try option -s with argument 'on' to enable it.
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enable failed: scsi error unsupported field in scsi command
Read SMART Data failed: scsi error unsupported field in scsi command
=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error unsupported field in scsi command
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.
Read SMART Error Log failed: scsi error unsupported field in scsi command
Read SMART Self-test Log failed: scsi error unsupported field in scsi command
Selective Self-tests/Logging not supported
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5
3:48 a.m.
On 3/14/21 9:13 PM, Erik P. Olsen wrote:
[erik@Erik-PC ~]$ sudo smartctl --all -T verypermissive -s on
/dev/sdc
smartctl 7.2 2021-01-17 r5171 [x86_64-linux-5.10.22-200.fc33.x86_64] (local build)
Copyright (C) 2002-20, 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: Mon Mar 15 05:11:16 2021 CET
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.
Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Unknown - Try option -s with argument 'on' to enable it.
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enable failed: scsi error unsupported field in scsi command
smartctl doesn't work well on USB attached drives.
6:40 a.m.
On Mon, 15 Mar 2021 at 05:49, Samuel Sieb <samuel(a)sieb.net> wrote:
smartctl doesn't work well on USB attached drives.
https://www.smartmontools.org/wiki/USB explains the situation.
Smartctl has worked well for me (several years ago) on drives
from LaCie and G-Technologies.
--
George N. White III
8:38 a.m.
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 ...
maybe this might help to get some data/the disk back:
https://www.hdat2.com/
9:40 a.m.
On 2021-03-16 at 13:38:16 elder sixpack13 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 ...
maybe this might help to get some data/the disk back:
https://www.hdat2.com/
Thanks, I'll look into this possibility.
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5
9:51 a.m.
On 2021-03-16 at 15:40:23 Erik P. Olsen wrote:
On 2021-03-16 at 13:38:16 elder sixpack13 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 ...
>
> maybe this might help to get some data/the disk back:
> https://www.hdat2.com/
Thanks, I'll look into this possibility.
Well, unfortunately for DOS/Windows only.
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5
6:05 p.m.
The dd-rescue package on linux should work just fine. Assuming you
can get the disk to respond. If the disk is taking 180s then the disk
is not responding at all, and even if the disk were responding in 10
sec any rescue program will take longer than anyone will wait. The
software tools will only work if the disk is bad sectors, with the
disk not responding at all that makes it more likely the disk is
simply dead, or the power supply/usb controller is dead.
Best plan would be to get it out of the usb enclosure and see if
smartctl will return anything useful and see if the disk behaves
better.
On Tue, Mar 16, 2021 at 11:46 AM elder sixpack13 <sixpack13(a)online.de> wrote:
>
> > On 2021-03-16 at 15:40:23 Erik P. Olsen wrote:
> ...
> > Well, unfortunately for DOS/Windows only.
>
> there are small iso's (~10 MB).
> I guess mediawriter should be able to put that on an usb stick too or a cd-writer on
an cd.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
6:49 p.m.
On Tue, 16 Mar 2021, Roger Heflin wrote:
Best plan would be to get it out of the usb enclosure and see if
smartctl will return anything useful and see if the disk behaves
better.
Another USB enclosure might work.
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
-- someeecards
10:13 a.m.
The dd-rescue package on linux should work just fine. Assuming you
can get the disk to respond. If the disk is taking 180s then the disk
is not responding at all, and even if the disk were responding in 10
sec any rescue program will take longer than anyone will wait. The
software tools will only work if the disk is bad sectors, with the
disk not responding at all that makes it more likely the disk is
simply dead, or the power supply/usb controller is dead.
Best plan would be to get it out of the usb enclosure and see if
smartctl will return anything useful and see if the disk behaves
better.
well, when it's dead, it might be dead for smartctl command's too....
No ?
;-)
11:10 a.m.
On 2021-03-19 at 15:13:10 elder sixpack13 wrote:
well, when it's dead, it might be dead for smartctl command's too....
No ?
;-)
The disk is stone dead and now it's demolished :-(
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5
1135
days inactive
1140
days old
22 comments
7 participants
participants (7)
-
elder sixpack13 -
Erik P. Olsen -
George N. White III -
Michael Hennebry -
Roger Heflin -
Samuel Sieb -
Tom Horsley