Missing 30 Gig in -Current after cross-install

From: Lane Holcombe (lane_at_joeandlane.com)
Date: 07/20/04

  • Next message: Oliver Fuchs: "fortune database"
    Date: Mon, 19 Jul 2004 22:39:19 -0500 (CDT)
    To: freebsd-questions@freebsd.org
    
    

    I have an 8Gig drive and a 30Gig drive on my PC.
     
    the 8Gig drive is known as /dev/ad2*
    the 30Gig drive is known as /dev/ad0*
     
    I've been running 4.9 STABLE since December on ad0, and I have been using ad2 for SWAP
    and TMP and other crap.
     
     
    Today I ran fdisk,disklabel, and newfs on ad2 and successfully completed the installation
    process to upgrade to 5.0-CURRENT. However, when I booted into -CURRENT, ad0 did not
    appear in /dev.
     
    The boot manager properly offers the option to boot from ad0 or ad2, and FreeBSD properly
    boots on either drive - -STABLE boots on ad0 and -CURRENT boots on ad2.
     
    When I boot into -STABLE I can still mount slices from ad2 as before, but I *cannot* mount
    slices from ad0 when I boot into -CURRENT.
     
    I first tried to auto-mount ad0 slices in -CURRENT by including them in /etc/fstab. When that
    failed I commented those entries out and rebooted and then tried to manually mount a slice
    from ad0 ... to no avail. "ls -al /dev | grep ad0" reveals that there are no entries for ad0*.
     
    Furthermore, there are no entries in the new /dev which resemble a disk device other than
    those for ad2.
     
    What is I'm gonna do?
     
    Thanks for your attention,
     
    Lane
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: Oliver Fuchs: "fortune database"

    Relevant Pages

    • 5.2.1 hangs on boot where 5.1 does not (ATA issue)
      ... I can boot just fine using 5.1-RELEASE-p11 (see partial bootlog ... somewhere around getting ata1 online. ... ad2: setting PIO4 on Intel ICH2 chip ... setting UDMA100 on Intel ICH2 chip ...
      (freebsd-current)
    • Re: Help with boot0
      ... To be sure which HD I'm on, I made (empty) directories in the root ... called..AD0 or ..AD1. ... If I interrupt the boot process, at the command prompt I can use the ...
      (freebsd-questions)
    • Re: FreeBSD > 4.11 hardware issue with Asus PSCH-SR/SATA mobo
      ... ignore ar0. ... ad2 will still appear in the boot sequence. ... http://dban.sourceforge.net/ and grab the floppy version. ...
      (comp.unix.bsd.freebsd.misc)
    • Re: FreeBSD system stops while booting
      ... If I boot my FreeBSD syste, it only goes up to the point where the HDs ... Waiting 5 seconds for SCSI devices to settle ... The real question for you though is why is your ad0 not ...
      (comp.unix.bsd.freebsd.misc)
    • recent commits break via 8235 ata
      ... It boots and ad0 is not detected so it can't mount root. ... boot -v working: ... ata1: reiniting channel .. ... acd0: ...
      (freebsd-current)