2011-07-05 17:11, Fajar A. Nugraha пишет:
On Tue, Jul 5, 2011 at 8:03 PM, Edward Ned Harvey
<opensolarisisdeadlongliveopensola...@nedharvey.com> wrote:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Orvar Korvar
Here is my problem:
I have an 1.5TB disk with OpenSolaris (b134, b151a) using non AHCI.
I then changed to AHCI in BIOS, which results in severe problems: I can
not
boot the system.
I suspect the problem is because I changed to AHCI.
This is normal, no matter what OS you have. It's the hardware.
If you start using a disk in non-AHCI mode, you must always continue to use
it in non-AHCI mode. If you switch, it will make the old data inaccessible.
Really? old data inaccessible?
Kind of. You can not access it now, right? ;)
So the question is, does similar workaround exists for (open)solaris?
One of the ways is to have Solaris remap the boot devices.
When you change the boot device paths, and this includes
switching the access mode in BIOS (the controller number
and driver would probably change), Solaris would give you
a panic during boot and restart.
See this list or the internet for how to boot Solaris with KDB
(kernel debugger) and/or verbose mode - this should keep
the computer from rebooting and allow you to read the strings
on the screen, along the lines: zfs/vfs can't mount the root,
panic, tried device paths /pci/something.
If that's the case, you can return the BIOS to the mode where
Solaris boots okay, and try to fix up the EEPROM - rather its
x86 emulation in file /boot/solaris/bootenv.rc - which stores
"hardware configuration".
For an easy solution you can try to comment away the line
like (if it is there in the first place):
setprop bootpath /pci@7b,0/pci1022,7458@11/pci1000,3060@2/sd@3,0:a
Otherwise you may have to discover and insert the correct
line by using the livecd/installcd or the failsafe boot mode
(Solaris 10/SXCE) while and running "devfsadm -Cv"
in order for it to generate new disk/slice paths.
Then you can use "ls -la /dev/dsk" and see what PCI paths
are assigned (possibly this would lead you to /devices/
first, though).
There is another possible solution: boot from livecd while
in AHCI mode, and import/export the rpool. This may change
the device names/links in the ZFS pool header, helping
to "rename" them to the new controller numbers...
Good luck! ;)
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
