From owner-freebsd-questions@FreeBSD.ORG Sun May 29 01:16:11 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC11C16A41C for ; Sun, 29 May 2005 01:16:11 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao04.coxmail.com (lakecmmtao04.coxmail.com [68.99.120.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 896BE43D53 for ; Sun, 29 May 2005 01:16:11 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao04.coxmail.com (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050529011610.PSFV3718.lakecmmtao04.coxmail.com@dns1>; Sat, 28 May 2005 21:16:10 -0400 From: Vizion To: Ulf Magnusson Date: Sat, 28 May 2005 18:11:09 -0700 User-Agent: KMail/1.8 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200505281811.09906.vizion@vizion.occoxmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Seagate HD not detected by FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 01:16:12 -0000 On Saturday 28 May 2005 18:08, the author Ulf Magnusson contributed to the= =20 dialogue on Re: Seagate HD not detected by FreeBSD: >From: Vizion > >> On Saturday 28 May 2005 16:48, the author Ulf Magnusson >> contributed to the >> >> dialogue on Seagate HD not detected by FreeBSD: >> >I'm trying to add a 120 GiB Seagate Barracuda (ST3120022A) HD. I've >> >attached it as the sole device on IDE cable 2, jumpering it as a >> >> slave>device. It is correctly detected by the BIOS as the Secondary >> Slave.> >> >> >The drive isn't detected by FreeBSD. There's no entry for it among >> >> the>dmesg messages, and no device node gets created. I've tried >> disabling>UDMA on the drive, to no avail. >> >> >System info: >> > >> >Epox Nforce2 motherboard >> >FreeBSD obygden 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Wed May 11 >> >> 17:32:06>CEST 2005 ulf@obygden:/usr/obj/usr/src/sys/DEB i386 >> >> >Parts of dmesg output: >> > >> >atapci0: port >> >0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 9.0 on >> >> pci0>ata0: channel #0 on atapci0 >> >> >ata1: channel #1 on atapci0 >> >... >> >ad0: 38166MB [77545/16/63] at ata0-master UDMA100 >> >Mounting root from ufs:/dev/ad0s1a >> > >> >> Can you please attach the full output from dmesg >> >> daid > >Copyright (c) 1992-2005 The FreeBSD Project. >Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. >FreeBSD 5.4-RELEASE #0: Wed May 11 17:32:06 CEST 2005 > ulf@obygden:/usr/obj/usr/src/sys/DEB >Timecounter "i8254" frequency 1193182 Hz quality 0 >CPU: AMD Athlon(tm) processor (1403.19-MHz 686-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0x644 Stepping =3D 4 > >Features=3D0x183fbffCM OV,PAT,PSE36,MMX,FXSR> > AMD Features=3D0xc0440000 >real memory =3D 536805376 (511 MB) >avail memory =3D 511438848 (487 MB) >mptable_probe: MP Config Table has bad signature: >ACPI APIC Table: >ioapic0 irqs 0-23 on motherboard >npx0: on motherboard >npx0: INT 16 interface >acpi0: on motherboard >acpi0: Power Button (fixed) >Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 >cpu0: on acpi0 >acpi_button0: on acpi0 >pcib0: port 0xcf8-0xcff on acpi0 >pci0: on pcib0 >agp0: mem 0xe0000000-0xe1ffffff at >device 0.0 on > pci0 >pci0: at device 0.1 (no driver attached) >pci0: at device 0.2 (no driver attached) >pci0: at device 0.3 (no driver attached) >pci0: at device 0.4 (no driver attached) >pci0: at device 0.5 (no driver attached) >isab0: at device 1.0 on pci0 >isa0: on isab0 >pci0: at device 1.1 (no driver attached) >ohci0: mem 0xe4001000-0xe4001fff irq 22 >at devic >e 2.0 on pci0 >usb0: OHCI version 1.0, legacy support >usb0: on ohci0 >usb0: USB revision 1.0 >uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub0: 3 ports with 3 removable, self powered >ohci1: mem 0xe4004000-0xe4004fff irq 21 >at devic >e 2.1 on pci0 >usb1: OHCI version 1.0, legacy support >usb1: on ohci1 >usb1: USB revision 1.0 >uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub1: 3 ports with 3 removable, self powered >pci0: at device 2.2 (no driver attached) >pcib1: at device 8.0 on pci0 >pci1: on pcib1 >xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd000-0xd07f mem >0xe3000000-0xe300 >007f irq 16 at device 8.0 on pci1 >miibus0: on xl0 >xlphy0: <3c905C 10/100 internal PHY> on miibus0 >xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >xl0: Ethernet address: 00:04:76:1c:4b:d1 >pcm0: port 0xd400-0xd41f irq 18 at device 10.0 on pci1 >pcm0: >atapci0: port >0xf000-0xf00f,0x376,0x170-0x17 >7,0x3f6,0x1f0-0x1f7 at device 9.0 on pci0 >ata0: channel #0 on atapci0 >ata1: channel #1 on atapci0 >pci0: at device 13.0 (no driver attached) >pcib2: at device 30.0 on pci0 >pci2: on pcib2 >nvidia0: mem >0xdc000000-0xdc07ffff,0xd8000000-0xdbffffff,0xd0000000-0 >xd0ffffff irq 19 at device 0.0 on pci2 >acpi_tz0: on acpi0 >fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 >fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on >acpi0 >sio0: type 16550A >sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 >sio1: type 16550A >ppc0: port 0x778-0x77b,0x378-0x37f irq >7 on acp >i0 >ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >ppbus0: on ppc0 >lpt0: on ppbus0 >lpt0: Interrupt-driven port >atkbdc0: port 0x64,0x60 irq 1 on acpi0 >atkbd0: irq 1 on atkbdc0 >kbd0 at atkbd0 >pmtimer0 on isa0 >orm0: at iomem 0xcc000-0xcc7ff,0xc0000-0xcb7ff on isa0 >sc0: at flags 0x100 on isa0 >sc0: VGA <16 virtual consoles, flags=3D0x300> >vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/13.20, addr 2, iclass 3/1 >ums0: 4 buttons and Z dir. >Timecounter "TSC" frequency 1403190916 Hz quality 800 >Timecounters tick every 10.000 msec >ad0: 38166MB [77545/16/63] at ata0-master UDMA100 >Mounting root from ufs:/dev/ad0s1a OK your drive is recognized as at1=20 Here is the page from the handbook on www.freebsd.org - if you follow the=20 instructions you should be OK: =2D------------------------------------------------------------------------= =2D------------- 16.3 Adding Disks Originally contributed by David O'Brien. Lets say we want to add a new SCSI disk to a machine that currently only ha= s a=20 single drive. First turn off the computer and install the drive in the=20 computer following the instructions of the computer, controller, and drive= =20 manufacturer. Due to the wide variations of procedures to do this, the=20 details are beyond the scope of this document. Login as user root. After you have installed the drive,=20 inspect /var/run/dmesg.boot to ensure the new disk was found. Continuing wi= th=20 our example, the newly added drive will be da1 and we want to mount it on /= 1=20 (if you are adding an IDE drive, the device name will be wd1 in pre-4.0=20 systems, or ad1 in 4.X and 5.X systems). =46reeBSD runs on IBM-PC compatible computers, therefore it must take into= =20 account the PC BIOS partitions. These are different from the traditional BS= D=20 partitions. A PC disk has up to four BIOS partition entries. If the disk is= =20 going to be truly dedicated to FreeBSD, you can use the dedicated mode.=20 Otherwise, FreeBSD will have to live within one of the PC BIOS partitions.= =20 =46reeBSD calls the PC BIOS partitions slices so as not to confuse them wit= h=20 traditional BSD partitions. You may also use slices on a disk that is=20 dedicated to FreeBSD, but used in a computer that also has another operatin= g=20 system installed. This is a good way to avoid confusing the fdisk utility o= f=20 other, non-FreeBSD operating systems. In the slice case the drive will be added as /dev/da1s1e. This is read as:= =20 SCSI disk, unit number 1 (second SCSI disk), slice 1 (PC BIOS partition 1),= =20 and e BSD partition. In the dedicated case, the drive will be added simply= =20 as /dev/da1e. Due to the use of 32-bit integers to store the number of sectors, bsdlabel(= 8)=20 (called disklabel(8) in FreeBSD 4.X) is limited to 2^32-1 sectors per disk = or=20 2TB in most cases. The fdisk(8) format allows a starting sector of no more= =20 than 2^32-1 and a length of no more than 2^32-1, limiting partitions to 2TB= =20 and disks to 4TB in most cases. The sunlabel(8) format is limited to 2^32-1= =20 sectors per partition and 8 partitions for a total of 16TB. For larger disk= s,=20 gpt(8) partitions may be used. 16.3.1 Using sysinstall(8) 1. Navigating Sysinstall You may use sysinstall (/stand/sysinstall in FreeBSD versions older t= han=20 5.2) to partition and label a new disk using its easy to use menus. Either= =20 login as user root or use the su command. Run sysinstall and enter the=20 Configure menu. Within the FreeBSD Configuration Menu, scroll down and sele= ct=20 the Fdisk option. 2. fdisk Partition Editor Once inside fdisk, typing A will use the entire disk for FreeBSD. Whe= n=20 asked if you want to =E2=80=9Cremain cooperative with any future possible o= perating=20 systems=E2=80=9D, answer YES. Write the changes to the disk using W. Now ex= it the=20 =46DISK editor by typing q. Next you will be asked about the =E2=80=9CMaste= r Boot=20 Record=E2=80=9D. Since you are adding a disk to an already running system, = choose=20 None. 3. Disk Label Editor Next, you need to exit sysinstall and start it again. Follow the=20 directions above, although this time choose the Label option. This will ent= er=20 the Disk Label Editor. This is where you will create the traditional BSD=20 partitions. A disk can have up to eight partitions, labeled a-h. A few of t= he=20 partition labels have special uses. The a partition is used for the root=20 partition (/). Thus only your system disk (e.g, the disk you boot from)=20 should have an a partition. The b partition is used for swap partitions, an= d=20 you may have many disks with swap partitions. The c partition addresses the= =20 entire disk in dedicated mode, or the entire FreeBSD slice in slice mode. T= he=20 other partitions are for general use. sysinstall's Label editor favors the e partition for non-root, non-sw= ap=20 partitions. Within the Label editor, create a single file system by typing = C.=20 When prompted if this will be a FS (file system) or swap, choose FS and typ= e=20 in a mount point (e.g, /mnt). When adding a disk in post-install mode,=20 sysinstall will not create entries in /etc/fstab for you, so the mount poin= t=20 you specify is not important. You are now ready to write the new label to the disk and create a fil= e=20 system on it. Do this by typing W. Ignore any errors from sysinstall that i= t=20 could not mount the new partition. Exit the Label Editor and sysinstall=20 completely. 4. Finish The last step is to edit /etc/fstab to add an entry for your new disk. 16.3.2 Using Command Line Utilities 16.3.2.1 Using Slices This setup will allow your disk to work correctly with other operating syst= ems=20 that might be installed on your computer and will not confuse other operati= ng=20 systems' fdisk utilities. It is recommended to use this method for new disk= =20 installs. Only use dedicated mode if you have a good reason to do so! # dd if=3D/dev/zero of=3D/dev/da1 bs=3D1k count=3D1 # fdisk -BI da1 #Initialize your new disk # disklabel -B -w -r da1s1 auto #Label it. # disklabel -e da1s1 # Edit the disklabel just created and add any partitio= ns. # mkdir -p /1 # newfs /dev/da1s1e # Repeat this for every partition you created. # mount /dev/da1s1e /1 # Mount the partition(s) # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. If you have an IDE disk, substitute ad for da. On pre-4.X systems use wd. 16.3.2.2 Dedicated If you will not be sharing the new drive with another operating system, you= =20 may use the dedicated mode. Remember this mode can confuse Microsoft=20 operating systems; however, no damage will be done by them. IBM's OS/2=C2= =AE=20 however, will =E2=80=9Cappropriate=E2=80=9D any partition it finds which it= does not=20 understand. # dd if=3D/dev/zero of=3D/dev/da1 bs=3D1k count=3D1 # disklabel -Brw da1 auto # disklabel -e da1 # create the `e' partition # newfs -d0 /dev/da1e # mkdir -p /1 # vi /etc/fstab # add an entry for /dev/da1e # mount /1 An alternate method is: # dd if=3D/dev/zero of=3D/dev/da1 count=3D2 # disklabel /dev/da1 | disklabel -BrR da1 /dev/stdin # newfs /dev/da1e # mkdir -p /1 # vi /etc/fstab # add an entry for /dev/da1e # mount /1 Note: Since FreeBSD 5.1-RELEASE, the bsdlabel(8) utility replaces the o= ld=20 disklabel(8) program. With bsdlabel(8) a number of obsolete options and=20 parameters have been retired; in the examples above the option -r should be= =20 removed with bsdlabel(8). For more information, please refer to the=20 bsdlabel(8) manual page. =2D------ David =2D-=20 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Tauru= s. Currently in San Diego, CA. Sailing May bound for Europe via Panama Canal.