Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 7 Jul 2001 23:22:07 -0400 (EDT)
From:      User Ipt Ian Patrick Thomas <ipthomas_77@yahoo.com>
To:        freebsd-questions@freebsd.org
Subject:   moving a hard drive (editing fstab)
Message-ID:  <200107080322.f683M7900513@scraemondaemon.my.domain>

next in thread | raw e-mail | index | archive | help
	I want to move my current hard drive which is on a UDMA 33 controller
to a UDMA 66 controller.  My current drive looks like this. 

Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/ad0s1a     49583    30587    15030    67%    /
/dev/ad0s1e    496111     3119   453304     1%    /var
/dev/ad0s1f   2032623  1086643   783371    58%    /usr
/dev/ad0s1g   4065262     5587  3734455     0%    /home
/dev/ad0s1h  12494951   411007 11084348     4%    /usr/local
mfs:63         254063       44   233694     0%    /tmp
procfs              4        4        0   100%    /proc

	dmesg shows this as far as info about my drive controllers goes

atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
atapci1: <HighPoint HPT366 ATA66 controller> port
0xd400-0xd4ff,0xd000-0xd003,0$
ata2: at 0xcc00 on atapci1
atapci2: <HighPoint HPT366 ATA66 controller> port
0xe000-0xe0ff,0xdc00-0xdc03,0$
ata3: at 0xd800 on atapci2

	When I had a previous drive that I had installed 3.x Stable on
connected to the UDMA 66 controller I could mount each of the slices by
doing this

mount /dev/ad5[a-h] /mnt

	When I have just the drive I want to switch to the UDMA 66 controller
connected and no other drives with the BIOS set to boot from this
controller it shows up as ad4.  I have tried editing fstab with each of the
following

/dev/ad4s1a             /               ufs     rw              1       1

	as well as

/dev/ad4a				/				ufs 	rw				1		1

	I have done a MAKEDEV ad4 and it has given me the following files

grep: ad4a: Device not configured
grep: ad4b: Device not configured
grep: ad4c: Device not configured
grep: ad4d: Device not configured
grep: ad4e: Device not configured
grep: ad4f: Device not configured
grep: ad4g: Device not configured
grep: ad4h: Device not configured
grep: ad4s1: Device not configured
grep: ad4s2: Device not configured
grep: ad4s3: Device not configured
grep: ad4s4: Device not configured

	This is using ls | grep ad4* for above about.  ad0 shows up as this
however

Binary file ad0a matches
Binary file ad0b matches
Binary file ad0c matches
Binary file ad0e matches
Binary file ad0f matches
Binary file ad0g matches
Binary file ad0h matches
Binary file ad0s1 matches
Binary file ad0s1a matches
Binary file ad0s1b matches
Binary file ad0s1c matches
Binary file ad0s1e matches
Binary file ad0s1f matches
Binary file ad0s1g matches
Binary file ad0s1h matches

	My kernel has the following

# ATA and ATAPI devices
device          ata0    at isa? port IO_WD1 irq 14
device          ata1    at isa? port IO_WD2 irq 15
device          ata
device          atadisk                 # ATA disk drives
device          atapicd                 # ATAPI CDROM drives
options         ATA_STATIC_ID           #Static device numbering

	I think I'm close to solving this problem but I have spent way to much
time editing my /etc/fstab file with ed after making errors previous.

Thanks in advance
uname -r
4.3-RELEASE

Ian

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?200107080322.f683M7900513>