FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 03-05-2011, 02:07 AM
Asif Iqbal
 
Default my laptop sometimes stop responding with disk errors

So I am seeing these errors. Do I need to start thinking about
replacing the disk or can this be fixed. It is a 750G disk. I have
used 67% of it. It is
running ubuntu maverick Linux mylaptop 2.6.35-28-generic #49-Ubuntu
SMP Tue Mar 1 14:39:03 UTC 2011 x86_64 GNU/Linux

[56075.354420] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[56075.354424] ata1.00: irq_stat 0x40000001
[56075.354427] ata1.00: failed command: READ FPDMA QUEUED
[56075.354432] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[56075.354433] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[56075.354436] ata1.00: status: { DRDY ERR }
[56075.354438] ata1.00: error: { UNC }
[56075.354440] ata1.00: failed command: READ FPDMA QUEUED
[56075.354444] ata1.00: cmd 60/08:08:a0:99:ad/00:00:4d:00:00/40 tag 1
ncq 4096 in
[56075.354445] res 41/40:00:00:00:00/00:00:00:00:00/00 Emask
0x9 (media error)
[56075.354448] ata1.00: status: { DRDY ERR }
[56075.354450] ata1.00: error: { UNC }
[56075.362640] ata1.00: configured for UDMA/133
[56075.362650] ata1: EH complete
[56078.176482] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[56078.176486] ata1.00: irq_stat 0x40000008
[56078.176489] ata1.00: failed command: READ FPDMA QUEUED
[56078.176495] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
ncq 4096 in
[56078.176496] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[56078.176499] ata1.00: status: { DRDY ERR }
[56078.176500] ata1.00: error: { UNC }
[56078.184339] ata1.00: configured for UDMA/133
[56078.184350] ata1: EH complete
[56080.987476] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[56080.987479] ata1.00: irq_stat 0x40000008
[56080.987483] ata1.00: failed command: READ FPDMA QUEUED
[56080.987488] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[56080.987489] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[56080.987491] ata1.00: status: { DRDY ERR }
[56080.987493] ata1.00: error: { UNC }
[56080.995040] ata1.00: configured for UDMA/133
[56080.995051] ata1: EH complete
[56083.798449] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[56083.798454] ata1.00: irq_stat 0x40000008
[56083.798457] ata1.00: failed command: READ FPDMA QUEUED
[56083.798468] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
ncq 4096 in
[56083.798468] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[56083.798477] ata1.00: status: { DRDY ERR }
[56083.798479] ata1.00: error: { UNC }
[56083.806781] ata1.00: configured for UDMA/133
[56083.806792] ata1: EH complete
[56086.620567] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[56086.620571] ata1.00: irq_stat 0x40000008
[56086.620574] ata1.00: failed command: READ FPDMA QUEUED
[56086.620579] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[56086.620581] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[56086.620583] ata1.00: status: { DRDY ERR }
[56086.620585] ata1.00: error: { UNC }
[56086.628502] ata1.00: configured for UDMA/133
[56086.628513] ata1: EH complete
[56089.431583] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[56089.431587] ata1.00: irq_stat 0x40000008
[56089.431590] ata1.00: failed command: READ FPDMA QUEUED
[56089.431595] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
ncq 4096 in
[56089.431596] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[56089.431599] ata1.00: status: { DRDY ERR }
[56089.431601] ata1.00: error: { UNC }
[56089.439186] ata1.00: configured for UDMA/133
[56089.439200] sd 0:0:0:0: [sda] Unhandled sense code
[56089.439202] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[56089.439205] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
[56089.439210] Descriptor sense data with sense descriptors (in hex):
[56089.439211] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[56089.439219] 0d 9d e4 f0
[56089.439222] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error -
auto reallocate failed
[56089.439227] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 0d 9d e4 f0 00 00 08 00
[56089.439234] end_request: I/O error, dev sda, sector 228451568
[56089.439249] ata1: EH complete
[56385.901315] Skipping EDID probe due to cached edid
[57122.196683] lo: Disabled Privacy Extensions
[57582.997072] show_signal_msg: 39 callbacks suppressed
[57582.997077] chrome[10824]: segfault at 800000007 ip
00007f10454b3178 sp 00007fff2df3bfe8 error 4 in
libpdf.so[7f10453d6000+11d1000]
[59014.253862] Skipping EDID probe due to cached edid
[59317.191308] Skipping EDID probe due to cached edid
[60314.662221] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[60314.662225] ata1.00: irq_stat 0x40000001
[60314.662229] ata1.00: failed command: READ FPDMA QUEUED
[60314.662234] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[60314.662235] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[60314.662238] ata1.00: status: { DRDY ERR }
[60314.662239] ata1.00: error: { UNC }
[60314.662241] ata1.00: failed command: READ FPDMA QUEUED
[60314.662246] ata1.00: cmd 60/08:08:88:a1:ad/00:00:4d:00:00/40 tag 1
ncq 4096 in
[60314.662247] res 41/40:00:00:00:00/00:00:00:00:00/00 Emask
0x9 (media error)
[60314.662250] ata1.00: status: { DRDY ERR }
[60314.662251] ata1.00: error: { UNC }
[60314.670247] ata1.00: configured for UDMA/133
[60314.670257] ata1: EH complete
[60317.473171] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[60317.473175] ata1.00: irq_stat 0x40000008
[60317.473178] ata1.00: failed command: READ FPDMA QUEUED
[60317.473183] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
ncq 4096 in
[60317.473184] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[60317.473187] ata1.00: status: { DRDY ERR }
[60317.473189] ata1.00: error: { UNC }
[60317.480978] ata1.00: configured for UDMA/133
[60317.480988] ata1: EH complete
[60320.295297] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[60320.295300] ata1.00: irq_stat 0x40000008
[60320.295304] ata1.00: failed command: READ FPDMA QUEUED
[60320.295309] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[60320.295310] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[60320.295312] ata1.00: status: { DRDY ERR }
[60320.295314] ata1.00: error: { UNC }
[60320.303732] ata1.00: configured for UDMA/133
[60320.303741] ata1: EH complete
[60323.106311] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[60323.106315] ata1.00: irq_stat 0x40000008
[60323.106318] ata1.00: failed command: READ FPDMA QUEUED
[60323.106324] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
ncq 4096 in
[60323.106330] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[60323.106333] ata1.00: status: { DRDY ERR }
[60323.106334] ata1.00: error: { UNC }
[60323.114472] ata1.00: configured for UDMA/133
[60323.114481] ata1: EH complete
[60325.917304] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[60325.917308] ata1.00: irq_stat 0x40000008
[60325.917311] ata1.00: failed command: READ FPDMA QUEUED
[60325.917317] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[60325.917318] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[60325.917320] ata1.00: status: { DRDY ERR }
[60325.917322] ata1.00: error: { UNC }
[60325.925174] ata1.00: configured for UDMA/133
[60325.925184] ata1: EH complete
[60328.728404] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
[60328.728408] ata1.00: irq_stat 0x40000008
[60328.728411] ata1.00: failed command: READ FPDMA QUEUED
[60328.728417] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
ncq 4096 in
[60328.728418] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[60328.728426] ata1.00: status: { DRDY ERR }
[60328.728427] ata1.00: error: { UNC }
[60328.736901] ata1.00: configured for UDMA/133
[60328.736915] sd 0:0:0:0: [sda] Unhandled sense code
[60328.736917] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[60328.736921] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
[60328.736925] Descriptor sense data with sense descriptors (in hex):
[60328.736927] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[60328.736935] 0d 9d e4 f0
[60328.736938] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error -
auto reallocate failed
[60328.736942] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 0d 9d e4 f0 00 00 08 00
[60328.736949] end_request: I/O error, dev sda, sector 228451568
[60328.736963] ata1: EH complete
[60604.373268] lo: Disabled Privacy Extensions
[61161.104635] npviewer.bin[7837]: segfault at 418 ip 00000000f60a1d16
sp 00000000ffb2b9f8 error 6 in libflashplayer.so[f5e34000+b5f000]
[61303.328324] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[61303.328328] ata1.00: irq_stat 0x40000008
[61303.328331] ata1.00: failed command: READ FPDMA QUEUED
[61303.328336] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[61303.328337] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[61303.328340] ata1.00: status: { DRDY ERR }
[61303.328342] ata1.00: error: { UNC }
[61303.336415] ata1.00: configured for UDMA/133
[61303.336423] ata1: EH complete
[61306.128174] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[61306.128178] ata1.00: irq_stat 0x40000008
[61306.128182] ata1.00: failed command: READ FPDMA QUEUED
[61306.128187] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[61306.128188] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[61306.128191] ata1.00: status: { DRDY ERR }
[61306.128193] ata1.00: error: { UNC }
[61306.136130] ata1.00: configured for UDMA/133
[61306.136139] ata1: EH complete
[61308.928122] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[61308.928126] ata1.00: irq_stat 0x40000008
[61308.928129] ata1.00: failed command: READ FPDMA QUEUED
[61308.928135] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[61308.928136] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[61308.928138] ata1.00: status: { DRDY ERR }
[61308.928140] ata1.00: error: { UNC }
[61308.935838] ata1.00: configured for UDMA/133
[61308.935847] ata1: EH complete
[61311.728046] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[61311.728050] ata1.00: irq_stat 0x40000008
[61311.728054] ata1.00: failed command: READ FPDMA QUEUED
[61311.728059] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[61311.728060] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[61311.728063] ata1.00: status: { DRDY ERR }
[61311.728064] ata1.00: error: { UNC }
[61311.735564] ata1.00: configured for UDMA/133
[61311.735573] ata1: EH complete
[61314.527888] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[61314.527892] ata1.00: irq_stat 0x40000008
[61314.527895] ata1.00: failed command: READ FPDMA QUEUED
[61314.527900] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[61314.527901] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[61314.527904] ata1.00: status: { DRDY ERR }
[61314.527906] ata1.00: error: { UNC }
[61314.536276] ata1.00: configured for UDMA/133
[61314.536288] ata1: EH complete
[61317.327795] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[61317.327799] ata1.00: irq_stat 0x40000008
[61317.327802] ata1.00: failed command: READ FPDMA QUEUED
[61317.327807] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
ncq 4096 in
[61317.327808] res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
0x409 (media error) <F>
[61317.327811] ata1.00: status: { DRDY ERR }
[61317.327813] ata1.00: error: { UNC }
[61317.336221] ata1.00: configured for UDMA/133
[61317.336237] sd 0:0:0:0: [sda] Unhandled sense code
[61317.336239] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[61317.336242] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
[61317.336247] Descriptor sense data with sense descriptors (in hex):
[61317.336248] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[61317.336256] 0d 9d e4 f0
[61317.336259] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error -
auto reallocate failed
[61317.336264] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 0d 9d e4 f0 00 00 08 00
[61317.336271] end_request: I/O error, dev sda, sector 228451568
[61317.336292] ata1: EH complete


--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 03-05-2011, 02:11 AM
Asif Iqbal
 
Default my laptop sometimes stop responding with disk errors

On Fri, Mar 4, 2011 at 10:07 PM, Asif Iqbal <vadud3@gmail.com> wrote:
> So I am seeing these errors. Do I need to start thinking about
> replacing the disk or can this be fixed. It is a 750G disk. I have
> used 67% of it. It is
> running ubuntu maverick Linux mylaptop 2.6.35-28-generic #49-Ubuntu
> SMP Tue Mar 1 14:39:03 UTC 2011 x86_64 GNU/Linux
>
> [56075.354420] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [56075.354424] ata1.00: irq_stat 0x40000001
> [56075.354427] ata1.00: failed command: READ FPDMA QUEUED
> [56075.354432] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [56075.354433] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [56075.354436] ata1.00: status: { DRDY ERR }
> [56075.354438] ata1.00: error: { UNC }
> [56075.354440] ata1.00: failed command: READ FPDMA QUEUED
> [56075.354444] ata1.00: cmd 60/08:08:a0:99:ad/00:00:4d:00:00/40 tag 1
> ncq 4096 in
> [56075.354445] * * * * *res 41/40:00:00:00:00/00:00:00:00:00/00 Emask
> 0x9 (media error)
> [56075.354448] ata1.00: status: { DRDY ERR }
> [56075.354450] ata1.00: error: { UNC }
> [56075.362640] ata1.00: configured for UDMA/133
> [56075.362650] ata1: EH complete
> [56078.176482] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [56078.176486] ata1.00: irq_stat 0x40000008
> [56078.176489] ata1.00: failed command: READ FPDMA QUEUED
> [56078.176495] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
> ncq 4096 in
> [56078.176496] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [56078.176499] ata1.00: status: { DRDY ERR }
> [56078.176500] ata1.00: error: { UNC }
> [56078.184339] ata1.00: configured for UDMA/133
> [56078.184350] ata1: EH complete
> [56080.987476] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [56080.987479] ata1.00: irq_stat 0x40000008
> [56080.987483] ata1.00: failed command: READ FPDMA QUEUED
> [56080.987488] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [56080.987489] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [56080.987491] ata1.00: status: { DRDY ERR }
> [56080.987493] ata1.00: error: { UNC }
> [56080.995040] ata1.00: configured for UDMA/133
> [56080.995051] ata1: EH complete
> [56083.798449] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [56083.798454] ata1.00: irq_stat 0x40000008
> [56083.798457] ata1.00: failed command: READ FPDMA QUEUED
> [56083.798468] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
> ncq 4096 in
> [56083.798468] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [56083.798477] ata1.00: status: { DRDY ERR }
> [56083.798479] ata1.00: error: { UNC }
> [56083.806781] ata1.00: configured for UDMA/133
> [56083.806792] ata1: EH complete
> [56086.620567] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [56086.620571] ata1.00: irq_stat 0x40000008
> [56086.620574] ata1.00: failed command: READ FPDMA QUEUED
> [56086.620579] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [56086.620581] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [56086.620583] ata1.00: status: { DRDY ERR }
> [56086.620585] ata1.00: error: { UNC }
> [56086.628502] ata1.00: configured for UDMA/133
> [56086.628513] ata1: EH complete
> [56089.431583] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [56089.431587] ata1.00: irq_stat 0x40000008
> [56089.431590] ata1.00: failed command: READ FPDMA QUEUED
> [56089.431595] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
> ncq 4096 in
> [56089.431596] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [56089.431599] ata1.00: status: { DRDY ERR }
> [56089.431601] ata1.00: error: { UNC }
> [56089.439186] ata1.00: configured for UDMA/133
> [56089.439200] sd 0:0:0:0: [sda] Unhandled sense code
> [56089.439202] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [56089.439205] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
> [56089.439210] Descriptor sense data with sense descriptors (in hex):
> [56089.439211] * * * * 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
> [56089.439219] * * * * 0d 9d e4 f0
> [56089.439222] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error -
> auto reallocate failed
> [56089.439227] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 0d 9d e4 f0 00 00 08 00
> [56089.439234] end_request: I/O error, dev sda, sector 228451568
> [56089.439249] ata1: EH complete
> [56385.901315] Skipping EDID probe due to cached edid
> [57122.196683] lo: Disabled Privacy Extensions
> [57582.997072] show_signal_msg: 39 callbacks suppressed
> [57582.997077] chrome[10824]: segfault at 800000007 ip
> 00007f10454b3178 sp 00007fff2df3bfe8 error 4 in
> libpdf.so[7f10453d6000+11d1000]
> [59014.253862] Skipping EDID probe due to cached edid
> [59317.191308] Skipping EDID probe due to cached edid
> [60314.662221] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [60314.662225] ata1.00: irq_stat 0x40000001
> [60314.662229] ata1.00: failed command: READ FPDMA QUEUED
> [60314.662234] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [60314.662235] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [60314.662238] ata1.00: status: { DRDY ERR }
> [60314.662239] ata1.00: error: { UNC }
> [60314.662241] ata1.00: failed command: READ FPDMA QUEUED
> [60314.662246] ata1.00: cmd 60/08:08:88:a1:ad/00:00:4d:00:00/40 tag 1
> ncq 4096 in
> [60314.662247] * * * * *res 41/40:00:00:00:00/00:00:00:00:00/00 Emask
> 0x9 (media error)
> [60314.662250] ata1.00: status: { DRDY ERR }
> [60314.662251] ata1.00: error: { UNC }
> [60314.670247] ata1.00: configured for UDMA/133
> [60314.670257] ata1: EH complete
> [60317.473171] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [60317.473175] ata1.00: irq_stat 0x40000008
> [60317.473178] ata1.00: failed command: READ FPDMA QUEUED
> [60317.473183] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
> ncq 4096 in
> [60317.473184] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [60317.473187] ata1.00: status: { DRDY ERR }
> [60317.473189] ata1.00: error: { UNC }
> [60317.480978] ata1.00: configured for UDMA/133
> [60317.480988] ata1: EH complete
> [60320.295297] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [60320.295300] ata1.00: irq_stat 0x40000008
> [60320.295304] ata1.00: failed command: READ FPDMA QUEUED
> [60320.295309] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [60320.295310] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [60320.295312] ata1.00: status: { DRDY ERR }
> [60320.295314] ata1.00: error: { UNC }
> [60320.303732] ata1.00: configured for UDMA/133
> [60320.303741] ata1: EH complete
> [60323.106311] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [60323.106315] ata1.00: irq_stat 0x40000008
> [60323.106318] ata1.00: failed command: READ FPDMA QUEUED
> [60323.106324] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
> ncq 4096 in
> [60323.106330] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [60323.106333] ata1.00: status: { DRDY ERR }
> [60323.106334] ata1.00: error: { UNC }
> [60323.114472] ata1.00: configured for UDMA/133
> [60323.114481] ata1: EH complete
> [60325.917304] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [60325.917308] ata1.00: irq_stat 0x40000008
> [60325.917311] ata1.00: failed command: READ FPDMA QUEUED
> [60325.917317] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [60325.917318] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [60325.917320] ata1.00: status: { DRDY ERR }
> [60325.917322] ata1.00: error: { UNC }
> [60325.925174] ata1.00: configured for UDMA/133
> [60325.925184] ata1: EH complete
> [60328.728404] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> [60328.728408] ata1.00: irq_stat 0x40000008
> [60328.728411] ata1.00: failed command: READ FPDMA QUEUED
> [60328.728417] ata1.00: cmd 60/08:08:f0:e4:9d/00:00:0d:00:00/40 tag 1
> ncq 4096 in
> [60328.728418] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [60328.728426] ata1.00: status: { DRDY ERR }
> [60328.728427] ata1.00: error: { UNC }
> [60328.736901] ata1.00: configured for UDMA/133
> [60328.736915] sd 0:0:0:0: [sda] Unhandled sense code
> [60328.736917] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [60328.736921] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
> [60328.736925] Descriptor sense data with sense descriptors (in hex):
> [60328.736927] * * * * 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
> [60328.736935] * * * * 0d 9d e4 f0
> [60328.736938] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error -
> auto reallocate failed
> [60328.736942] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 0d 9d e4 f0 00 00 08 00
> [60328.736949] end_request: I/O error, dev sda, sector 228451568
> [60328.736963] ata1: EH complete
> [60604.373268] lo: Disabled Privacy Extensions
> [61161.104635] npviewer.bin[7837]: segfault at 418 ip 00000000f60a1d16
> sp 00000000ffb2b9f8 error 6 in libflashplayer.so[f5e34000+b5f000]
> [61303.328324] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> [61303.328328] ata1.00: irq_stat 0x40000008
> [61303.328331] ata1.00: failed command: READ FPDMA QUEUED
> [61303.328336] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [61303.328337] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [61303.328340] ata1.00: status: { DRDY ERR }
> [61303.328342] ata1.00: error: { UNC }
> [61303.336415] ata1.00: configured for UDMA/133
> [61303.336423] ata1: EH complete
> [61306.128174] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> [61306.128178] ata1.00: irq_stat 0x40000008
> [61306.128182] ata1.00: failed command: READ FPDMA QUEUED
> [61306.128187] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [61306.128188] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [61306.128191] ata1.00: status: { DRDY ERR }
> [61306.128193] ata1.00: error: { UNC }
> [61306.136130] ata1.00: configured for UDMA/133
> [61306.136139] ata1: EH complete
> [61308.928122] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> [61308.928126] ata1.00: irq_stat 0x40000008
> [61308.928129] ata1.00: failed command: READ FPDMA QUEUED
> [61308.928135] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [61308.928136] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [61308.928138] ata1.00: status: { DRDY ERR }
> [61308.928140] ata1.00: error: { UNC }
> [61308.935838] ata1.00: configured for UDMA/133
> [61308.935847] ata1: EH complete
> [61311.728046] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> [61311.728050] ata1.00: irq_stat 0x40000008
> [61311.728054] ata1.00: failed command: READ FPDMA QUEUED
> [61311.728059] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [61311.728060] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [61311.728063] ata1.00: status: { DRDY ERR }
> [61311.728064] ata1.00: error: { UNC }
> [61311.735564] ata1.00: configured for UDMA/133
> [61311.735573] ata1: EH complete
> [61314.527888] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> [61314.527892] ata1.00: irq_stat 0x40000008
> [61314.527895] ata1.00: failed command: READ FPDMA QUEUED
> [61314.527900] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [61314.527901] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [61314.527904] ata1.00: status: { DRDY ERR }
> [61314.527906] ata1.00: error: { UNC }
> [61314.536276] ata1.00: configured for UDMA/133
> [61314.536288] ata1: EH complete
> [61317.327795] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> [61317.327799] ata1.00: irq_stat 0x40000008
> [61317.327802] ata1.00: failed command: READ FPDMA QUEUED
> [61317.327807] ata1.00: cmd 60/08:00:f0:e4:9d/00:00:0d:00:00/40 tag 0
> ncq 4096 in
> [61317.327808] * * * * *res 41/40:00:f0:e4:9d/00:00:0d:00:00/40 Emask
> 0x409 (media error) <F>
> [61317.327811] ata1.00: status: { DRDY ERR }
> [61317.327813] ata1.00: error: { UNC }
> [61317.336221] ata1.00: configured for UDMA/133
> [61317.336237] sd 0:0:0:0: [sda] Unhandled sense code
> [61317.336239] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [61317.336242] sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
> [61317.336247] Descriptor sense data with sense descriptors (in hex):
> [61317.336248] * * * * 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
> [61317.336256] * * * * 0d 9d e4 f0
> [61317.336259] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error -
> auto reallocate failed
> [61317.336264] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 0d 9d e4 f0 00 00 08 00
> [61317.336271] end_request: I/O error, dev sda, sector 228451568
> [61317.336292] ata1: EH complete

I am using ext4. Here are disk and fs layout

$ sudo fdisk -l

Disk /dev/sda: 750 GB, 750153761280 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 88249 708860061 83 Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sda2 88249 91202 23719972 5 Extended
Warning: Partition 2 does not end on cylinder boundary.
/dev/sda5 88249 91202 23719972 82 Linux swap
Warning: Partition 5 does not end on cylinder boundary.

$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
(rw,noexec,nosuid,nodev)
/home/iqbala/.Private on /home/iqbala/Private type ecryptfs
(ecryptfs_sig=67fb6de4529a0521,ecryptfs_fnek_sig=4 b36f304d413d295,ecryptfs_cipher=aes,ecryptfs_key_b ytes=16,ecryptfs_unlink_sigs)
gvfs-fuse-daemon on /home/iqbala/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=iqbala)

>
>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
>



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 03-05-2011, 02:31 AM
MR ZenWiz
 
Default my laptop sometimes stop responding with disk errors

On Fri, Mar 4, 2011 at 7:11 PM, Asif Iqbal <vadud3@gmail.com> wrote:
> On Fri, Mar 4, 2011 at 10:07 PM, Asif Iqbal <vadud3@gmail.com> wrote:
>> So I am seeing these errors. Do I need to start thinking about
>> replacing the disk or can this be fixed. It is a 750G disk. I have
>> used 67% of it. It is
>> running ubuntu maverick Linux mylaptop 2.6.35-28-generic #49-Ubuntu
>> SMP Tue Mar 1 14:39:03 UTC 2011 x86_64 GNU/Linux
>>
:
>
> I am using ext4. Here are disk and fs layout
>
> $ sudo fdisk -l
>
> Disk /dev/sda: 750 GB, 750153761280 bytes
> 255 heads, 63 sectors/track, 91201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>

Unless you can isolate the problem to a cable or some other hardware
flaw that would be cheaper to fix, I'd recommend a new drive -
a.s.a.p.

Sometimes errors like that are bogus, but you can't count on it. I
have a Seagate that was reporting 4294967295 bad sectors every 30
minutes until I retired it, but Seagate's stools showed that there
were in fact no errors on the drive, and that number just happens to
be 0xffffffff, so I didn't really believe it, but I also didn't trust
it - for two years. AFAIK it's still working flawlessly....

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 03-05-2011, 03:16 AM
Jeff Lane
 
Default my laptop sometimes stop responding with disk errors

On Fri, Mar 4, 2011 at 22:07, Asif Iqbal <vadud3@gmail.com> wrote:
> So I am seeing these errors. Do I need to start thinking about
> replacing the disk or can this be fixed. It is a 750G disk. I have
> used 67% of it. It is
> running ubuntu maverick Linux mylaptop 2.6.35-28-generic #49-Ubuntu
> SMP Tue Mar 1 14:39:03 UTC 2011 x86_64 GNU/Linux

Yep... Probably time to start considering a new hard disk.

You can test the hard disk (or you SHOULD be able to) using SMART...

do this:

sudo smartctl --all /dev/sda

and see what that tells you about the health of your hard disk...

If you don't happen to have smartctl installed, you can install it like so:

sudo apt-get install smartmontools

Either way, you should start backing up your data NOW.

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 03-05-2011, 06:04 AM
Asif Iqbal
 
Default my laptop sometimes stop responding with disk errors

On Fri, Mar 4, 2011 at 11:16 PM, Jeff Lane <jeff@ubuntu.com> wrote:
> On Fri, Mar 4, 2011 at 22:07, Asif Iqbal <vadud3@gmail.com> wrote:
>> So I am seeing these errors. Do I need to start thinking about
>> replacing the disk or can this be fixed. It is a 750G disk. I have
>> used 67% of it. It is
>> running ubuntu maverick Linux mylaptop 2.6.35-28-generic #49-Ubuntu
>> SMP Tue Mar 1 14:39:03 UTC 2011 x86_64 GNU/Linux
>
> Yep... Probably time to start considering a new hard disk.
>
> You can test the hard disk (or you SHOULD be able to) using SMART...
>
> do this:
>
> sudo smartctl --all /dev/sda
>
> and see what that tells you about the health of your hard disk...

$ sudo smartctl --all /dev/sda shows PASSED

smartctl 5.40 2010-03-16 r3077 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model: WDC WD7500BPVT-00HXZT1
Serial Number: WD-WX21A50V9604
Firmware Version: 01.01A01
User Capacity: 750,156,374,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sat Mar 5 02:03:09 2011 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (15960) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 185) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x7035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 167 167 051 Pre-fail
Always - 2097
3 Spin_Up_Time 0x0027 205 205 021 Pre-fail
Always - 733
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 335
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail
Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age
Always - 0
9 Power_On_Hours 0x0032 096 096 000 Old_age
Always - 3477
10 Spin_Retry_Count 0x0032 100 100 000 Old_age
Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 331
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age
Always - 76
193 Load_Cycle_Count 0x0032 200 200 000 Old_age
Always - 2387
194 Temperature_Celsius 0x0022 107 077 000 Old_age
Always - 40
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age
Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age
Always - 1
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age
Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age
Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Short offline Aborted by host 10% 3 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


>
> If you don't happen to have smartctl installed, you can install it like so:
>
> sudo apt-get install smartmontools
>
> Either way, you should start backing up your data NOW.
>
> --
> ubuntu-users mailing list
> ubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 03-05-2011, 01:29 PM
Jeff Lane
 
Default my laptop sometimes stop responding with disk errors

On Sat, Mar 5, 2011 at 02:04, Asif Iqbal <vadud3@gmail.com> wrote:
> $ sudo smartctl --all /dev/sda *shows PASSED

Cool... good for you
So the next thing is filesystem problems... Pick out one of the error
messages you're seeing and do a google search on it (without the
timestamps, obviously):

Such as one of these two:
ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
ata1.00: status: { DRDY ERR }

You'll find all sorts of things going way back to Feisty and Hardy...
In a lot of older cases, this seems to be caused by the CD drive, for
some reason. Or bad cables. In any case, BACK YOUR DATA UP NOW.

You can try booting from the live cd and once you're in, open a
terminal and do this:

Read the man page for badblocks and understand what it's doing and
what the options are:

# man badblocks

MAKE SURE YOU HAVE BACKED UP YOUR DATA!!!

run bad blocks:

# sudo badblocks -n -s /dev/sdaX (where X is the number of the partition)

this should tell you if you have any bad sectors or blocks on the
disk. You can also try running e2fsck on it:

read the man page for e2fsck:

# man e2fsck

and understand what it's doing and what the options are. Run fsck:

# sudo fsck.ext4 /dev/sdaX (where X is the number of the partition)

but keep in mind before doing ANY OF THIS, that you NEED TO BACK YOUR
DATA UP NOW.

It still could be a failing hard disk though... SMART is a good tool
for keeping tabs on HDD health, but it's not guaranteed and may not
show you anything at all until just before the disk actually dies.

Some googling of the above tools and the error messages, as I pointed
out earlier, will show you a LOT about the many different types of
problems that can cause those issues to appear.

Also, did you just upgrade? And did you have these problems BEFORE
you upgraded, or only AFTER you upgraded?

I noticed you're running 2.6.35-28, while I'm still on 2.6.35-25 on
Maverick. Soooo.... I wonder if this is possibly a kernel bug. You
should also probably file a bug against the kernel:

on your system, not from within the live CD environment, open a
terminal and do this:

apport-bug linux

Follow the steps and file the bug. Then read hte bug and make sure
you attach a copy of the dmesg log, syslog, and paste a copy of that
smartctl output you provided here...

Cheers,

Jeff

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 03-05-2011, 05:16 PM
Asif Iqbal
 
Default my laptop sometimes stop responding with disk errors

On Sat, Mar 5, 2011 at 9:29 AM, Jeff Lane <jeff@ubuntu.com> wrote:
> On Sat, Mar 5, 2011 at 02:04, Asif Iqbal <vadud3@gmail.com> wrote:
>> $ sudo smartctl --all /dev/sda *shows PASSED
>
> Cool... good for you
> So the next thing is filesystem problems... Pick out one of the error
> messages you're seeing and do a google search on it (without the
> timestamps, obviously):
>
> Such as one of these two:
> ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> ata1.00: status: { DRDY ERR }
>
> You'll find all sorts of things going way back to Feisty and Hardy...
> In a lot of older cases, this seems to be caused by the CD drive, for
> some reason. *Or bad cables. In any case, BACK YOUR DATA UP NOW.
>
> You can try booting from the live cd and once you're in, open a
> terminal and do this:
>
> Read the man page for badblocks and understand what it's doing and
> what the options are:
>
> # man badblocks
>
> MAKE SURE YOU HAVE BACKED UP YOUR DATA!!!
>
> run bad blocks:
>
> # sudo badblocks -n -s /dev/sdaX (where X is the number of the partition)
>
> this should tell you if you have any bad sectors or blocks on the
> disk. *You can also try running e2fsck on it:
>
> read the man page for e2fsck:
>
> # man e2fsck
>
> and understand what it's doing and what the options are. *Run fsck:
>
> # sudo fsck.ext4 /dev/sdaX (where X is the number of the partition)
>
> but keep in mind before doing ANY OF THIS, that you NEED TO BACK YOUR
> DATA UP NOW.
>
> It still could be a failing hard disk though... SMART is a good tool
> for keeping tabs on HDD health, but it's not guaranteed and may not
> show you anything at all until just before the disk actually dies.
>
> Some googling of the above tools and the error messages, as I pointed
> out earlier, will show you a LOT about the many different types of
> problems that can cause those issues to appear.
>
> Also, did you just upgrade? *And did you have these problems BEFORE
> you upgraded, or only AFTER you upgraded?

only after the kernel upgrade

>
> I noticed you're running 2.6.35-28, while I'm still on 2.6.35-25 on
> Maverick. *Soooo.... I wonder if this is possibly a kernel bug. *You
> should also probably file a bug against the kernel:
>
> on your system, not from within the live CD environment, open a
> terminal and do this:
>
> apport-bug linux
>
> Follow the steps and file the bug. *Then read hte bug and make sure
> you attach a copy of the dmesg log, syslog, and paste a copy of that
> smartctl output you provided here...

thanks a lot for such a detail email.

>
> Cheers,
>
> Jeff
>



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 03-06-2011, 12:26 AM
NoOp
 
Default my laptop sometimes stop responding with disk errors

On 03/05/2011 06:29 AM, Jeff Lane wrote:
> On Sat, Mar 5, 2011 at 02:04, Asif Iqbal <vadud3@gmail.com> wrote:
>> $ sudo smartctl --all /dev/sda shows PASSED
>
> Cool... good for you
> So the next thing is filesystem problems... Pick out one of the error
> messages you're seeing and do a google search on it (without the
> timestamps, obviously):
>
> Such as one of these two:
> ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
> ata1.00: status: { DRDY ERR }
...

Or:

READ FPDMA QUEUED

https://bugs.launchpad.net/ubuntu/+bug/550559
[hdd problems, failed command: READ FPDMA QUEUED]
and this might also be of interest:
https://answers.launchpad.net/ubuntu/+question/122588
[How do I fix a boot error: "failed command: READ FPDMA QUEUED"]

<https://launchpad.net/+search?field.text=READ+FPDMA+QUEUED&field.actions .search=Search>

[http://www.google.com/search?hl=en&complete=0&q=ubuntu+%2B"READ+FPDMA+QU EUED"&btnG=Search]



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 
Old 03-06-2011, 04:53 AM
Jeff Lane
 
Default my laptop sometimes stop responding with disk errors

On Sat, Mar 5, 2011 at 13:16, Asif Iqbal <vadud3@gmail.com> wrote:

>> Also, did you just upgrade? *And did you have these problems BEFORE
>> you upgraded, or only AFTER you upgraded?
>
> only after the kernel upgrade
>

Ok...

1: again, back up your data.
2: Please file a bug against the linux package
3: reboot your system and in the grub menu, pick an older kernel and
see if the problems go away (I would start with the kernel before the
one you're seeing problems with).

but by all means, please file a bug. Kernel upgrades shouldn't cause
that issue, but I HAVE seen reports in the past where a kernel upgrade
b0rked ext4, which could well be what happened here.

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 

Thread Tools




All times are GMT. The time now is 12:01 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org