Public bug reported:
Trying to clean install Karmic Server.
Died while creating and formatting partitions.
Noticed bug #493661 but not sure it was related since his is post
install.
I suspect the real problem is outlined in bug #492994 - problems with
the sata_via module.
I have seen these ata resets using both the Hardy and Karmic server install
disks.
This was the first time I ignored them and let the installation proceed.
I've tried two different hard drives, two different SATA controllers
(same chipset) and two different SATA cables, all with similar reset
notices when drives in heavy use.
Please let me know if any more info is required, I'll try and produce.
Complete syslog attached but this exerpt hits the high spots
Jan 3 17:50:12 kernel: [ 616.809340] ata3: hard resetting link
Jan 3 17:50:13 kernel: [ 617.128068] ata3: SATA link up 1.5 Gbps (SStatus 113
SControl 310)
Jan 3 17:50:13 kernel: [ 617.152542] ata3.00: configured for UDMA/33
Jan 3 17:50:13 kernel: [ 617.152571] ata3: EH complete
Jan 3 17:50:13 kernel: [ 617.158607] ata3.00: exception Emask 0x12 SAct 0x0
SErr 0x1400500 action 0x6
Jan 3 17:50:13 kernel: [ 617.158615] ata3.00: BMDMA stat 0x5
Jan 3 17:50:13 kernel: [ 617.158626] ata3: SError: { UnrecovData Proto
Handshk TrStaTrns }
Jan 3 17:50:13 kernel: [ 617.158648] ata3.00: cmd
35/00:00:57:14:c4/00:04:1c:00:00/e0 tag 0 dma 524288 out
Jan 3 17:50:13 kernel: [ 617.158652] res
51/84:90:57:14:c4/84:03:1c:00:00/e0 Emask 0x12 (ATA bus error)
Jan 3 17:50:13 kernel: [ 617.158661] ata3.00: status: { DRDY ERR }
Jan 3 17:50:13 kernel: [ 617.158668] ata3.00: error: { ICRC ABRT }
Jan 3 17:50:13 kernel: [ 617.158683] ata3: hard resetting link
Jan 3 17:50:13 kernel: [ 617.476071] ata3: SATA link up 1.5 Gbps (SStatus 113
SControl 310)
Jan 3 17:50:13 kernel: [ 617.500925] ata3.00: configured for UDMA/33
Jan 3 17:50:13 kernel: [ 617.501014] sd 2:0:0:0: [sda] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 3 17:50:13 kernel: [ 617.501024] sd 2:0:0:0: [sda] Sense Key : Aborted
Command [current] [descriptor]
Jan 3 17:50:13 kernel: [ 617.501037] Descriptor sense data with sense
descriptors (in hex):
Jan 3 17:50:13 kernel: [ 617.501044] 72 0b 47 00 00 00 00 0c 00 0a 80
00 00 00 00 00
Jan 3 17:50:13 kernel: [ 617.501068] 1c c4 14 57
Jan 3 17:50:13 kernel: [ 617.501079] sd 2:0:0:0: [sda] Add. Sense: Scsi
parity error
Jan 3 17:50:13 kernel: [ 617.501098] end_request: I/O error, dev sda, sector
482612311
Jan 3 17:50:13 kernel: [ 617.501417] ata3: EH complete
Jan 3 17:50:13 kernel: [ 617.509252] Aborting journal on device dm-0:8.
Jan 3 17:50:13 kernel: [ 617.509496] mpage_da_map_blocks block allocation
failed for inode 102 at logical offset 0 with max blocks 49 with error -30
Jan 3 17:50:13 kernel: [ 617.529738] This should not happen.!! Data will be
lost
Jan 3 17:50:13 kernel: [ 617.536802] EXT4-fs error (device dm-0) in
ext4_reserve_inode_write: Journal has aborted
Jan 3 17:50:13 kernel: [ 617.536814] EXT4-fs (dm-0): Remounting filesystem
read-only
Jan 3 17:50:13 debootstrap: tar: write error: Read-only file system
Jan 3 17:50:13 kernel: [ 617.542106] ext4_da_writepages: jbd2_start: 1024
pages, ino 102; err -30
Jan 3 17:50:13 kernel: [ 617.542124] Pid: 24, comm: pdflush Not tainted
2.6.31-14-generic #48-Ubuntu
Jan 3 17:50:13 kernel: [ 617.542131] Call Trace:
Jan 3 17:50:13 kernel: [ 617.542171] [<c056e41c>] ? printk+0x18/0x1c
Jan 3 17:50:13 kernel: [ 617.542189] [<c0266162>]
ext4_da_writepages+0x452/0x490
Jan 3 17:50:13 kernel: [ 617.542217] [<c01ba551>] do_writepages+0x21/0x40
Jan 3 17:50:13 kernel: [ 617.542240] [<c02033fe>]
writeback_single_inode+0x16e/0x3d0
Jan 3 17:50:13 kernel: [ 617.542259] [<c013b614>] ? dequeue_entity+0x14/0x290
Jan 3 17:50:13 kernel: [ 617.542284] [<c0453564>] ?
dm_any_congested+0x54/0x70
Jan 3 17:50:13 kernel: [ 617.542294] [<c0203afd>]
generic_sync_sb_inodes+0x38d/0x4a0
Jan 3 17:50:13 kernel: [ 617.542305] [<c0203ced>] writeback_inodes+0x4d/0xe0
Jan 3 17:50:13 kernel: [ 617.542315] [<c01b9432>] wb_kupdate+0xa2/0x110
Jan 3 17:50:13 kernel: [ 617.542326] [<c01bac27>] __pdflush+0xf7/0x1f0
Jan 3 17:50:13 kernel: [ 617.542335] [<c01bad20>] ? pdflush+0x0/0x40
Jan 3 17:50:13 kernel: [ 617.542344] [<c01bad20>] ? pdflush+0x0/0x40
Jan 3 17:50:13 kernel: [ 617.542353] [<c01bad59>] pdflush+0x39/0x40
Jan 3 17:50:13 kernel: [ 617.542361] [<c01b9390>] ? wb_kupdate+0x0/0x110
Jan 3 17:50:13 kernel: [ 617.542377] [<c015bf8c>] kthread+0x7c/0x90
Jan 3 17:50:13 kernel: [ 617.542386] [<c015bf10>] ? kthread+0x0/0x90
Jan 3 17:50:13 kernel: [ 617.542404] [<c0104007>]
kernel_thread_helper+0x7/0x10
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
mpage_da_map_blocks block allocation failed
https://bugs.launchpad.net/bugs/502661
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
