On Sun, Feb 02, 2003 at 01:52:30PM -0600, Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Brent Kearney <[EMAIL PROTECTED]> typed:
> > No /dev/ad5s1, etc., and `mount /dev/ad5s1 /home` produces only:
> > mount: /dev/ad5s1: No such file or directory
> > Do I need to make device nodes for the ad5s1 partition? I'm not sure how,
> > if so.
> Yes, you need to make device nodes. Try:
> # cd /dev
> # ./MAKEDEV ad5s1c
> Or s1a, or whatever you were using.
`/dev/MAKEDEV ad5` made all of the nodes, and I was able to mount
/dev/ad5s1e, and relieve my panic ;).
What if this system were an all-IDE system? I was planning to update
one soon, and will no doubt run into this problem. The root
filesystem device node will change names, and according to this
even if I anticipate what the new name will be (how do I do that,
anyways?), updating /etc/fstab before rebooting with the new binaries
won't help. It doesn't look like anyone followed up on that thread,
but maybe I'm using the wrong search criteria.
The note in /usr/src/UPDATING on this new ata code is quite sparse,
given what people may unexpectedly run into when updating on IDE
systems. That should probably be fixed to include the requirement of
doing not only `MAKEDEV all`, but also `MAKEDEV <your device>` to
create partition nodes, and whatever needs to be done for booting onto
the newly named partitions, if the / is on one of them.
> The reason ad0 turned into ad5 is that ata disk devices are now
> numbered statically instead of dynamically. This is a good
> thing. While it does mean that your drives move when you upgrade the
> OS this one time, it also means that they won't move when you add a
> drive to the system.
> Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/consulting.html
> Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message