[Summary] a clone panics on vfs_mountroot

From: Jacques Beigbeder (Jacques.Beigbeder_at_ens.fr)
Date: 12/31/04

  • Next message: Buozis, Martynas: "FW: Solaris problems"
    Date: Fri, 31 Dec 2004 10:00:32 +0100
    To: sunmanagers@sunmanagers.org
    
    

    Question was:
            I installed Solaris 9, and patches, and softwares,
            and printers and ... on a first Sun Blade 150.
            Then I cloned this installation to a second Blade 150:
            ...
            This second Blade fails to boot:
              Cannot assemble drivers for root /pci@1f,0/ide@d/disk@0,0:0
              Cannot mount root on /pci@1f,0/ide@d/disk@0,0:0 fstype ufs

              panic[cpu0]/thread=140a000: vfs_mountroot: cannot mount root

    The answer is: setenv boot-device disk
               or: setenv boot-device disk:a

    The workstation was configured with a boot-device as disk:f
    (some installation CD), so I wanted to correct and I set:
            setenv boot-device disk:0
    (may be because nowadays slice are s0, s1, and so on).
    Then the station loads the kernel but displays the message
            Cannot assemble drivers for root /pci@1f,0/ide@d/disk@0,0:0
                                                                     ^^
    A missing check somewhere? I'm allowed to set this, but it fails...

    Thanks to:
            John Dewey
            Michael Horton
            Andris Martmne
            Drew Skinner

    --
    Jacques Beigbeder                    |  Jacques.Beigbeder@ens.fr
    Service de Prestations Informatiques |     http://www.spi.ens.fr
    Ecole normale supirieure             |
    45 rue d'Ulm                         |Tel : (+33 1)1 44 32 37 96
    F75230 Paris cedex 05                |Fax : (+33 1)1 44 32 20 75
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    

  • Next message: Buozis, Martynas: "FW: Solaris problems"

    Relevant Pages

    • Re: Explain the merit of this install method
      ... All I found was that Office licenses are concurrent licenses. ... The clients are regular not Terminal Server clients. ... The installation seems to be a full one, ... everytime a new user sits at a workstation the Office 2k3 has to be ...
      (microsoft.public.office.setup)
    • Re: Networked Office
      ... > copied to the workstation. ... you are simulating workstation installation but using the network drive. ... If this is a SMART and TRUE Network Apps, I will be able to execute the ... No administration headache. ...
      (microsoft.public.office.setup)
    • Re: Networked Office
      ... > copied to the workstation. ... you are simulating workstation installation but using the network drive. ... If this is a SMART and TRUE Network Apps, I will be able to execute the ... No administration headache. ...
      (microsoft.public.windows.server.general)
    • Re: Networked Office
      ... > copied to the workstation. ... you are simulating workstation installation but using the network drive. ... If this is a SMART and TRUE Network Apps, I will be able to execute the ... No administration headache. ...
      (microsoft.public.windows.server.sbs)
    • Re: Networked Office
      ... administrative install on the server and PUSH it down to the workstations. ... Creating an Administrative Installation Point (Office 2003 Editions ... > 100 workstation) will get updated instantly without clogging up the network ...
      (microsoft.public.office.setup)