Hi, whenever I create a new zfs my PC hangs at boot. Basically where the login screen should appear. After booting from livecd and removing the zfs the boot works again. This also happened when I created a new zpool for the other half of my HDD. Any idea why? How to solve it? -- This message posted from opensolaris.org
Please help. :( I use snv134 -- This message posted from opensolaris.org
On 5/28/2010 1:24 PM, schatten wrote:> Hi, > > whenever I create a new zfs my PC hangs at boot. Basically where the login screen should appear. After booting from livecd and removing the zfs the boot works again. > This also happened when I created a new zpool for the other half of my HDD. > Any idea why? How to solve it? >Schatten, You need to be a buit more specific. Describe exactly what you are doing, step by step. Especially how your disks are laid out - is the boot disk a single OpenSolaris parition, or are you sharing with other OSes? Do you mean that you have an already-working b134 install on a disk, and that you''re trying to add another zfs filesystem to the rpool? Or are you trying to add another disk/partition as a whole new zpool? Or something else? -- Erik Trimble Java System Support Mailstop: usca22-123 Phone: x17195 Santa Clara, CA
Okay. I had/have a running snv134 install on one half of my disk. I created a zfs (zfs create rpool/VB) for my virtualbox. Then zfs set mountpoint=/export/home/schatten/VirtulBox rpool/VB. Then a reboot and it hangs right before the login should appear. I removed the zfs with an OSOL livecd and booting works. Then I tried to add the other half of my disk. First formatting it, then zpool create c5d1p0 (not sure exactly, but zpool list showed the other half as up and running). Reboot, same as above. -- This message posted from opensolaris.org
I should note that all of it works. I have access to the ZFS/zpool while running OSOL. I can create files and stuff in the newly created zfs but the reboot hangs. Looks like the reboot has a flaw. Not to mention the reboot is no real reboot. 2009.06 had a reboot that powered off the PC. snv134 reboot means that only the OS is being rebooted. Hard to describe what I mean. When I do a reboot OSOL brings me right back to the kernel info message, hostname etc... Maybe that is related. -- This message posted from opensolaris.org
Upsala. And another note: A shutdown brings the same results. Hangs before the login screen. So no matter if I do a reboot or a powercycle. I also can''t revert to OSOL 2009.06 as my hardware is not recognized. 2009.06 won''t find my two SLI graphiccards. -- This message posted from opensolaris.org
On 5/29/2010 12:22 AM, schatten wrote:> Okay. > > I had/have a running snv134 install on one half of my disk. I created a zfs (zfs create rpool/VB) for my virtualbox. Then zfs set mountpoint=/export/home/schatten/VirtulBox rpool/VB. Then a reboot and it hangs right before the login should appear. > I removed the zfs with an OSOL livecd and booting works. > > Then I tried to add the other half of my disk. > First formatting it, then zpool create c5d1p0 (not sure exactly, but zpool list showed the other half as up and running). Reboot, same as above. >OK, let me get this straight: (1) Your boot disk has a Solaris fdisk partition that takes up 50% of the actual disk space (2) Inside that fdisk partition, you have b134 installed, with the zpool being the default ''rpool'' (3) There exists the following zfs filesystems: rpool/export rpool/export/home rpool/export/home/schatten (4) You do a ''zfs create rpool/VB'' (5) You then do ''zfs set mountpoint=/export/home/schatten/VB'' (6) Everything works fine then, up until you reboot the system, after which is hangs before displaying the GDM login screen. Right? Also, you are NOT going to be able to use the 2nd fdisk partition on your boot drive - OpenSolaris only recognizes 1 Solaris fdisk partition per drive at this point. It will recognize more than one Solaris *slice* inside an fdisk partition, though. -- Erik Trimble Java System Support Mailstop: usca22-123 Phone: x17195 Santa Clara, CA
Yep, that is correct. The rpool also has stuff like swap and 1-2 other mountpoints I forgot. Just the default installation layout. I am really not sure if I did something wrong or if there is a bug. But if it is a bug, why do only I see it?> OpenSolaris only recognizes 1 Solaris fdisk partitionper drive at this point. So I can create an zpool on my other HDD and OSOL will see and work with it? -- This message posted from opensolaris.org
On 5/29/2010 12:48 AM, schatten wrote:> Yep, that is correct. The rpool also has stuff like swap and 1-2 other mountpoints I forgot. Just the default installation layout. > I am really not sure if I did something wrong or if there is a bug. But if it is a bug, why do only I see it? >Hmm.... Can you try this when you create the VB filesystems: mkdir -p /export/home/schatten/VB zfs create -o mountpoint=/export/home/schatten/VB rpool/VB and let me know if it hangs as before? I tried what you are doing on a machine running b118, and it works fine.>> OpenSolaris only recognizes 1 Solaris fdisk partition >> > per drive at this point. > So I can create an zpool on my other HDD and OSOL will see and work with it? >Yes. You can either use the whole drive, or create fdisk partitions, giving ZFS one of the fdisk paritions. Either way, ZFS will use the other hard drives happily. -- Erik Trimble Java System Support Mailstop: usca22-123 Phone: x17195 Santa Clara, CA
Hi. Sorry, it took a bit longer because I had to reinstall OSOL. With a FRESH snv134 install the commands from you worked. I just did them and did a soft reboot. The change I did from a fresh install and my previous are pretty small. If you are a devel I can email you my changes and maybe that will help in pinpoint the error because this error is reproducable at least on my rig. -- This message posted from opensolaris.org
Just FYI. The error was that I created the ZFS at the wrong pool. rpool/a/b/c rpool/new I mounted "new" in a directory of rpoo/ "c". Seems like this hierarchical mounting is not working like I thought. ;) -- This message posted from opensolaris.org