Eric Sproul wrote: > Ben Rockwood wrote: > > >> If your not getting any other types of errors reported back (wierd >> driver errors, etc) I'd go for replacing everything you easily can >> (cables), retest, and then go from there. Following the cables, I'd opt >> to use a SATA card other than the 3114. Just a hunch, but I think thats >> your problem. >> > > Hi Ben, > I don't see any hardware errors in dmesg/messages. What brand of SATA card > would you recommend? Most of the cheapies are some variant of Silicon Image > 3114/3124/3512. It's also darn-near impossible to find something at retail > that's not cheesy "RAID". :) >
I've had the same experience. Frankly, I don't have a good suggestion. I need one for my workstation, but I don't want to spend money on a card that doesn't work well and I don't live near a Fry's anymore (shipping back to NewEgg sucks). I should look around for an inexpensive LSI. >> On the more unusual side, check the power to the drives. It is >> possible, however unlikely, that the drives are getting insufficient >> voltage and misbehaving under high load... I doubt it, but you know, >> just have a check anyway. >> > > I'm not sure how I'd check that, but for perspective, this is a 5U > storage-oriented chassis with 24 disk bays, only 6 of which are currently in > use, plus the OS drives in 2 internal bays. We used to run this system with > Linux using 16 SATA drives and 2 3ware controllers, so I'm pretty sure the > power > supplies are up to the task with the current load. > For some reason I had the odd idea that these were eSATA drives... for internal drives about all you can do is re-check the connectors and possibly switch to a different power rail from the supplies, but if you've got time on this thing I wouldn't both... just an out-there thing to mention. >> I assume when you say "rpool" you mean "remote pool", for backups >> perhaps? >> > > No, I was referring to the default name of the ZFS root pool, as in: > > rpool/ROOT/snv_99 > > >> Also... have you asked FMA what it thinks? "fmadm faulty -v" In my >> experience FMA rarely actually catches hardware issues but none-the-less >> sometimes it gets it right, so give it a check. >> > > I thought that as well, and it reports nothing. :) > > I'll try the cable swap, and if that doesn't nail it, an add-in card. > However, > The device names will change when I move off the onboard ports, and in the > past > I've not been able to recover from that. I'm guessing that GRUB needs to be > updated somehow-- is it a matter of booting failsafe, importing the pool, and > re-installing the stage1/stage2 files? I don't know. I've been avoiding ZFS Root, frankly, and prefer UFS root. I'd ordinarily offer to try it but I'm swamped atm. As another alternative form of diagnosis... have you looked at the SMART data? benr. _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
