Date: Sat, 25 Nov 2000 10:06:25 -0600 (CST) From: koziol@ncsa.uiuc.edu To: "Sean O'Connell" <sean@stat.Duke.EDU> Cc: stable@freebsd.org Subject: Re: Losing ATA channel? Message-ID: <200011251606.eAPG6PF41111@hawkwind.ncsa.uiuc.edu> In-Reply-To: <20001124194437.B14254@stat.Duke.EDU> "from Sean O'Connell at Nov 24, 2000 07:44:37 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Sean,
Here's the ATA section of my kernel config:
# 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
device atapifd # ATAPI floppy drives
options ATA_STATIC_ID #Static device numbering
I've been running stable on this machine for quite a while and the drive
the /data partition is on was working fine until about two months ago and then
started getting the timeout messages that people have been mentioning lately.
I unmounted it then and haven't had the time to take a look into it until
recently.
I have MAKEDEV'd ad3, ad3s1a, ad4 and ad4s1a, so the device should be
configured properly.
It definitely looks like the first HPT366 channel is not being attached
to an ata channel and subsequently, my drive is being missed... (Not 100%
certain the two are related though)
Thanks for your help,
Quincey
> : I'm having problems with my machine locating it's second hard drive.
> :I've got the first hard drive and IDE ZIP drive on my first IDE channel (master
> :and slave, respectively) and a CD-ROM as the master on my second IDE channel.
> :I've got the second hard drive as the master on the Highpoint ATA66 controller,
> :but every time I try to mount it with "mount /data", mount whines about "Device
> :not configured". About two month ago I started having problems with the drive,
> :but didn't have a chance to look into it until now. I'm running 4.2-STABLE as
> :of November 22nd.
> : From my dmesg output (attached below), it looks like there should be four
> :ata devices, but only ata1-3 are being attached to my controllers and the
> :first HPT366 is being skipped over.
> : Here's the fstab which used to work:
> :
> : # Device Mountpoint FStype Options Dump Pass#
> : /dev/ad0s1b none swap sw 0 0
> : /dev/ad0s1a / ufs rw 1 1
> : /dev/ad0s1f /usr ufs rw 2 2
> : /dev/ad0s1e /var ufs rw 2 2
> : proc /proc procfs rw 0 0
> : /dev/acd0c /cdrom cd9660 ro,noauto 0 0
> : /dev/afd0c /zip ufs rw,noauto 0 0
> : /dev/ad4s1e /data ufs rw 2 2
> :
>
> Quincey-
>
> What entry/entries are in your kernel for ata support? I would
> guess that you should have just
>
> device ata
> device atadisk
> device atapicd
> device atapifd
>
> If you have
>
> options ATA_STATIC_ID #Static device numbering
>
> Did you completely wipe this machine when you did the install? The
> ad4* are not part of the standard devices made. Maybe if you did
>
> cd /dev; sh MAKEDEV ad4
> cd /dev; sh MAKEDEV ad4s1a
>
> However, it doesn't seem that the drive is showing up in the boot
> probe .. (not sure if that is due to the missing ad4s1* or it is
> just not seeing anything on that channel).
>
> S
> 1--------01---------01--------01--------01--------01--------01--------0
> Sean O'Connell sean@stat.Duke.EDU
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011251606.eAPG6PF41111>