i have Arch linux installed on my SCSI disc (Seagate Cheetah 18GB)
my controler is
Adaptec AHA-2940U/UW / AHA-39xx / AIC-7895 (rev 04)
working on kernel 2.6.15-ARCH (from 0.7.1 installation CD)
with default initrd ....
sometimes i get error like
(scsi0:A:0:0): Unexpected busfree in Data-out phase SEQADDR == 0x7d sd 0:0:0:0: SCSI error: return code = 0x10000 end_request: I/O error, dev sda, sector 664214 Buffer I/O error on device sda3, logical block 6718 lost page write due to I/O error on sda3
and my filesystem goes read-only ... after reset everything goes back to normal ... how i can prevent going read-only on "/" and restarting my linux ?
have a look wether mkinitrd put aic7xxx along with aic79xx into the ramdisk. if so, they are most likely conflicting with each other.
i suggest to exclude one of them in mkinitrd.conf.
I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell
id recommend going into scsi setup & verify the disc
it will reassign any bad sectors
i have the same scsi card with 2 73gb 10000 rpmm used drives on it with no problems so far (knock knock) check it out theyre pretty cheap the 2 i got are quiet & good condition
http://www.computergiants.com/items/par … T173404LCV
the disc verify may cause some data loss or corruption if any sectors are bad & reassigned
if not then it shouldnt damage any data on disc
ive not had any sectors reassigned on my current drives but i have had it in the past with no data on disc so i couldnt say for sure what outcome you may experience
i veryfied disc as i bought it and it showed that disc is ok
and yes both modules was loaded
now i created my own initrd ... and we will see
tx for help
well disabling one of modules doesn't help
i created my own initrd with
HOSTCONTROLLER_SCSI: aic7xxx sd_mod
and only this module is loadedfor my scsi controller
but i still get error
after error i restarted my computer and runned
in SCSI Controller Setup (Ctrl-A at start up) and and drive was veryfied without any error so i guess that isn't my drive problem
maybe will help that after this error my linux doesn't hang-up .. just FS goes readonly .. i still can read every file on disc .. just cannot write to them
... after restart everything is ok for about 2-3 days ....
please help ..