Issues after last update.

[Sno]

Hi All,

I updated my box tonight. After the update it was amazingly SLOW. No message for a reboot, but I figured I would anyway. It hung on the splash screen for a minute or so, then went to terminal. Looked fine as everything scrolled. Got to GDM. Took about 5 minutes to complete the login. Rebooted to recovery to watch the boot and saw a ton of errors.Rebooted, checked dmesg ad got the following....

[ 43.387325] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 43.411682] ata3.00: ATA-8: WDC WD2500AAKS-00VYA0, 12.01B02, max UDMA/133
[ 43.411737] ata3.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 43.427954] ata3.00: configured for UDMA/133
[ 43.738831] ata4: SATA link down (SStatus 0 SControl 300)
[ 43.749461] scsi 3:0:0:0: Direct-Access ATA WDC WD2500AAKS-0 12.0 PQ: 0 ANSI: 5
[ 43.749850] sd 3:0:0:0: [sdc] 488397168 512-byte hardware sectors (250059 MB)
[ 43.749909] sd 3:0:0:0: [sdc] Write Protect is off
[ 43.749958] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 43.749971] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 43.750067] sd 3:0:0:0: [sdc] 488397168 512-byte hardware sectors (250059 MB)
[ 43.750123] sd 3:0:0:0: [sdc] Write Protect is off
[ 43.750172] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 43.750185] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 43.750245] sdc: sdc1 sdc2 < sdc5 sdc6 >
[ 43.760531] sd 3:0:0:0: [sdc] Attached SCSI disk
[ 43.760609] sd 3:0:0:0: Attached scsi generic sg4 type 0
[ 44.039212] Attempting manual resume
[ 44.039262] swsusp: Resume From Partition 8:37
[ 44.039264] PM: Checking swsusp image.
[ 44.039442] PM: Resume from disk failed.
[ 44.048317] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 44.050025] SGI XFS Quota Management subsystem
[ 44.084538] XFS mounting filesystem sdc6
[ 44.719427] Ending clean XFS mount for filesystem: sdc6
[ 58.168025] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 58.168086] ata3.00: BMDMA stat 0x24
[ 58.168137] ata3.00: cmd 25/00:00:ca:60:66/00:02:05:00:00/e0 tag 0 dma 262144 in
[ 58.168139] res 51/40:00:f1:61:66/40:00:05:00:00/e0 Emask 0x9 (media error)
[ 58.168253] ata3.00: status: { DRDY ERR }
[ 58.168301] ata3.00: error: { UNC }
[ 58.191495] ata3.00: configured for UDMA/133
[ 58.191550] ata3: EH complete
[ 67.893789] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 67.893843] ata3.00: BMDMA stat 0x24
[ 67.893894] ata3.00: cmd 25/00:00:ca:60:66/00:02:05:00:00/e0 tag 0 dma 262144 in
[ 67.893896] res 51/40:00:f4:61:66/40:00:05:00:00/e0 Emask 0x9 (media error)
[ 67.894010] ata3.00: status: { DRDY ERR }
[ 67.894058] ata3.00: error: { UNC }
[ 67.918290] ata3.00: configured for UDMA/133
[ 67.918346] ata3: EH complete
[ 80.258911] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 80.258965] ata3.00: BMDMA stat 0x24
[ 80.259017] ata3.00: cmd 25/00:00:ca:60:66/00:02:05:00:00/e0 tag 0 dma 262144 in
[ 80.259018] res 51/40:00:f6:61:66/40:00:05:00:00/e0 Emask 0x9 (media error)
[ 80.259133] ata3.00: status: { DRDY ERR }
[ 80.259181] ata3.00: error: { UNC }
[ 80.281405] ata3.00: configured for UDMA/133
[ 80.281461] ata3: EH complete
[ 90.594525] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 90.594579] ata3.00: BMDMA stat 0x24
[ 90.594634] ata3.00: cmd 25/00:00:ca:60:66/00:02:05:00:00/e0 tag 0 dma 262144 in
[ 90.594635] res 51/40:00:f5:61:66/40:00:05:00:00/e0 Emask 0x9 (media error)
[ 90.594750] ata3.00: status: { DRDY ERR }
[ 90.594798] ata3.00: error: { UNC }
[ 90.619051] ata3.00: configured for UDMA/133
[ 90.619108] ata3: EH complete
[ 101.101120] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 101.101174] ata3.00: BMDMA stat 0x24
[ 101.101226] ata3.00: cmd 25/00:00:ca:60:66/00:02:05:00:00/e0 tag 0 dma 262144 in
[ 101.101227] res 51/40:00:f2:61:66/40:00:05:00:00/e0 Emask 0x9 (media error)
[ 101.101342] ata3.00: status: { DRDY ERR }
[ 101.101390] ata3.00: error: { UNC }
[ 101.124583] ata3.00: configured for UDMA/133
[ 101.124639] ata3: EH complete
[ 108.256459] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 108.256513] ata3.00: BMDMA stat 0x24
[ 108.256565] ata3.00: cmd 25/00:00:ca:60:66/00:02:05:00:00/e0 tag 0 dma 262144 in
[ 108.256566] res 51/40:00:f2:61:66/40:00:05:00:00/e0 Emask 0x9 (media error)
[ 108.256680] ata3.00: status: { DRDY ERR }
[ 108.256728] ata3.00: error: { UNC }
[ 108.278951] ata3.00: configured for UDMA/133
[ 108.279014] sd 3:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 108.279110] sd 3:0:0:0: [sdc] Sense Key : Medium Error [current] [descriptor]
[ 108.279307] Descriptor sense data with sense descriptors (in hex):
[ 108.279393] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 108.280061] 05 66 61 f2
[ 108.280290] sd 3:0:0:0: [sdc] Add. Sense: Unrecovered read error - auto reallocate failed
[ 108.280424] end_request: I/O error, dev sdc, sector 90595826
[ 108.280484] ata3: EH complete
[ 115.497182] sd 3:0:0:0: [sdc] 488397168 512-byte hardware sectors (250059 MB)
[ 115.503447] sd 3:0:0:0: [sdc] Write Protect is off
[ 115.503496] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 123.265314] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 149.446611] sd 3:0:0:0: [sdc] 488397168 512-byte hardware sectors (250059 MB)
[ 153.567199] sd 3:0:0:0: [sdc] Write Protect is off
[ 153.567252] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 153.942432] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

I suppose the drive could have corrupted or hardware failed, but that seems like a stretch given I just updated. And yes, sdc is the linux drive. It runs, but very slowly!!!!

Anyone else with any troubles???? Any ideas out there?????

Thanks,

-Sno

[DaddyX3]

Someone just posted something similar that happened to them after an update, but this was because they had 'back ports' and 'unsupported' enabled in their software sources selected. I'm not sure if they got it sorted out or not. But if you have those things 'ticked' in software sources, then you 'asked for it'. Sorry to here of your problem. Do you have a backup kernel still installed in GRUB? Can you boot to the earlier kernel in you GRUB menu?

[bpollen]

Someone just posted something similar that happened to them after an update, but this was because they had 'back ports' and 'unsupported' enabled in their software sources selected.

Yeah, that was the update to 2.6.24-20-generic that you were referring to.... The strange thing is, I have those choices selected, and I have upgraded to that kernel, but have no problems (as of yet). In fact, I can't point to a single error as a result of having those choices checked yet.

Usually I am the guy they are talking about when they say: "When you idiot-proof it, they just build a better idiot!"

[Sno]

Well, unfortunately, I don't have those turned on. And the older kernel I have is not any better. The only things I have added to the source list are Ultimate Edition repos and Medibuntu repos for the extra non-free stuff. I am starting to think it is either hardware or filesystem failure. Since it is my Root linux partition, guess I will wipe it and try a different filesystem this time. Maybe stick with ext3 instead of xfs, and see if I can format it and reinstall.

Oh well.... **** happens.

Later,

-Sno

[Sno]

Hardware Failure