Date: 02 Mar 2005 09:18:56 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Perttu Laine <plaine@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: hd timeouts. Message-ID: <448y56ku5r.fsf@be-well.ilk.org> In-Reply-To: <c6ef380c05030200067ea7b60e@mail.gmail.com> References: <c6ef380c050228040776dde7c5@mail.gmail.com> <44zmxn2zle.fsf@be-well.ilk.org> <c6ef380c05030200067ea7b60e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Perttu Laine <plaine@gmail.com> writes: > > If the hardware hasn't been touched since the last time it worked, > > then a failing disk would be a pretty safe guess. If not, or > > especially if this is a new configuration, there are a few things to > > try first. One is to make sure that there is a master on the ATA bus > > containing ad5; the ATA specs say that you're not supposed to have a > > slave unless there's a master (the quickest way to fix it would be to > > move the disk from slave to master). > > I think this is not hd problem because it's new disk. Been use under > two months. But actually there's no master on ad5. I'm recently moved > to freebsd so I'd like to know if there is anything I need to conf (on > fstab etc) if I move that drive from slave to master? Like would > /dev/ad5s1d then be like ad5s1a or something? It might become ad4s1d, depending on whether your kernel is configured to"wire down" the devices. The slice and partitioning will be the same no matter what. > > And of course, cable problems are a *very* frequent issue. > > I think I'll try other cable too when I change it to be master. If you can spare an extra few minutes, try *just* changing the cable first. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448y56ku5r.fsf>