Asus M2V Motherboard VT8237A SATA controller issue

[gorgonizer]

Hello

I am running Kubuntu Gutsy Gibbon Tribe 3 with 2.6.22-9-generic kernel. When I first boot the machine, the SATA drive is viewable and I can access all the files (mounted as /home/gorgonizer/shares) without a problem. After a period of time however the drive appears to be lost, none of the files are accessible, and if I unmount the drive, it is not re-mountable:

root@sweetleaf:~# umount /home/gorgonizer/shares
root@sweetleaf:~# mount /home/gorgonizer/shares/
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@sweetleaf:~# dmesg | tail
[42568.236000] Write-error on swap-device (8:0:38895)
[43037.992000] Buffer I/O error on device sda2, logical block 1545
[43037.992000] lost page write due to I/O error on sda2
[43037.992000] Buffer I/O error on device sda2, logical block 1545
[43037.992000] lost page write due to I/O error on sda2
[43037.992000] Buffer I/O error on device sda2, logical block 1545
[43037.992000] lost page write due to I/O error on sda2
[43037.992000] Buffer I/O error on device sda2, logical block 0
[43037.992000] lost page write due to I/O error on sda2
[43047.132000] EXT3-fs: unable to read superblock

From /var/log/messages I get the following:

Aug 22 07:00:35 sweetleaf kernel: [19453.912000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 22 07:00:35 sweetleaf kernel: [19453.912000] ata1: soft resetting port
Aug 22 07:01:05 sweetleaf kernel: [19484.096000] ata1.00: qc timeout (cmd 0x27)
Aug 22 07:01:05 sweetleaf kernel: [19484.096000] ata1.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (625142448)
Aug 22 07:01:05 sweetleaf kernel: [19484.096000] ata1: failed to recover some devices, retrying in 5 secs
Aug 22 07:01:10 sweetleaf kernel: [19489.100000] ata1: soft resetting port
Aug 22 07:01:40 sweetleaf kernel: [19519.284000] ata1.00: qc timeout (cmd 0x27)
Aug 22 07:01:40 sweetleaf kernel: [19519.284000] ata1.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (625142448)
Aug 22 07:01:40 sweetleaf kernel: [19519.284000] ata1.00: limiting speed to UDMA/133:PIO3
Aug 22 07:01:40 sweetleaf kernel: [19519.284000] ata1: failed to recover some devices, retrying in 5 secs
Aug 22 07:01:45 sweetleaf kernel: [19524.288000] ata1: soft resetting port
Aug 22 07:02:16 sweetleaf kernel: [19554.472000] ata1.00: qc timeout (cmd 0x27)
Aug 22 07:02:16 sweetleaf kernel: [19554.472000] ata1.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (625142448)
Aug 22 07:02:16 sweetleaf kernel: [19554.472000] ata1.00: disabled
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] ata1: EH complete
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] end_request: I/O error, dev sda, sector 71
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] end_request: I/O error, dev sda, sector 1095
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] end_request: I/O error, dev sda, sector 2119
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] end_request: I/O error, dev sda, sector 3143
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] end_request: I/O error, dev sda, sector 3151
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.976000] end_request: I/O error, dev sda, sector 4175
Aug 22 07:02:16 sweetleaf kernel: [19554.980000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.980000] end_request: I/O error, dev sda, sector 5199
Aug 22 07:02:16 sweetleaf kernel: [19554.980000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.980000] end_request: I/O error, dev sda, sector 6223
Aug 22 07:02:16 sweetleaf kernel: [19554.980000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.980000] end_request: I/O error, dev sda, sector 7247
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] end_request: I/O error, dev sda, sector 8271
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] end_request: I/O error, dev sda, sector 9295
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] end_request: I/O error, dev sda, sector 10319
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] end_request: I/O error, dev sda, sector 11343
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] sd 0:0:0:0: [sda] READ CAPACITY failed
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] sd 0:0:0:0: [sda] Sense not available.
Aug 22 07:02:16 sweetleaf kernel: [19554.984000] sd 0:0:0:0: [sda] Write Protect is off

I have tried adding a brand new SATA drive to the system also, but this fails in a similar manner (initially works, but becomes inaccessible over time), and the drive used to work on an older kernel (and when I had Debian Testing installed) so I am certain that it is not an issue with the drive itself.

Has anyone suffered a similar issue, and if so, can you indicate a possible solution?

Cheers

Stewart

[enchesss]

Re: Asus M2V Motherboard VT8237A SATA controller issue

Sorry - i have attempted many installations with teh m2v and failed to get anywhere except with mandriva.
How did you go with previous versions of ubuntu e.g. fiesty- did they work?

Does your board have vga output? or is it just pci video card?

no idea about the HD becuase i cant even get any ubuntu past the installationon this motherboard

cheers

[gorgonizer]

Re: Asus M2V Motherboard VT8237A SATA controller issue

The M2V was using a Nvidia Geforce 7600 GS PCI-E card for graphics.

The drives were used on a KT6 Delta mobo, which died, and I bought the M2V as a replacement, and Gutsy Gibbon/Debian Testing were the only Linux distributions I tried with the M2V. Both failed, although Debian took longer to loose access to the SATA drive.

In the end I gave up and bought the awesome M2N32-SLI Premium which came with a free remote, which was nice. Had no problems getting the drives to work with new mobo, and even the remote works too!!

[dibl]

Re: Asus M2V Motherboard VT8237A SATA controller issue

Cool -- Welcome!