Hi Silviu, You'll find quite a few if you google for "sata_nv" and "scsi parity error" There are problems with VIA chipsets as well but at least on my home computer (with VIA) the sata drive is loaded as an IDE and I can use ide=nodma to get around the issue - the HDD access won't be very fast but at least it works without lockups. This is not the case however with nForce 250 chipset where ide=nodma is "invalid" and thus ignored. Haven't tried with other nVidia chipsets though. Strangely enough that SLES 9 will work OK as long as DMA is disabled ... Regards (aka numa cele bune :-) Florin ----- Original Message ---- From: Silviu Marin-Caea <silviu_marin-caea@fieldinsights.ro> To: suse-linux-e@suse.com Sent: Friday, May 26, 2006 1:35:41 PM Subject: Re: [SLE] Workaroud for a SATA nForce 250 SCSI Parity Error problem On Friday 26 May 2006 13:56, hatespam00-mlist@yahoo.com wrote:
mount existing Linux partitions, I can see on the logger that infamous “SCSI Parity Error”, “device busy”, timeout and I/O errors while accessing the hard drive. And the only way out is to use the POWER RESET button.
Where do I found more info on these infamous errors? I think the same bug has bit me. nforce 350 + maxtor drives = > drive failures, lots of bad sectors etc. Should they work on a different chipset than nvidia? One of those failed drives has very precious data on it. It's part on a RAID1 mirror. The other disk died completely. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com