Opensuse 11.2 32/64 ata frozen, {DRDY} error?

English Install/Boot/Login
1

Hello!

i have a problem, or a kernel bug, dont know, and i am losing my patience with opensuse 11.2 :S

so the story goes like this:
i had installed on sata disk Samsung 500gb opensuse 11.0 and a second disk Samsung 500gb, and old motherboard with 478 socket, and one day i decided to upgrade motherboard to socket 775 and ddr2 ram, but after the motherboard change the sistem didnt boot, and i didnt want to apply new drivers and stuff so i just upgrade to opensuse 11.2 and the sistem take care of it self, but after the update the wierd things starts to happens, like this error:

Feb 3 20:16:47 pomaranca kernel: 8843.704047] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 3 20:16:47 pomaranca kernel: 8843.704070] ata3.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0
Feb 3 20:16:47 pomaranca kernel: 8843.704072] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 3 20:16:47 pomaranca kernel: 8843.704090] ata3.00: status: { DRDY }
Feb 3 20:16:51 pomaranca kernel: 8848.141023] ata3: soft resetting link
Feb 3 20:16:51 pomaranca kernel: 8848.301765] ata3.00: configured for UDMA/133
Feb 3 20:16:51 pomaranca smartd[4447]: Device: /dev/sdb [SAT], not capable of SMART self-check

and the partition remount in RO mode, someties it just froze, so i got new sata WD640gb and install a fresh sistem with ext4, same errors, reinstall and use ext3, same error, reinstall with 64 version beacuse i realised by then that a new CPU supported 64bit, same error…
i did a mem test 1 hole day, no errors, change 5 diffrent motherboards ( asus, asrock, gigabyte ) same error, then i try IDE disk 200gb to install sistem and mount /srv and /home with new 640 gb sata disk, now the sistem works, but i get those errors on /srv and /home

Feb 3 20:14:45 pomaranca kernel: 8721.704155] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 3 20:14:45 pomaranca kernel: 8721.704179] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 3 20:14:45 pomaranca kernel: 8721.704181] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 3 20:14:45 pomaranca kernel: 8721.704199] ata3.00: status: { DRDY }
Feb 3 20:14:47 pomaranca kernel: 8723.999020] ata3: soft resetting link
Feb 3 20:14:47 pomaranca kernel: 8724.160067] ata3.00: configured for UDMA/133
Feb 3 20:14:47 pomaranca kernel: 8724.160085] ata3.00: device reported invalid CHS sector 0
Feb 3 20:14:47 pomaranca kernel: 8724.160115] ata3: EH complete
Feb 3 20:14:48 pomaranca kernel: 8725.376312] end_request: I/O error, dev sdb, sector 1044678138
Feb 3 20:14:48 pomaranca kernel: 8725.376451] Aborting journal on device sdb2:8.
Feb 3 20:14:56 pomaranca kernel: 8732.995211] journal commit I/O error
Feb 3 20:14:57 pomaranca kernel: 8733.995024] EXT4-fs error (device sdb2): ext4_journal_start_sb: Detected aborted journal
Feb 3 20:14:57 pomaranca kernel: 8733.995043] EXT4-fs (sdb2): Remounting filesystem read-only
Feb 3 20:14:57 pomaranca kernel: 8733.995054] ext4_da_writepages: jbd2_start: 1024 pages, ino 280066; err -30
Feb 3 20:14:57 pomaranca kernel: 8733.995064] Pid: 20, comm: pdflush Tainted: G C 2.6.31.5-0.1-desktop #1
Feb 3 20:14:57 pomaranca kernel: 8733.995073] Call Trace:
Feb 3 20:14:57 pomaranca kernel: 8733.995096] <ffffffff81011a19>] try_stack_unwind+0x189/0x1b0
Feb 3 20:14:57 pomaranca kernel: 8733.995110] <ffffffff8101025d>] dump_trace+0xad/0x3a0
Feb 3 20:14:57 pomaranca kernel: 8733.995122] <ffffffff81011524>] show_trace_log_lvl+0x64/0x90
Feb 3 20:14:57 pomaranca kernel: 8733.995135] <ffffffff81011573>] show_trace+0x23/0x40
Feb 3 20:14:57 pomaranca kernel: 8733.995148] <ffffffff81551ee2>] dump_stack+0x81/0x9e
Feb 3 20:14:57 pomaranca kernel: 8733.995192] <ffffffffa0092b51>] ext4_da_writepages+0x571/0x5b0 [ext4]
Feb 3 20:14:57 pomaranca kernel: 8733.995217] <ffffffff81109c85>] do_writepages+0x35/0x70
Feb 3 20:14:57 pomaranca kernel: 8733.995233] <ffffffff81172a19>] writeback_single_inode+0x1a9/0x450
Feb 3 20:14:57 pomaranca kernel: 8733.995246] <ffffffff81173120>] generic_sync_sb_inodes+0x1a0/0x560
Feb 3 20:14:57 pomaranca kernel: 8733.995258] <ffffffff81173525>] sync_sb_inodes+0x45/0x60
Feb 3 20:14:57 pomaranca kernel: 8733.995270] <ffffffff81173665>] writeback_inodes+0x65/0x120
Feb 3 20:14:57 pomaranca kernel: 8733.995281] <ffffffff81108a4c>] wb_kupdate+0xcc/0x160
Feb 3 20:14:57 pomaranca kernel: 8733.995293] <ffffffff8110ad39>] __pdflush+0x139/0x270
Feb 3 20:14:57 pomaranca kernel: 8733.995304] <ffffffff8110aef8>] pdflush+0x88/0xb0
Feb 3 20:14:57 pomaranca kernel: 8733.995316] <ffffffff8108c336>] kthread+0xb6/0xc0
Feb 3 20:14:57 pomaranca kernel: 8733.995328] <ffffffff8100d7ba>] child_rip+0xa/0x20
Feb 3 20:15:44 pomaranca master[22455]: process 22784 exited, status 0

Feb 3 21:24:02 pomaranca kernel: 293.704048] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 3 21:24:02 pomaranca kernel: 293.704068] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 3 21:24:02 pomaranca kernel: 293.704071] res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 3 21:24:02 pomaranca kernel: 293.704085] ata3.00: status: { DRDY }
Feb 3 21:24:07 pomaranca kernel: 298.294021] ata3: soft resetting link
Feb 3 21:24:07 pomaranca kernel: 298.454410] ata3.00: configured for UDMA/133
Feb 3 21:24:07 pomaranca kernel: 298.454440] end_request: I/O error, dev sdb, sector 1044665698
Feb 3 21:24:07 pomaranca kernel: 298.454472] ata3: EH complete
Feb 3 21:24:07 pomaranca kernel: 298.454613] Aborting journal on device sdb2:8.
Feb 3 21:24:07 pomaranca kernel: 298.510892] EXT4-fs error (device sdb2): ext4_journal_start_sb: Detected aborted journal
Feb 3 21:24:07 pomaranca kernel: 298.510912] EXT4-fs (sdb2): Remounting filesystem read-only
Feb 3 21:24:07 pomaranca kernel: 298.566390] journal commit I/O error
Feb 3 21:24:24 pomaranca sshd[3631]: Accepted keyboard-interactive/pam for janezek from 192.168.1.6 port 54628 ssh2
Feb 3 21:24:30 pomaranca su: (to root) janezek on /dev/pts/0
Feb 3 21:24:43 pomaranca kernel: 334.974658] EXT4-fs: mballoc: 1 blocks 1 reqs (0 success)
Feb 3 21:24:43 pomaranca kernel: 334.974674] EXT4-fs: mballoc: 1 extents scanned, 0 goal hits, 1 2^N hits, 0 breaks, 0 lost
Feb 3 21:24:43 pomaranca kernel: 334.974682] EXT4-fs: mballoc: 201 generated and it took 6377987
Feb 3 21:24:43 pomaranca kernel: 334.974689] EXT4-fs: mballoc: 512 preallocated, 0 discarded
Feb 3 21:24:43 pomaranca kernel: 334.974791] EXT4-fs error (device sdb2): ext4_put_super: Couldn’t clean up the journal
Feb 3 21:25:03 pomaranca kernel: 354.295558] EXT4-fs (sdb2): barriers enabled
Feb 3 21:25:03 pomaranca kernel: 354.387128] kjournald2 starting: pid 3692, dev sdb2:8, commit interval 5 seconds
Feb 3 21:25:03 pomaranca kernel: 354.387149] EXT4-fs warning (device sdb2): ext4_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Feb 3 21:25:03 pomaranca kernel: 354.387163] EXT4-fs warning (device sdb2): ext4_clear_journal_err: Marking fs in need of filesystem check.
Feb 3 21:25:03 pomaranca kernel: 354.387415] EXT4-fs (sdb2): warning: mounting fs with errors, running e2fsck is recommended
Feb 3 21:25:03 pomaranca kernel: 354.387630] EXT4-fs (sdb2): internal journal on sdb2:8
Feb 3 21:25:03 pomaranca kernel: 354.387643] EXT4-fs (sdb2): delayed allocation enabled
Feb 3 21:25:03 pomaranca kernel: 354.387651] EXT4-fs: file extents enabled
Feb 3 21:25:03 pomaranca kernel: 354.419342] EXT4-fs: mballoc enabled
Feb 3 21:25:03 pomaranca kernel: 354.419385] EXT4-fs (sdb2): recovery complete
Feb 3 21:25:03 pomaranca kernel: 355.007503] EXT4-fs (sdb2): mounted filesystem with ordered data mode

any ideas?

Kristijan

2

Could you please report this to Novell’s bugzilla?

3

i think that my second new drive WD640 is failing! >:(

if you get this error with opensuse 11.2 and sata drive STOP USING THE DRIVE!

i have corrupted 2 new sata drives and my old one! the bios is reporting that the disk are failing!

i used WD640AAKS, WD500AAKS, samsung HD502IJ!

4

Where did you get 11.2? Download? If so, did you check the md5sum? Checked the used media?
So far you’ve been changing hardware, the cause may very well be in corrupt install media. Aspecially since it errors out on all kinds of mobo’s and disks.

So, I suggest you leave hardware as it is now, download and burn a new install medium, install and see if trouble persists.

BTW. I don’t believe openSUSE destroys disks. A corrupted kernel install may do a lot, but not that.

5

i got 11.2 32 & 64 from opensuse.org, check md5, all good, and this current motherboard is brand new, the install is fresh, and the WD640 is brand new, but the problem is still there, but now the wd640 is so bad, that i cant even boot anymore

6

Try changing the drive access in the BIOS, it seems the kernel does not like it. LBA should do OK. It must be somewhere in there since you can install.

7

you mean enhanced and compatible mode? curently i have enhanced mode, before fresh install i poke around this setting with no luck, it didnt like compatible mode, the bios didnt even boot
i want to mention that when linux start to boot, its halted at loading drivers, and the error pops out