Date: Mon, 29 Nov 1999 11:39:37 -0600 From: "Bruce DeVault" <internal@intechsoft.net> To: <freebsd-questions@freebsd.org> Subject: adding a large IDE hard-drive post-install Message-ID: <002701bf3a90$b50ad1b0$0c01a8c0@wkbruce>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. ------=_NextPart_000_0024_01BF3A5E.6A3F66A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've been real problems adding a couple of hard drives to a server that = we've otherwise had no problems with, and I have to appeal for help with = this one. The server prior to adding the hard drives was an AMD K6/2-300 with 32MB = of RAM and an IDE 4 gig hard drive, running 3.3-STABLE cvsup'd as of = last week from a clean install. The kernel is the GENERIC kernel, with = IPDIVERT and IPFIREWALL enabled. We recently purchased two IBM Deskstar DPTA-373420 34.2 GB hard drives. = The top of the drives reads: P/N: 31L9060, LBA: 66,835,440, RPM: 7200, = MLC: 842312 CHS: 16383/16/63. I installed the two drives as master and slave on the secondary IDE = controller. They weren't detected with the right size by the BIOS, so I = upgraded the BIOS to the latest code from the motherboard manufacturer's = website, and they then detected perfectly. I set the BIOS for LBA, and = it showed: size: 34,219MB cyl: 4160, head: 255, precomp: 0, landz: = 16380, sect: 63. On bootup, the drives appeared as "wd2" and "wd3" as expected in BSD. = The kernel on bootup detects the drives as: wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): <IBM-DPTA-373420> wd2: 32634MB (66835440 sectors), 66305 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): <IBM-DPTA-373420> wd3: 32634MB (66835440 sectors), 66305 cyls, 16 heads, 63 S/T, 512 B/S I tried to install the drives using /stand/sysinstall, and fdisk'd them = with "use entire disk", dangerously dedicated. After some time I = determined that "use entire disk" overrides the manual setting of the = geometry, which starts off being something totally inappropriate, so I = followed the recommendation on the FAQ, and fdisk'd both drives with = Windows 98, and formatted them as MS-DOS FAT32 partitions. Both drives = fdisk'd to the right size under DOS and formatted with no bad sectors. I went back into BSD's fdisk using /stand/sysinstall and changed the = type of the partition to 165 (FreeBSD), noted that the geometry was now = detected correctly (apparently having been set by DOS's fdisk) and all = was well. But when I use disklabel to try to install a single filesystem, like = this: Disk: wd2 Partition name: wd2s1 Free: 0 blocks (0MB) Part Mount Size Newfs Part =20 ---- ----- ---- ----- ---- ----- wd2s1e /ua 32632MBUFS Y It fails with a mount error ("Invalid argument") after a lengthy time. I = tried to mount it and realized the newfs had failed, as the superblocks = weren't correct. When I run newfs manually, just like /stand/sysinstall = does, it shows: su-2.03# newfs -b 8192 -f 1024 /dev/rwd2s1e /dev/rwd2s1e: 66830336 sectors in 16316 cylinders of 1 tracks, 4096 = sectors 32632.0MB in 1020 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) super-block backups (for fsck -b #) at: 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, = 589856, 655392, 720928, 786464, 852000, 917536, 983072, 1048608, 1114144, = 1179680, ...a bunch deleted... 65667104, 65732640, 65798176, 65863712, 65929248, 65994784, 66060320, 66125856, 66191392, 66256928, 66322464, 66388000, 66453536, 66519072, 66584608, 66650144, 66715680, 66781216, write error: 0 newfs: wtfs: Read-only file system su-2.03# I can't figure out what I'm doing wrong, or what is wrong with the = newfs. I have repeated the entire procedure several times, on both = drives, both with after having used DOS's fdisk (with LBA enabled in the = BIOS) and using only BSD's utilities (both with LBA and NORMAL modes). = With BSD only, the geometry is detected incorrectly and I have to enter = what the BIOS says (4160/255/63). In between tries, I've been zeroing = out the partition table to make sure it isn't getting confused, with: dd if=3D/dev/zero of=3D/dev/rwd2 count=3D1000 which seems to work well to restart things with a clean slate. I would sure appreciate any help anyone could provide. Thank you for = your consideration of this, sorry this message is so long. Bruce DeVault InTech Software ------=_NextPart_000_0024_01BF3A5E.6A3F66A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>I've been real problems adding a couple = of hard=20 drives to a server that we've otherwise had no problems with, and I have = to=20 appeal for help with this one.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>The server prior to adding = the hard=20 drives was an AMD K6/2-300 with 32MB of RAM and an IDE 4 gig hard drive, = running=20 3.3-STABLE cvsup'd as of last week from a clean install. The kernel is = the=20 GENERIC kernel, with IPDIVERT and IPFIREWALL enabled.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>We recently purchased two IBM Deskstar = DPTA-373420=20 34.2 GB hard drives. The top of the drives reads: P/N: 31L9060, LBA: = 66,835,440,=20 RPM: 7200, MLC: 842312 CHS: 16383/16/63.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>I installed the two drives as master = and slave on=20 the secondary IDE controller. They weren't detected with the right size = by the=20 BIOS, so I upgraded the BIOS to the latest code from the motherboard=20 manufacturer's website, and they then detected perfectly. I set the BIOS = for=20 LBA, and it showed: size: 34,219MB cyl: 4160, head: 255, precomp: 0, = landz:=20 16380, sect: 63.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>On bootup, the drives appeared as "wd2" = and "wd3"=20 as expected in BSD. The kernel on bootup detects the drives=20 as:</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>wdc1 at 0x170-0x177 irq 15 on = isa<BR>wdc1: unit 0=20 (wd2): <IBM-DPTA-373420><BR>wd2: 32634MB (66835440 sectors), 66305 = cyls,=20 16 heads, 63 S/T, 512 B/S<BR>wdc1: unit 1 (wd3): = <IBM-DPTA-373420><BR>wd3:=20 32634MB (66835440 sectors), 66305 cyls, 16 heads, 63 S/T, 512=20 B/S<BR></FONT></DIV> <DIV><FONT face=3DArial size=3D2>I tried to install the drives using=20 /stand/sysinstall, and fdisk'd them with "use entire disk", dangerously=20 dedicated. After some time I determined that "use entire disk" overrides = the=20 manual setting of the geometry, which starts off being something totally = inappropriate, so I followed the recommendation on the FAQ, and fdisk'd = both=20 drives with Windows 98, and formatted them as MS-DOS FAT32 partitions. = Both=20 drives fdisk'd to the right size under DOS and formatted with no bad=20 sectors.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I went back into BSD's fdisk using=20 /stand/sysinstall and changed the type of the partition to 165 = (FreeBSD), noted=20 that the geometry was now detected correctly (apparently having been set = by=20 DOS's fdisk) and all was well.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>But when I use disklabel to try to = install a single=20 filesystem, like this:</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Disk: = wd2 =20 Partition name: wd2s1 Free: 0 blocks (0MB)</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Part =20 Mount = Size=20 Newfs Part <BR>---- =20 ----- = ----=20 ----- ---- -----</FONT></DIV> <DIV><FONT face=3DArial size=3D2>wd2s1e =20 /ua = 32632MBUFS=20 Y</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>It fails with a mount error ("Invalid = argument")=20 after a lengthy time. I tried to mount it and realized the newfs = had=20 failed, as the superblocks weren't correct. When I run newfs = manually, just=20 like /stand/sysinstall does, it shows:</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>su-2.03# newfs -b 8192 -f 1024=20 /dev/rwd2s1e<BR>/dev/rwd2s1e: 66830336 sectors in 16316 = cylinders of=20 1 tracks, 4096 sectors<BR> = 32632.0MB=20 in 1020 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)<BR>super-block backups = (for=20 fsck -b #) at:<BR> 32, 65568, 131104, 196640, 262176, 327712, = 393248,=20 458784, 524320, 589856,<BR> 655392, 720928, 786464, 852000, 917536, = 983072,=20 1048608, 1114144, 1179680,<BR>...a bunch deleted...</FONT></DIV> <DIV><FONT face=3DArial size=3D2> 65667104, 65732640, 65798176, = 65863712,=20 65929248, 65994784, 66060320,<BR> 66125856, 66191392, 66256928, = 66322464,=20 66388000, 66453536, 66519072,<BR> 66584608, 66650144, 66715680,=20 66781216,<BR>write error: 0<BR>newfs: wtfs: Read-only file=20 system<BR>su-2.03#<BR></FONT></DIV> <DIV><FONT face=3DArial size=3D2>I can't figure out what I'm doing = wrong, or what is=20 wrong with the newfs. I have repeated the entire procedure several = times, on=20 both drives, both with after having used DOS's fdisk (with LBA enabled = in the=20 BIOS) and using only BSD's utilities (both with LBA and NORMAL modes). = With BSD=20 only, the geometry is detected incorrectly and I have to enter what the = BIOS=20 says (4160/255/63). In between tries, I've been zeroing out the = partition table=20 to make sure it isn't getting confused, with:</FONT></DIV> <DIV> </DIV> <DIV><FONT size=3D2><FONT face=3DArial>dd if=3D/dev/zero of=3D/dev/rwd2=20 count=3D1000</FONT></FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2><FONT face=3DArial>which seems to work well to = restart things=20 with a clean slate.</FONT></FONT></DIV> <DIV><FONT size=3D2><FONT face=3DArial></FONT></FONT> </DIV> <DIV><FONT size=3D2><FONT face=3DArial>I would sure appreciate any help = anyone could=20 provide. Thank you for your consideration of this, sorry this message is = so=20 long.</FONT></FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Bruce DeVault</FONT></DIV> <DIV><FONT face=3DArial size=3D2>InTech Software</FONT></DIV> <DIV> </DIV></BODY></HTML> ------=_NextPart_000_0024_01BF3A5E.6A3F66A0-- 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?002701bf3a90$b50ad1b0$0c01a8c0>