Tuesday, February 3, 2009

Easy EON storage setup






To answer some recent questions:
- Can I set the my own hostname? Yes for USB/CF installs
- Will my changes survive a reboot? Yes for USB/CF installs

13 comments:

mikeathome said...

Thank you Andre!

I tried to setup a test environment on Virtualbox.

Is it possible to install EON on a vdi? I get a 'Failure to cut slice...' with install.sh; a partition will not be created.

mike

Andre said...

I have not had the chance to test it on a vdi.

You can try either:
- manually copying the entire eon.iso root contents into the vdi and manually running installgrub.

- do a ksh -x install.sh | tee -a /tmp/foo and post back the contents so I could take a look.

Thanks

mikeathome said...

Andre,
I did the second, here's the report (c0d0 - vdi, c2t0d0 - USB stick):

This script installs EON live to a destination listed below:
1. c0d0 (508MB)
2. c2t0d0 (249MB)
Enter destination choice:
!!! WARNING !!! All data on device [c0d0] will be LOST !!!

Proceed with formatting, install [y,n?] searching /etc/mnttab ...
searching /mnt/eon0 ...
found: /mnt/eon0/boot/grub/stage1
found: /mnt/eon0/boot/grub/stage2
c0d0 :: /dev/rdsk/c0d0s0 :: /dev/dsk/c0d0s0
cut_root_slice /dev/rdsk/c0d0p0 failed
newfs_slice /dev/rdsk/c0d0s0 failed
Updating master boot sector destroys existing boot managers (if any).
continue (y/n)?stage1 written to partition 0 sector 0 (abs 2048)
stage2 written to partition 0, 267 sectors starting at 50 (abs 2098)
stage1 written to master boot sector
EON install complete on /dev/dsk/c0d0s0

Bootmgr is written. Install on a USB stick from within the VB works but does not help, as VB can't boot from USB. Will try manual copy later.

Thanks,
mike

Andre said...

Can you send me the output of:
ls -al /dev/dsk/c0d0*

mikeathome said...

Here is the output of ls -al /dev/dsk/c0d0*:

lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0p0 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:q
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0p1 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:r
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0p2 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:s
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0p3 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:t
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0p4 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:u
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s0 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:a
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s1 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:b
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s10 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:k
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s11 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:l
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s12 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:m
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s13 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:n
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s14 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:o
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s15 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:p
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s2 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:c
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s3 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:d
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s4 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:e
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s5 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:f
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s6 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:g
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s7 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:h
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s8 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:i
lrwxrwxrwx 1 root root 50 Feb 9 09:56 /dev/dsk/c0d0s9 -> ../../devices/pci@0,0/pci-ide@1,1/ide@0/cmdk@0,0:j

Mark50+ said...

I did manage to install it with vmware workstation.
Same problem as described - no s0 slive, so I manually created it & reinstalled which worked inspite of the errors.

I was keen to add some network drivers, but didn't find the mentioned imgsol.sh, etc scripts.

mikeathome said...

Mark,
I found the scripts in the original EON Contest Entry on the Solaris HP:
http://opensolaris.org/os/project/awards/awards_land/Entries/

in the 0.58.7 tarball:

http://dlc.sun.com/osol/awards/downloads/current/EON.tar.gz

Not sure if there is an update.

mike

Andre said...

Mark, Mike
I had a chance to test this and can reproduce the problem on vmware. I will update when I figure out the problem.

Mike
that imgsol.sh won't work with the 104 version. Lotsa changes. May I ask what driver you wish to add? Realtek nic?

Mark50+ said...

a new intel chipset for a quad port card that is still dev in the ibg driver.
Also would go 64 bit & see what it can do in a grunty box.

mikeathome said...

I guess people would be interested in the Realtec and Marvell Yukon. Lots MBs with these onboard chipsets.

I followed your advice and got a GX620 (this is the one and only I could find with a Broadcom | Intel onboard, apart from expensive new I7 platform).

mike

corndog said...

Hello Andre,

Trying to test on a Norco DS520 which has a Marvel SATA controller in it. Does eon support this?

Andre said...

Corndog,

I'm not sure about the marvell. It's been kinda hit or miss with opensolaris.

One way to test would be to boot it with the latest opensolaris live CD and see if the drives show up. If it does it would be easy to add the driver to EON.

me said...

Hi there - I was wondering if there are plans to enable eonstore to run from a regular hard disk instead of ramdisk. In my case, I'd like to embed this as a virtual machine so the ramdisk merely consumes resources that I could otherwise use for the base system.

Thanks!