Re: disk/drive-bay problem
g_vfs_done():da4s1d[READ(offset=261868847104, length=16384)]error = 5 ... 1. This only happens on drive-bay 4. If I swap the 300 Gig drives around, they are all happy in any drive-bay but number 4 ... 2. The old 145Gig drives work perfectly in any bay, including bay 4. ... Why would one (proven good) drive fail in that slot, while the other (also proven good) drive succeeds. The only difference is the size and speed (145 vs 300, 10k vs 15k). Any chance bay 4 has a minor wiring problem, like a broken ground or three, causing an impedance bump? Such things might just barely work at 10k, but fail at higher transfer speeds. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: disk/drive-bay problem
On Wed, Feb 25, 2009 at 05:59:58PM -0800, Richard Stockton wrote: I have a Dell PowerEdge 4400 running FreeBSD 6.2 (yes, I know it's old). This machine has 8 hot-swapable drive bays. Recently I purchased 7 new drives for it (300Gig 15K) to replace the old ones (145Gig 10k). I was able to successfully install 6 of the 7 drives, and they all work perfectly. The 7th drive (actually the 4th drive-bay) gives lots of errors like this: g_vfs_done():da4s1d[READ(offset=261868847104, length=16384)]error = 5 One reason I've seen for this error is a bad cable connection. It could be that the connector between the drive and the bay is somewhat oxidised or dirty. Sanding the connectors might help in that case. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpor1u1FCPqd.pgp Description: PGP signature
Re: disk/drive-bay problem
At 12:10 PM 2/26/2009, Roland Smith wrote: On Wed, Feb 25, 2009 at 05:59:58PM -0800, Richard Stockton wrote: I have a Dell PowerEdge 4400 running FreeBSD 6.2 (yes, I know it's old). This machine has 8 hot-swapable drive bays. Recently I purchased 7 new drives for it (300Gig 15K) to replace the old ones (145Gig 10k). I was able to successfully install 6 of the 7 drives, and they all work perfectly. The 7th drive (actually the 4th drive-bay) gives lots of errors like this: g_vfs_done():da4s1d[READ(offset=261868847104, length=16384)]error = 5 One reason I've seen for this error is a bad cable connection. It could be that the connector between the drive and the bay is somewhat oxidised or dirty. Sanding the connectors might help in that case. Try to avoid sanding a connector. It's better to use a clean pencil eraser and basically wipe off the oxidation. After it's looking shiny, use a clean cloth to wipe off any eraser residue. Brad Mettee PC HotShots, Inc. Baltimore, MD (410) 426-7617 - Let us bring out the *Power* of your PCs. - - Custom Business Software Solutions since 1991 - visit http://www.pchotshots.com for information about our company. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
disk/drive-bay problem
I have a Dell PowerEdge 4400 running FreeBSD 6.2 (yes, I know it's old). This machine has 8 hot-swapable drive bays. Recently I purchased 7 new drives for it (300Gig 15K) to replace the old ones (145Gig 10k). I was able to successfully install 6 of the 7 drives, and they all work perfectly. The 7th drive (actually the 4th drive-bay) gives lots of errors like this: g_vfs_done():da4s1d[READ(offset=261868847104, length=16384)]error = 5 and while you can partially read/write to it, every error like the above means a failed read or write. Here's the really strange part. 1. This only happens on drive-bay 4. If I swap the 300 Gig drives around, they are all happy in any drive-bay but drive-bay number 4, and there are no errors with any of them. 2. The old 145Gig drives work perfectly in any bay, including bay 4. This makes no sense to me. Why would one (proven good) drive fail in that slot, while the other (also proven good) drive succeeds. The only difference is the size and speed (145 vs 300, 10k vs 15k). Here's a df: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 202603086743099651847%/ devfs 1 1 0 100%/dev /dev/da0s1d 6090094 3353614 224927460%/home /dev/da0s1e 3045006 1307482 149392447%/usr /dev/da0s1f 2120714 5972 1945086 0%/var /dev/da1s1d 283743762 45540 260998722 0%/bak /dev/da2s1d 283743762 213625780 4741848282%/bak13a /dev/da3s1d 283743762 89492866 17155139634%/bak13b /dev/da5s1d 283743762 213359628 4768463482%/bak14a /dev/da4s1d 138860928 97258122 3049393276%/bak14b /dev/da6s1d 283743762 214408266 4663599682%/bak15a /dev/da7s1d 283743762 97749186 16329507637%/bak15b The controller is an Adaptec aic7880 Ultra SCSI adapter. All the 300 Gig drives are SEAGATE ST3300655LC 0003. All the 145 Gig drives are SEAGATE ST3146707LC 0005. I would appreciate any light anyone can shine on this problem. Thank you. - Richard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
