https://bugzilla.novell.com/show_bug.cgi?id=248860 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |imotgm@yahoo.com ------- Comment #29 from teheo@novell.com 2007-04-08 05:03 MST ------- * Sorry about the sata_nv confusion. The point I was trying to make was problems occur across two unrelated controllers. They're not sharing any resources and even if they do the CRC error bit's meaning is very specific, it's CRC error on the IDE bus. The most common causes for that are faulty cabling, power problem and broken hardware. Also, it's quite common that IDE controllers using the TF/BMDMA interface indicate transmission failure detected on the host side as timeout. So, those symptoms across multiple independent controllers make me think it's most likely a power problem. I've seen quite a few weird transmission failure cases caused by power issues and because when power is problematic the symptoms vary greatly, it's a good idea to rule it out in the early stage during debugging. Also, another problem with high power multi-rail PSU is that each rail is actually given less wattage compared to e.g. 300w single-rail PSU. So, overloading a rail is actually easier on multi-rail PSUs. I have some first hand experience with that and I always use 300~350w single-rail PSU to power my disk arrays. So, if it isn't too much trouble, please try to balance disks more evenly among power connectors and try to use another power supply to power the system. Mandravia is suffering the same problem. Its symptom is much less drastic but the root cause is still there. Your system isn't working too well currently. I'm suspecting PSU problem but it might as well be a it821x driver problem as the smart mode support on the driver seems a bit flaky. * About the automatic stuff, oh well, I guess we'll just have to go that way to better make it easier for less tech-savvy users. I can probably disable automounting by editing fstab and messing with udev rules. Auto indexing is done by beagle but I can't tell from here whether that's causing your problem. Just de-install beagle if you don't want it. Automatic indexing has been there for long time with unix tho, think about locatedb and how long it has been around unix. I'm an old dog regarding those fancy desktop stuff, so I'm afraid I won't be too helpful. * The parameter is named it8212_noraid not it821x_noraid. git tells me it hasn't changed since its first inclusion in 2005. * Due to the large number of disk ports including USB or what not, it's becoming more an more difficult to maintain static device naming. I also liked /dev/hdX static naming but it's just a fact that they're going away (they're not so static with native/legacy mode switching controllers anyway). So, it seems we'll have to learn the LABEL= and UUID tricks. They're really neat once you get used to them too. And yeap, you're right, adding discontinuous minors to scsi disks in on my todo list. * To sum up, I think it might be a hardware, more specifically, PSU related problem. Please try to rule that out. Suse, redhat, mandravia, what not, most distributions try to keep their kernels as close to the mainline as possible these days and to some extent userland too. According to your report, mandravia kernel is seeing the problems too and I think you're likely to encounter similar severity as suse in later versions. So, please apply some standard hardware debugging methods - swap drives, connectors, disconnect some of them, redistribute power connectors. It takes some time but you know a lot and I think you'll be able to figure out what's going on (or not). Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.