error deluge

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

error deluge

Tom Daly-3
booting Mint 19.3 Cinammon on deskset:


[3.986534] sd 7:0:0:0: [sdb] No Caching mode page found
[3.986583] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[8.947967] ata1.00: exception Emask 0x0 SAct 0x38000 SErr 0x0 action 0x0
[8.948019] ata1.00: irq_stat 0x40000001
[8.948063] ata1.00: failed command: READ FPDMA QUEUED
[8.948111] ata1.00: cmd 60/00:78:00:09:c0/0a:00:01:00:00/40 tag 15 ncq  
dma 1310720 in
[8.948111] res 41/40:00:70:0a:c0/00:0a:01:00:00/00 Emask 0x409 (media  
error)<F>
[8.948173] ata1.00: status {DRDY ERR}
[8.948216] ata1.00: error: {UNC}
[9.034677] blk_update_request: I/O error, dev sda, sector 29362800 op  
0x0:(READ) flags 0x80700 phys_seg 18 prio class 0

this is so far over my head ...

I am a user-level user, would happily drop this into a forum  
somewhere, but all my user info is on the machine I can't get into ...

what to do ???

_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug
Reply | Threaded
Open this post in threaded view
|

Re: error deluge

Rory-9
The {UNC} is not a good sign, stands for "Uncorrectable error" which
implies a bad sector.

https://ata.wiki.kernel.org/index.php/Libata_error_messages#ATA_error_expansion

I'd recommend booting off of another disk, like a usb 'live' image, to
see if all the important stuff is still readable from that disk. If so,
then you can probably save most of your files and start on filesystem
checks, repairs, etc.

These things can be a result of random sector failures but in my
experience once a desktop/laptop disk starts with these kinds of errors
it's days are numbered.

On Sat, 2020-05-16 at 15:08 -0300, [hidden email] wrote:

> booting Mint 19.3 Cinammon on deskset:
>
>
> [3.986534] sd 7:0:0:0: [sdb] No Caching mode page found
> [3.986583] sd 7:0:0:0: [sdb] Assuming drive cache: write through
> [8.947967] ata1.00: exception Emask 0x0 SAct 0x38000 SErr 0x0 action
> 0x0
> [8.948019] ata1.00: irq_stat 0x40000001
> [8.948063] ata1.00: failed command: READ FPDMA QUEUED
> [8.948111] ata1.00: cmd 60/00:78:00:09:c0/0a:00:01:00:00/40 tag 15
> ncq  
> dma 1310720 in
> [8.948111] res 41/40:00:70:0a:c0/00:0a:01:00:00/00 Emask 0x409
> (media  
> error)<F>
> [8.948173] ata1.00: status {DRDY ERR}
> [8.948216] ata1.00: error: {UNC}
> [9.034677] blk_update_request: I/O error, dev sda, sector 29362800
> op  
> 0x0:(READ) flags 0x80700 phys_seg 18 prio class 0
>
> this is so far over my head ...
>
> I am a user-level user, would happily drop this into a forum  
> somewhere, but all my user info is on the machine I can't get into
> ...
>
> what to do ???
>
> _______________________________________________
> nSLUG mailing list
> [hidden email]
> http://nslug.ns.ca/mailman/listinfo/nslug

_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: error deluge

George N. White III
On Sat, 16 May 2020 at 15:23, Rory <[hidden email]> wrote:
The {UNC} is not a good sign, stands for "Uncorrectable error" which
implies a bad sector.

https://ata.wiki.kernel.org/index.php/Libata_error_messages#ATA_error_expansion

I'd recommend booting off of another disk, like a usb 'live' image, to
see if all the important stuff is still readable from that disk. If so,
then you can probably save most of your files and start on filesystem
checks, repairs, etc.

Your priuority should be to get everything important copied to a new drive.
Attempting to repair a dying drive often makes things worse.  If you can't 
get to your important files using a live boot disk, you may still be able copy 
the raw data to a new drive using GNU ddrescue.   Once the data have been 
copied you can attempt to repair the damaged filesystem on the new disk.   
 

These things can be a result of random sector failures but in my
experience once a desktop/laptop disk starts with these kinds of errors
it's days are numbered.

Yes, and sometimes the numbering isn't in days but in hours.

On Sat, 2020-05-16 at 15:08 -0300, [hidden email] wrote:
> booting Mint 19.3 Cinammon on deskset:
>
>
> [3.986534] sd 7:0:0:0: [sdb] No Caching mode page found
> [3.986583] sd 7:0:0:0: [sdb] Assuming drive cache: write through
> [8.947967] ata1.00: exception Emask 0x0 SAct 0x38000 SErr 0x0 action
> 0x0
> [8.948019] ata1.00: irq_stat 0x40000001
> [8.948063] ata1.00: failed command: READ FPDMA QUEUED
> [8.948111] ata1.00: cmd 60/00:78:00:09:c0/0a:00:01:00:00/40 tag 15
> ncq 
> dma 1310720 in
> [8.948111] res 41/40:00:70:0a:c0/00:0a:01:00:00/00 Emask 0x409
> (media 
> error)<F>
> [8.948173] ata1.00: status {DRDY ERR}
> [8.948216] ata1.00: error: {UNC}
> [9.034677] blk_update_request: I/O error, dev sda, sector 29362800
> op 
> 0x0:(READ) flags 0x80700 phys_seg 18 prio class 0
>
> this is so far over my head ...
>
> I am a user-level user, would happily drop this into a forum 
> somewhere, but all my user info is on the machine I can't get into
> ...
>
> what to do ???
>
> _______________________________________________
> nSLUG mailing list
> [hidden email]
> http://nslug.ns.ca/mailman/listinfo/nslug
_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug


--
George N. White III


_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug
Reply | Threaded
Open this post in threaded view
|

Re: error deluge

Joel Maxwell
I have had this before, with a 500GB Seagate Barracuda HDD.

http://nslug.996319.n3.nabble.com/Hard-drive-or-power-supply-td5650.html

Turned out to be a failing power supply, occasionally forcing the HDD
to spin down. I replaced the PSU and even though I shuffled that HDD to
a different (less important) system/role, it remained in use for
another three years. At that point, I sold the HTPC that it was
contained in - fully working.

A very good idea to go for backing up the drive contents immediately.
However, it is as good an idea to do so connected to a different
system.

--
Regards,
Joel Maxuel

On Sat, 2020-05-16 at 18:46 -0300, George N. White III wrote:

> On Sat, 16 May 2020 at 15:23, Rory <[hidden email]> wrote:
> > The {UNC} is not a good sign, stands for "Uncorrectable error"
> > which
> > implies a bad sector.
> >
> > https://ata.wiki.kernel.org/index.php/Libata_error_messages#ATA_error_expansion
> >
> > I'd recommend booting off of another disk, like a usb 'live' image,
> > to
> > see if all the important stuff is still readable from that disk. If
> > so,
> > then you can probably save most of your files and start on
> > filesystem
> > checks, repairs, etc.
>
> Your priuority should be to get everything important copied to a new
> drive.
> Attempting to repair a dying drive often makes things worse.  If you
> can't
> get to your important files using a live boot disk, you may still be
> able copy
> the raw data to a new drive using GNU ddrescue.   Once the data have
> been
> copied you can attempt to repair the damaged filesystem on the new
> disk.  
>  
> > These things can be a result of random sector failures but in my
> > experience once a desktop/laptop disk starts with these kinds of
> > errors
> > it's days are numbered.
>
> Yes, and sometimes the numbering isn't in days but in hours.
> > On Sat, 2020-05-16 at 15:08 -0300, [hidden email] wrote:
> > > booting Mint 19.3 Cinammon on deskset:
> > >
> > >
> > > [3.986534] sd 7:0:0:0: [sdb] No Caching mode page found
> > > [3.986583] sd 7:0:0:0: [sdb] Assuming drive cache: write through
> > > [8.947967] ata1.00: exception Emask 0x0 SAct 0x38000 SErr 0x0
> > action
> > > 0x0
> > > [8.948019] ata1.00: irq_stat 0x40000001
> > > [8.948063] ata1.00: failed command: READ FPDMA QUEUED
> > > [8.948111] ata1.00: cmd 60/00:78:00:09:c0/0a:00:01:00:00/40 tag
> > 15
> > > ncq  
> > > dma 1310720 in
> > > [8.948111] res 41/40:00:70:0a:c0/00:0a:01:00:00/00 Emask 0x409
> > > (media  
> > > error)<F>
> > > [8.948173] ata1.00: status {DRDY ERR}
> > > [8.948216] ata1.00: error: {UNC}
> > > [9.034677] blk_update_request: I/O error, dev sda, sector
> > 29362800
> > > op  
> > > 0x0:(READ) flags 0x80700 phys_seg 18 prio class 0
> > >
> > > this is so far over my head ...
> > >
> > > I am a user-level user, would happily drop this into a forum  
> > > somewhere, but all my user info is on the machine I can't get
> > into
> > > ...
> > >
> > > what to do ???
> > >
> > > _______________________________________________
> > > nSLUG mailing list
> > > [hidden email]
> > > http://nslug.ns.ca/mailman/listinfo/nslug
> > _______________________________________________
> > nSLUG mailing list
> > [hidden email]
> > http://nslug.ns.ca/mailman/listinfo/nslug
>
>
> _______________________________________________
> nSLUG mailing list
> [hidden email]
> http://nslug.ns.ca/mailman/listinfo/nslug

_______________________________________________
nSLUG mailing list
[hidden email]
http://nslug.ns.ca/mailman/listinfo/nslug