From owner-freebsd-questions Tue Jan 17 20:32:39 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA08179 for questions-outgoing; Tue, 17 Jan 1995 20:32:39 -0800 Received: from picspc01.pics.com (picspc01.pics.com [192.135.189.20]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id UAA08172 for ; Tue, 17 Jan 1995 20:32:37 -0800 Received: (from tpr@localhost) by picspc01.pics.com (8.6.9/8.6.9) id XAA00828 for freebsd-questions@freebsd.org; Tue, 17 Jan 1995 23:32:27 -0500 From: Terry Rossi Message-Id: <199501180432.XAA00828@picspc01.pics.com> Subject: Please Help! Disk Problem To: freebsd-questions@FreeBSD.org Date: Tue, 17 Jan 1995 23:32:26 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2270 Sender: questions-owner@FreeBSD.org Precedence: bulk I have just plunged into FreeBSD 2.0R and have purchased a 2nd hard disk for news spooling. I thought I had this licked last night and the news started spooling in today no problems. All of a sudden, the drive start- ed freaking out today..reporting thousands of this error: wd1e: hard error writing fsbn 306688 of 306688-306703 (wd1 bn 306751; cn 304 tn 5 sn 4)wd1: status 61 error 4 wd1e: hard error writing fsbn 306768 of 306768-306783 (wd1 bn 306831; cn 304 tn 6 sn 21)wd1: status 61 error 4 So... I figured that I screwed something up because I had quite a hard time getting the drive ready for a filesystem. Here is the output from the messages file and the the steps I went through maybe someone can tell me where I am going wrong. wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 534MB (1094688 total sec), 1086 cyl, 16 head, 63 sec, bytes/sec 512 wdc0: unit 1 (wd1): wd1: 515MB (1056384 total sec), 1048 cyl, 16 head, 63 sec, bytes/sec 512 Run sysinstall Fdisk and allocate the entire drive to FreeBSD, change the boot flag to no since this is the 2nd disk. Run sysinstall disklabel and I)mport the "1" slice into the "e" partition of the drive (c and d are listed). Exit to the os and run "newfs -i 1024 /dev/wd1e" . As I said everything works great for a little while then (as if the disk gets to a certian spot) the drive starts reporting all the above errors. The only other odd thing is that when I run newfs (again on the "e" partition, I am not sure if this is the correct thing to do) I receive the following warnings: newfs: /dev/wd1e: not a character-special device Warning: 64 sector(s) in last cylinder unallocated <-----odd /dev/wd1c: 1056320 sectors in 1048 cylinders of 16 tracks, 63 sectors 515.8MB in 66 cyl groups (16 c/g, 7.88MB/g, 1920 i/g) I find this interesting as "newfs -N /dev/wd1d" doesn't produce the warning. Please help as this is really messing me up. -- ------------------------------------------------------------ Terry Rossi tpr@pics.com Data: 609/753-2540 Sysop, Pics OnLine BBS telnet: bbs.pics.com 609/767-0216 Voice/Fax WWW: http://www.pics.com