On Sat, May 7, 2011 at 9:41 PM, Hudes, Dana <[email protected]> wrote: > You could manually mount the devices in the io domain and see if it looks > like a root disk. If so then find etc/nodename on it and that will tell you. > With 20 to check I would cobble a shell script together which checks nodename > file for you and reports.
main thing I found out is that the device name included ssd@ in the OS, is different from the boot-device name including disk@ Thanks . > > ----- Original Message ----- > From: [email protected] > <[email protected]> > To: [email protected] <[email protected]> > Sent: Sat May 07 13:40:02 2011 > Subject: [ldoms-discuss] fixing a SAN boot-device in an IO Domain > > I have a T5440 with an LDOM and IO Domain. I had to tear down the > domain to do some maintenance, but now cannot find the right device > name to get the system booting. I can boot off the network, but even > being able to see the boot device, I cannot figure out exactly what I > should be using since the boot-device listed in the newly created ldom > no longer works. I can boot off the nxge0 which is how the original > image go put on the san device. > > Even using the other LDOM (we're clustering the LDOMs) to try and > figure out how that is configured, I've been unsuccessful. I > > The LDOM is 2.0, and had been booting off a qlogics 2462, and there > are approximately 20 san devices presented to the controllers. > > > Ideas? > > Ben > _______________________________________________ > ldoms-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss > _______________________________________________ ldoms-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
