Date: Mon, 28 Feb 2000 18:42:08 +0200 From: "freebsd" <george@vagner.com> To: "Jeff Lush" <jeff@nerdpower.com>, "Mike Nowlin" <mike@argos.org> Cc: <freebsd-questions@FreeBSD.ORG> Subject: RE: FW: Help with a bad hard disk Message-ID: <000401bf820a$c1162100$0eb65c8b@oemcomputer> In-Reply-To: <NDBBKIMGBBOBEOPLFCHIIEADCHAA.jeff@nerdpower.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Better yet drop kick that WD and get an IBM SCSI or Seagate,Quantum. I have had 5 drives go bad in 3 years from WD. Never again will I ever buy A WD drive. I run quantum scsi drives in our semiconductor processing tools and they run 24/7/365 non stop For years on end. I have heard of bad drives once or twice in my 10 years of Working on this equipment. -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG] On Behalf Of Jeff Lush Sent: Monday, January 31, 2000 7:18 AM To: Mike Nowlin Cc: freebsd-questions@FreeBSD.ORG Subject: RE: FW: Help with a bad hard disk > > I'm hoping someone can offer some assistance with a bad IDE disk running > > FreeBSD 3.4. The disk is a Western Digital Caviar 1.6 GB and is the > > secondary drive on a PPro 200. The machine was accidently and suddenly > > powered off and now whenever the machine boots, the kernel > stops and I need > > to run fsck manually, when I run fsck manually, it says: > > > > w1s1e: hard error reading fsbn3016199 of 3016176-3016287 (w1s1 > bn 3016199; > > cn 748 to 4 sn 11) (status59(rdy,seekdone,drg,err) error 40<uncorr>) > > /dev/rwd1s1e: CANNOT READ: BLK 3016176 > > Don't suppose this is a 31600 model? I've had that particular problem on > a LOT of these drives, plus the 32100 (2.1g) models... Out of 30 32100's > we bought, 6 failed within the first two months, about ten more within the > first year, and now only two remain (think it's been a little under 3 > years since we got them.) The 31600's had a similar track record -- the > one in my FBSD box just died about three weeks ago. They tend to meet > their maker with a fairly annoying "ker-CHUNK" sound every few seconds... > > WD made the 3xx00 and 2xx00 drives during the same time frame -- the 2's > have been quite reliable, but the 3's need to be drop-kicked. > > > If you do have one of these, I'd suggest replacing as quickly as possible > -- this problem seems to grow quickly until the drive is useless. I've > had fairly good success (when caught early) with copying files off the bad > drives -- mount them read-only, then just copy the contents off to another > HD. > > Western Dig. had a 3-year warranty on some of their drives from this > period, and a 5-year on others... Should be able to find out from their > web site. If it's still under warranty, get them to replace it, and be > sure not to accept the 3xx00-series as a replacement (I'm sure they have a > bunch in the warehouse for exchanges) -- try to get a 21600 or one of > their newer models... > > > Just filling you in on a little history -- hopefully, this isn't the > problem you're having... > > good luck -- mike Thanks for the help. My two biggest problems are that 1)I'm a bit of a newbie 2)I'm stuck in single user only mode and cannot mount the partition To make things worse, I have cannot start the OS in multi user mode. My primary drive (Quantum Fireball 3.2GB) has all the system files and checks out fine from fsck. The bad WD disk only has a www directory. I have tried removing the WD disk and restarting, but fsck still complains and will not start. My goal is to edit fstab to remove the entries pointing the the bad WD disk, but I can't find a way to do it. Any suggestions? Thanks, Jeff Lush To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000401bf820a$c1162100$0eb65c8b>