Controller changes when I boot from CD/disk - SUN

This is a discussion on Controller changes when I boot from CD/disk - SUN ; The oddest thing just happened. I just jump started a Netra240 (3 actually, but this only happened on 1) and after it rebooted it said it couldn't read the file system. I tried to look at the disks, but it ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Controller changes when I boot from CD/disk

  1. Controller changes when I boot from CD/disk

    The oddest thing just happened. I just jump started a Netra240 (3
    actually, but this only happened on 1) and after it rebooted it said it
    couldn't read the file system. I tried to look at the disks, but it
    said they didn't exist. It turns out that when booting from the disk I
    get one controller ID and when I boot from the CD I get another. I'm
    pretty sure the controller when booting from the CD is correct. Any
    idea why this might happen?


    Boot from CD:
    AVAILABLE DISK SELECTIONS:
    0. c1t0d0
    /pci@1c,600000/scsi@2/sd@0,0
    1. c1t1d0
    /pci@1c,600000/scsi@2/sd@1,0


    Boot from disk after jumpstart.
    AVAILABLE DISK SELECTIONS:
    0. c0t0d0
    /pci@1c,600000/scsi@2/sd@0,0
    1. c0t1d0
    /pci@1c,600000/scsi@2/sd@1,0


  2. Re: Controller changes when I boot from CD/disk

    In comp.unix.solaris bozothedeathmachine wrote:
    > The oddest thing just happened. I just jump started a Netra240 (3
    > actually, but this only happened on 1) and after it rebooted it said it
    > couldn't read the file system. I tried to look at the disks, but it
    > said they didn't exist. It turns out that when booting from the disk I
    > get one controller ID and when I boot from the CD I get another. I'm
    > pretty sure the controller when booting from the CD is correct. Any
    > idea why this might happen?


    They can both be correct. The hardware->controller mapping is in
    /dev/cfg. If the jumpstart vs CD boot happened to do a different probe
    order that could happen (although I would think it unusual).

    --
    Darren Dunham ddunham@taos.com
    Senior Technical Consultant TAOS http://www.taos.com/
    Got some Dr Pepper? San Francisco, CA bay area
    < This line left intentionally blank to confuse you. >

  3. Re: Controller changes when I boot from CD/disk

    Well, I booted off the CD and changed the mappings in the /etc/vfstab
    file to c0t0... and it booted fine after that. The other two 240s that
    I jumpstarted have the c1t0...

    So strange.

    Thanks for the reply


  4. Re: Controller changes when I boot from CD/disk

    In article <1134153903.129776.55270@o13g2000cwo.googlegroups.c om> "bozothedeathmachine" writes:
    >Well, I booted off the CD and changed the mappings in the /etc/vfstab
    >file to c0t0... and it booted fine after that. The other two 240s that
    >I jumpstarted have the c1t0...
    >
    >So strange.
    >
    >Thanks for the reply


    V240's ship without a DVD-ROM drive. Without that drive, there's
    nothing on the builtin IDE controller, so it gets ignored, and SCSI
    disks show up on controller 0 instead. I'm guessing that a Netra240 is
    similar.

    On a related note, if you put one of the old dual channel Symbios-based
    UltraSCSI controllers in a V240, and it has disks on it, it'll show up
    before builtin SCSI controller, as c1 in our case. When we moved to a
    QLogic Ultra160 controller, the builtin controller now shows up as c1.
    I don't believe that the old UltraSCSI is officially supported in a
    V240 anyway.

    Actually this machine now has:

    c0 - Builtin IDE w/ DVD ROM
    c1 - Builtin SCSI w/ disks
    c2 - QLogic w/ disks
    c3 - QLogic w/ disks
    c4 - Builtin SCSI w/ tape drive

    The second builtin SCSI channel winds up as c4 because all it has on
    it is a tape drive.
    --
    Jeff Wieland

  5. Re: Controller changes when I boot from CD/disk

    In comp.unix.solaris bozothedeathmachine wrote:
    > The oddest thing just happened. I just jump started a Netra240 (3
    > actually, but this only happened on 1) and after it rebooted it said it
    > couldn't read the file system. I tried to look at the disks, but it
    > said they didn't exist. It turns out that when booting from the disk I
    > get one controller ID and when I boot from the CD I get another. I'm
    > pretty sure the controller when booting from the CD is correct. Any
    > idea why this might happen?


    Probably http://sunsolve.sun.com/search/docum...y=1-26-57674-1

    Scott

+ Reply to Thread