Re: No root filesystem

On Fri, Aug 22, 2008 at 5:38 PM, Randy Bush <randy_at_psg.com> wrote:
>> It tried to mount ufs:/dev/ad6s1a, which is correct, but somehow
>> came up empty.  At the "Manual root filesystem specification" prompt,
>> "?" did not list any devices.
>
> i had similar, but it showed devices
>
> reboot and it was ok
>
> this was with gmirror
>
> randy

Apart from a hardware failure (which is possible -- try a liveCD based
OS to see whether or not the disk can be spotted and read from), there
are a number of commits that have gone in recently which could be
affecting your system.

A few which caught my eye (from the CVS emails) for amd64 are listed
below. I'm not listing the kernel core specific CVS commits which
could be affecting your system (there are about 12 or so commits which
affected core kernel components, like VFS, scheduling, MPSAFE TTY
support, etc).

Make sure to boot with the older, stable kernel (boot kernel.old at
the manual option prompt), and do the following:

1. Nuke /usr/obj:
    rm -Rf /usr/obj
2. Copy stable kernel to another dir:
    cp -Rpf /boot/kernel.old /boot/kernel.stable
3. Rebuild your system:
    make NO_CLEAN=0 cleandir clean buildworld buildkernel installkernel
4. Reboot system.

... and see if the issue persists. If so, please post the info about
your SATA chipset / card that you use to boot with your system so the
issue can be debugged further.

Good luck,
-Garrett

==============

jhb         2008-08-22 02:14:23 UTC

 FreeBSD src repository

 Modified files:
   sys/amd64/include    pci_cfgreg.h
   sys/amd64/pci        pci_cfgreg.c
   sys/dev/acpica       acpi.c
   sys/i386/include     pci_cfgreg.h
   sys/i386/pci         pci_cfgreg.c
 Log:
 SVN rev 181987 on 2008-08-22 02:14:23Z by jhb

 Extend the support for PCI-e memory mapped configuration space access:
 - Rename pciereg_cfgopen() to pcie_cfgregopen() and expose it to the
   rest of the kernel.  It now also accepts parameters via function
   arguments rather than global variables.
 - Add a notion of minimum and maximum bus numbers and reject requests for
   an out of range bus.
 - Add more range checks on slot/func/reg/bytes parameters to the cfg reg
   read/write routines.  Don't panic on any invalid parameters, just fail
   the request (writes do nothing, reads return -1).  This matches the
   behavior of the other cfg mechanisms.
 - Port the memory mapped configuration space access to amd64.  On amd64
   we simply use the direct map (via pmap_mapdev()) for the memory mapped
   window.
 - During acpi_attach() just after loading the ACPI tables, check for a
   MCFG table.  If it exists, call pciereg_cfgopen() on each subtable
   (memory mapped window).  For now we only support windows for domain 0
   that start with bus 0.  This removes the need for more chipset-specific
   quirks in the MD code.
 - Remove the chipset-specific quirks for the Intel 5000P/V/Z chipsets
   since these machines should all have MCFG tables via ACPI.
 - Updated pci_cfgregopen() to DTRT if ACPI had invoked pcie_cfgregopen()
   earlier.

 MFC after:      2 weeks

 Revision  Changes    Path
 1.15      +1 -0      src/sys/amd64/include/pci_cfgreg.h
 1.111     +137 -3    src/sys/amd64/pci/pci_cfgreg.c
 1.251     +41 -0     src/sys/dev/acpica/acpi.c
 1.15      +1 -0      src/sys/i386/include/pci_cfgreg.h
 1.130     +42 -36    src/sys/i386/pci/pci_cfgreg.c

kib         2008-08-21 09:58:18 UTC

 FreeBSD src repository

 Modified files:        (Branch: RELENG_7)
   sys/amd64/amd64      exception.S
 Log:
 SVN rev 181961 on 2008-08-21 09:58:18Z by kib

 MFC r181823:
 Remove the check for mode and conditional swapgs in doreti_iret_fault,
 we already have right gs base in the MSR.

 Revision   Changes    Path
 1.129.2.2  +3 -6      src/sys/amd64/amd64/exception.S

jhb         2008-08-20 17:44:02 UTC

 FreeBSD src repository

 Modified files:        (Branch: RELENG_7)
   sys/amd64/amd64      db_disasm.c
   sys/i386/i386        db_disasm.c
 Log:
 SVN rev 181930 on 2008-08-20 17:44:02Z by jhb

 MFC: Decode "exotic" instructions such as pause as well as "cmov*" on i386.

 Revision   Changes    Path
 1.31.2.1   +68 -9     src/sys/amd64/amd64/db_disasm.c
 1.29.10.1  +84 -10    src/sys/i386/i386/db_disasm.c

jhb         2008-08-20 18:01:59 UTC

 FreeBSD src repository

 Modified files:        (Branch: RELENG_6)
   sys/amd64/amd64      db_disasm.c
   sys/i386/i386        db_disasm.c
 Log:
 SVN rev 181932 on 2008-08-20 18:01:59Z by jhb

 MFC: Decode "exotic" instructions such as pause as well as "cmov*" on i386.

 Revision  Changes    Path
 1.30.2.2  +68 -9     src/sys/amd64/amd64/db_disasm.c
 1.29.2.1  +84 -10    src/sys/i386/i386/db_disasm.c

julian      2008-08-20 02:48:33 UTC

 FreeBSD src repository

 Modified files:
   sys/sys              sysctl.h
 Log:
 SVN rev 181890 on 2008-08-20 02:48:33Z by julian

 Fix wierd integration error
 No idea where this came from

 Revision  Changes    Path
 1.161     +1 -1      src/sys/sys/sysctl.h

jhb         2008-08-19 19:53:52 UTC

 FreeBSD src repository

 Modified files:
   sys/amd64/include    pcpu.h
   sys/arm/include      pcpu.h
   sys/i386/include     pcpu.h
   sys/ia64/include     pcpu.h
   sys/mips/include     pcpu.h
   sys/powerpc/include  pcpu.h
   sys/sparc64/include  pcpu.h
   sys/sun4v/include    pcpu.h
   sys/sys              pcpu.h types.h
 Log:
 SVN rev 181875 on 2008-08-19 19:53:52Z by jhb

 Export 'struct pcpu' to userland w/o requiring _KERNEL.  A few ports
 already define _KERNEL to get to this and I'm about to add hooks to
 libkvm to access per-CPU data.

 MFC after:      1 week

 Revision  Changes    Path
 1.50      +2 -2      src/sys/amd64/include/pcpu.h
 1.7       +4 -0      src/sys/arm/include/pcpu.h
 1.53      +3 -2      src/sys/i386/include/pcpu.h
 1.21      +2 -2      src/sys/ia64/include/pcpu.h
 1.2       +3 -2      src/sys/mips/include/pcpu.h
 1.28      +2 -1      src/sys/powerpc/include/pcpu.h
 1.24      +2 -2      src/sys/sparc64/include/pcpu.h
 1.12      +3 -2      src/sys/sun4v/include/pcpu.h
 1.27      +4 -4      src/sys/sys/pcpu.h
 1.99      +1 -1      src/sys/sys/types.h