Re: filesystem disappeared following 4.2 -> 4.7 upgrade

From: Brent Kearney (brent_at_kearneys.ca)
Date: 02/02/03

  • Next message: AL Grant: "Archive Mail"
    Date: Sun, 02 Feb 2003 12:20:43 -0800
    To: dwbear75@gmail.com
    
    

    On Sun, Feb 02, 2003 at 01:52:30PM -0600, Mike Meyer wrote:
    > In <20030202191806.GA14696@kearneys.ca>, Brent Kearney <brent@kearneys.ca> 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.

    Thanks Mike;

    `/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
    thread:

    http://www.freebsd.org/cgi/getmsg.cgi?fetch=2388792+2394647+/usr/local/www/db/text/2003/freebsd-questions/20030112.freebsd-questions

    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.

    Best regards,

    Brent

    > 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
    > --
    > Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html
    > Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

    To Unsubscribe: send mail to majordomo@FreeBSD.org
    with "unsubscribe freebsd-questions" in the body of the message

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: AL Grant: "Archive Mail"

    Relevant Pages

    • [PATCH] nbd: fix device names
      ... It seems more appropriate to call the devices "nbX" rather than "nbdX", ... since that's what the device nodes are actually named. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: USB Card Reader.
      ... individual partition nodes when the device nodes for the reader are ... Seems that udev thinks it's a floppy drive...? ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
      (Debian-User)
    • Re: missing serial script in /etc?
      ... Making the device nodes in Etch, which uses udev, doesn't really ... Flags: spd_normal skip_test ... To what physical port are you trying to connect? ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • Re: USB Card Reader.
      ... I followed the instructions in and now have the device nodes available. ... Everything *seems* to be working (I get a no media error message if I try to mount an empty slot), ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
      (Debian-User)
    • Re: /dev/rhd00 does not exist error when running fdisk...
      ... That creates any necessary device nodes according to what devices are ... mknod /dev/rhd00 c 1 0 ... Here is a block device listing from a 5.0.7 system with 2 ide drives, ...
      (comp.unix.sco.misc)