It is the vmware lsi scsi controller... I managed to fix the UFS disk (DISK A) using the procedure describe here (https://www.opensolaris.org/jive/thread.jspa?threadID=7615) but I am still struggling with the ZFS boot disk (DISK B).
On 08/10/2007, at 7:53 AM, Eric Schrock wrote: > What driver are you using? The SATA framework has a bug that prevents > ldi_open_by_devid() from working early in boot. ZFS is trying to > do the > right thing, but has to fall back on the physical device path, > which in > this case is the wrong value. > > - Eric > > On Mon, Oct 08, 2007 at 07:26:39AM +0700, Kugutsumen wrote: >> Hi, >> >> Given two disk c1t0d0 (DISK A) and c1t1d0 (DISK B)... >> >> 1/ Standard install on DISK A. >> 2/ zfs boot install on DISK B. >> 3/ I change the boot order and my zfs boot works fine. >> >> 4/ I install grub on the mbr of DISK B >> 5/ I disconnect and replace DISK A with DISK B >> >> 6/ Reboot, get the grub menu select Solaris ZFS and it panics that it >> cannot mount root path @ device XXX... >> >> This is not a ZFS specific issue since even the UFS install will fail >> to boot if I don't put back the disks in the exact order they were in >> during the initial install. >> >> What am I missing? >> >> >> >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss@opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > -- > Eric Schrock, Solaris Kernel Development http://blogs.sun.com/ > eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss