It is available in a CIFS and Samba flavor
EON 64-bit x86 CIFS ISO image version 0.59.1 based on snv_114- eon-0.591-114-64-cifs.iso
- MD5: a8560cf9b407c9da846dfa773aeaf676
- Size: ~83Mb
- Released: Tuesday 26-May-2009
EON 64-bit x86 Samba ISO image version 0.59.1 based on snv_114- eon-0.591-114-64-smb.iso
- MD5: c845255be1d3efec26fdc919963b15de
- Size: ~96Mb
- Released: Tuesday 26-May-2009
EON 32-bit x86 CIFS ISO image version 0.59.1 based on snv_114- eon-0.591-114-32-cifs.iso
- MD5: 9c0c093969c931f9a4614663faea90db
- Size: ~53Mb
- Released: Tuesday 26-May-2009
EON 32-bit x86 Samba ISO image version 0.59.1 based on snv_114- eon-0.591-114-32-smb.iso
- MD5: 0a82dda197ab8a55007ba83145c0a662
- Size: ~66Mb
- Released: Tuesday 26-May-2009
- fixed multi-cpu support
- ssh keys and config files added to backup list
- backup list separated from updimg.sh and located on USB/CF root
- added dtrace to help with future webgui/bui interface metrics
- added marvell 88sx and AHCI drivers (intel Bad Axe2 motherboard support)
You can roll your current custom changes into the new 0.59.1 version by executing updimg.sh with arguments/path to the new unpacked x86.eon image. Please read full details first on upgrading EON from an older post here.
updimg.sh /mnt/eon0/boot/x86_new.eon
85 comments:
Hi, whats up with the strange upgrade process? Is EON not built with IPS? I thought by now every distro would have clone + update from the internet support :(
This is very nice. However, as I've seen, port-multiplexing (PMP) for eSATA is completely missing in OpenSolaris, or at least for Silicon Image SATA controllers, which make OpenSolaris useless to me. This is unfortunate, since ZFS looks like the most capable filesystem for my 5-disk RAID array.
what,
It is an appliance type NAS that's compatible with IPS binaries/packages, but as it aims to have a small footprint, including the packaging state db would kill the size of the distro. You can use IPS binaries with it, more here:
http://eonstorage.blogspot.com/2009/05/eon-zfs-nas-meets-ips-packages.html
Felipe,
True, driver issues do hamper opensolaris and people from trying the awesome features and capabilites of ZFS. It is compatible with some very good sil3124 controllers if those would do for you.
Hi Andre,
it's kinda surprising, but cifs transfer speed under eon is different than under osol. Under eon it's up to max 100mbit speed in both directions. Under osol write is about 8.5mb/s, read is a little less (another surprise for me). I'm glad eon have made it better :)
Also, could you post a tutorial how to use your eon kit?
Is possible to boot eon from flash drive and mount some essential system mount points on the existing raidz? So I will be able to install packages, etc without updating eon image and wasting ram on the bigger ram image?
scf,
[1uote]Also, could you post a tutorial how to use your eon kit?[quote]
The info is all here on the blog. Expand the posts on the right and start from post #1.
The configuration scripts are setup, install.sh, updimg.sh.
To add mounts etc see the customizing post. Let me know if this answers what you're trying to achieve.
http://eonstorage.blogspot.com/2009/03/customizing-and-optimizing-eon.html
Nice work dude. Sounds interesting and I want to try it but need a SPARC build, please.
thx
jake
Hi Andre & all,
thanks for publishing the b_114 based version that fast.
Unfortunately my systems crashes using that version (very early at the boot screen) with a "Unrecoverable Machine-Check Exception". I can't see any further log messages, because of rebooting automaticly.
The same hardware runs with osol 2008.11 perfect (except the known bugs, memory leaks etc.)
To be sure it is not caused by using the EON distribution, I've tried other b_114 based versions, same problem. The latest working version for me seems to be b_110.
Just in case somebody else has a similar problem:
Board: Tyan Thunder h2000M (S3992-E)
CPU: One Opteron Dual Core (second socket left empty)
RAM: 4GB (in two modules)
for the testbed, there are no additional cards pluged in.
In case somebody has an idea how to solve that issue - you are very welcome :-)
kind regards
Robert
Jake,
Unfortunately, I do not have bare metal sparc hardware that boots from USB/CF to test dev on.
Robert,
You can try doing a kmdb boot with the other snv_114 src (eon does don't have the mdb bits) and post it in the opensolaris forums. Please post me a link if you get to do it. I'll take a look.
Can you tell if either eon or other snv_114 boot src will boot to single user mode? If it does you can boot in stages with -v and maybe see the last script that is called before the problem.
Hello Andre,
thank You for Your nike work!
I wanted to ask can I use EON 0.59.1 with LSI MegaRAID card (just to hook up my 8 SAS drives in JBOD mode) out of the box ?
If not how can I add megaraid driver to EON ? Thanks in advance!
Denis,
All you need to do is identify the driver, add it /kernel/drv/ and amd64 and make an entry in /etc/name_t0_major.
http://eonstorage.blogspot.com/2009/02/adding-your-own-drivers-to-eon.html
Identifying the driver however is the tricky part if you got that down then you're all set.
One way to do it is boot one of the open solaris live CD 2008, 2009a and see which driver it uses if the card works after booting then just go get that driver.
You can check with prtconf -D to help.
It seems to me I've found this driver on my fresh 2009.06 install. It's /kernel/drv/mega_sas and /kernel/drv/mega_sas.conf. I must copy those onto live EON and follow your older post ?
Sorry for dumb questions cause last time I worked with Solaris was 2.8
Denis,
That is correct for 32-bit versions. For the 64-bit version you would also add the corresponding /kernel/drv/amd64/mega_sys.
I must also add that the proper driver to add would come from the corresponding snv version of eon. So for 0.59.1 built on snv_114, you would pull the /kernel/drv/mega_sys, kernel/drv/mega_sas.conf and /kernel/drv/amd64/mega_sas from the snv_114 DVD to avoid memory leaks and other possible downsides.
I've struggled all day and finally inserted mega_sas from os2009.06 to eon. The next problem is that driver is not loading automatically, I need to add_drv and update_drv every time I reboot EON.
I added a line mega_sas 61 to /etc/name_to_major, but no luck. I'll try to download nv_114 to get drivers from correct kernel version. One more q, is there a way to set jumbo mtu 9000 for e1000g interfaces I have in the box ?
Denis,
Did you preserve the image with updimg.sh after adding your driver and /etc/name_to_major changes?
Are you running 32 or 64-bit eon?
for mtu 9000, after making your changes to /kernel/drv/e1000g.conf add it to the backup list in /mnt/eon0/.backup so that the changes are preserved when you run updimg.sh. It's best to very them working before running a update.
So you should have a one time addition to /mnt/eon0/.backup of:
/kernel/drv/mega_sas
/kernel/drv/mega_sas.conf
/kernel/drv/amd64/mega_sas
/kernel/drv/e1000g.conf
/etc/name_to_major
Andre,
thanks for your help! 9000 mtu is working, after I added suggested files to .backup list. Enabled NFS and from linux machine I have only 27-30 MB/s write operations. mtu on both ends are 9000 e1000 nic in both machines. Will examine why the speed is so slow.
Denis,
No problem and thanks for trying EON. How are you measuring? How much do you measure using CIFS or Samba whichever you are using?
My other guess is you are using the mega_sas driver from Osol 2009 06 with EON 0.59.1 Opensolaris B_114.
If you can use the mega_sas driver from opensolaris 114. I am not saying there is an incompatibility for sure. Another way would be to boot Osol 2009 and see if the transfer numbers match or ?
Please let me know if you get to try it.
Andre, my mesurements are calculated like this:
1. mount -t nfs eon:/tank/test /mnt/test -o rsize=8192,wsize=8192 (nfs runs in tcp)
2. dd if=/dev/random of=/mnt/test/test.img bs=1024k (with various block sizes) count=1000
the result is shown after dd is ended.
I'm not using CIFS or Samba, machines around EON is unix farm. So my goal is to get NFS (maybe iSCSI) storage working.
Results for CIFS:
2,5Gib for 85-87 MB/s
Hi,
Great work as always.
I have been trying to use the image build scripts originally published, however the smf repository is read only.
Just wondering how you got around this issue?
Cheers
DM
ps (to all) - I have eon running on 3 Thecus n5200Pros, but you need to upgrade to 1GB ram.
My goal is to have publish a linux -> solaris upgrade process, that only requires a ram upgrade (currently I have to remove the flash module and partition & format in another machine). You can also run from a usb flash boot, but you need to remove the internal flash module. The preferred option is to install a native module on the thecus through the original thecus web gui and update grub to load the solaris as wan boot or form a usb flash, then load onto the internal flash.
This process could also be used as the upgrade process too, perhaps..
DM,
That is magnificent news! I'm sure alot of people would love to see your write up of how to achieve running eon on Thecus n5200pro. With your permission I'd love to reproduce the write up here when it's complete.
You question about the smf repositiory being read only, do you mean changing it while running on eon or during build?
On Thecus n5200 pro:
-Are you running 32 or 64-bit eon?
-How is the performance vs its OEM OS?
Andre, is there a way to install LSI Logic MegaCLI.pkg onto EON ? I want to manage the controller using Solaris 10 megacli application (text-mode).
Denis,
It could be done in a couple of ways.
-use the build kit and inlcude the pkg at build time. requires another working solaris install to do this
-using the pkg cli method and a one time updimg.sh
-convert the .pkg (data stream) to file system format (pkgtrans megacli.pkg /tmp all). copy the bits and updimg.sh
Andre, thanks for the help, I already tried to unpack the package and updated the image :) One thing is a must for this project -- rsync, to replicate the storage.
I dropped mega_sas out of my box, just plugged 5x750 SATA2 drives and created raidz2 array. Exported array over nfs and now I got 65-80MB/s throughput.
All,
Added the realtek (rge) drivers for download in case anyone else needs it. I will try to add it to the next release.
http://cloud.github.com/downloads/eonstorage/eon/SUNWrge-114.cpio
Hi Andre,
I've followed all your instructions when adding drivers. I have a Realtek GbE, 8169. I can load it manually using add_drv but at reboot it won't load. I have added
/kernel/drv/rge
/etc/name_to_major
to
/mnt/eon0/.backup
before doing in updimg.sh. The entry for rge 61 on /etc/name_to_major was automatic as soon as I did add_drv command. I still don't have it loaded at reboot. I'm pretty sure I wasn't missing anything, but if I have I'd appreciate it if you can see it.
Glenn,
You also need to add (covers 32-bit)
/kernel/drv/rge.conf
and if you're running the 64-bit version you will also need to add
/kernel/drv/amd64/rge
followed by and updimg.sh. That should do it.
Thanks for the reply Andre. rge.conf doesn't exist on the archive you had available at github. Should I be making that file myself? And what would be the contents? Sorry, I'm not really familiar that well with Solaris yet.
Glenn,
You are correct, it seems there is no rge.conf. Are you using the 32 or 64 bit version of EON? If you are using 32-bit, the steps you've listed should've worked. For retracing. Note the files should be located as listed in .backup
add to .backup
/kernel/drv/rge
/kernel/drv/amd64/rge (for 64-bit)
/etc/name_to_major (rge inc number added)
run updimg.sh
Andre,
I am using 32bit. I've retraced and everything is located as it should be in .backup. All files are preserved when I run updimg.sh but at reboot, the driver is still not loaded. It seems that it doesn't know where to attach itself. I have to manually execute
update_drv -i pci10ec,8169 rge
for it to find the right device to attach to. It works after that.
I have tried using your original build kit with the driver loaded, but I'm not happy with the customization since I'm quite blind in what I'm doing. Not really familiar with all the programming stuffs. Also, the ISO produced is upwards to 200MBs when your distro is only 50MB.
I might just wait for your next update, since you said it'll include rge driver on it. For now, update_drv command will suffice to initialize it at boot using your .exec file.
Glenn,
I rolled a 32-bit cifs image (snv_114) with the rge driver. If you could kindly test and report back when you have a chance.
http://www.badongo.com/file/15476882
You can either rename it to x86.eon or you can add/modify the grub entry /boot/grub/menu.1st to test boot it.
Where can I download a snv_114 distribution for extracting drivers?
Hi Bradley,
Unfortunately, once the sxce download increments now at snv_115, there is nowhere I know off to download a copy. I keep a copy of the version EON has a release against so I can try to pull the drivers for of snv_114 if you have an idea which drivers you are after.
Andre,
fFinally found time to try 0.59.1 64b CIFS on my SS4200E.
After reading into on how the configuration works I was able to boot and use the SS4200E from a USB stick.
I saw somewhere mentioned that a 256MB stick is big enough but updimg failed the second time running, leaving a unbootable stick behind.
I didnt see that effect on a larger stick.
Tried Jumboframes for a moment but performance is less than with standard sized frames.
Also I didnt experience any SMBD/CIFS disconnects like 2009.06 (showstopper release).
Very good work ! Thanks.
Andre,
Thanks for the image. I'm trying to download it now.
Bradley,
I know that SXCE is on snv_115 now. But I tried editing the link on the address bar and replacing the part where it says snv_115 and put snv_114 on it and was able to get a copy of that DVD version. I tried it also for a snv_113 and it worked.
Glenn,
Thanks! Good info to know editing the link can get the previous snv DVD image. I assume this would work for 110 also.
Note the 113, 114 in the links!
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=Sol-Express_b114-FULL-x86-SP-G-B@CDS-CDS_SMI
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=Sol-Express_b113-FULL-x86-SP-G-B@CDS-CDS_SMI
Guido,
The 256Mb quote was for the initial 32-bit release. For the 64-bit image (approx 83Mb CIFS, 96Mb Samba), updimg.sh failing the second time makes sense because each update is stored on the key. You are free to archive old updates anywhere on the storage. The first one is rolled to x86.eon.oem in case you wish to go back to the default and start fresh.
3x83Mb ~ 249Mb
3x96Mb ~ 288Mb
You can use any size USB key. The low side was given as a minimum.
Just put together a D945GCLF2 (dual core 1.6ghz atom) with 2GB memory, and a Supermicro 8-port SATA card for my home-grown RAID. Could have done with a "getting started with EON" page for sure, since I had to go looking for the root login, what to do once started, how to add the rge device drivers, and how to add zfs webmin pages. They seem to be all over the place :) Maybe EON is big enough now for you to make a real landing-page...
With 2GB, I don't think I need to be as lean as EON is by default, so I will learn how to roll my own with some more niceties.
Great job btw! Thanks.
Hi Andre,
I'm still working on getting the image you sent me to work. Looks like the CF card I had is starting to fail or it could be the IDE adapter that I got that's failing, not sure, but it's giving me error. I was able to boot it once and it did recognize my GigE NIC, so that's good. Anyway, do you have a new copy of your build script? Are you using the original one for your releases? When I tried it, it gave me a 200MB iso image. Just not sure if you had other changes on your script. Thanks.
Glenn :)
Glenn,
It's the same script except for the dtrace stuff i've recently added SUNWdtrc, SUNWdtrp. Based on your description, it sounds like the trimpkg.sh and/or stripbnl.sh is not running or cleaning up.
Andre,
Your image worked great. Thanks! I am up and running. Time to start working on getting Time Machine working with a ZFS Volume on my Macbook Pro. :)
Thanks for all your help and keep doing great work!
Hit a roadblock. iscsiadm is missing from the distro. In which package is iscsiadm being taken out of? iscsiadm is needed to add a discovery address for the initiator to find the target. At least that's what's according to the guide I was following. Any ideas?
GleNN,
Only the target initiator is currently in. I guess you are using it as a client initiator as well. I will take a look at the client initiator packages.
hi Andre
i insterest in eon long time
and
i want to try compiling a system like eon
but failed
Do u have any document of you compiling eon
I would like to learn more detail
my mail
alex.lbb@gmail.com
Hi Andre
Quick question on licensing. The current credit cruch has provided me the "opportunity" to try starting up in business. In looking for a value proposition I can offer local businesses the idea of an OSOL/NAS seems appealing and a differentiator from the "off the shelf" market. I have been working with standard OpenSolaris so far but really like the idea of EON. I note your files are "all rights reserved" and completely respect your right to have your work used how you see fit, but for avoidance of doubt on my part, is it your intention that EON based images be reserved to home/hobby/own business use or did you have something else in mind?
Kind regards and congrats on the project.
Chris
I have created a project over at sourceforge specifically for off the shelf appliances such as those from www.thecus.com.
A lot of inspiration came from Andre's great work, and also some inspiration from Jim Conners and the Pulsar project too.
Currently, there are 2 target platforms, a Dell SC440 (because I have one sitting next to me as a dev box), and more importantly, the Thecus n5200pro.
I also have a Thecus n7700, but there is currently no solaris driver for the Marvell 88se6340 chipset (I have spoken to the local Sun guys about this, and hopefully some peer pressure, and some favours will result in a driver being written, otherwise, we will get someone to write one ourselves)
You can download the build stuff form https://sourceforge.net/project/showfiles.php?group_id=264827
The build server is snv_b114, but have also tested with build targets of b114, b115 and b116.
Some caveats exist, so treat it as an alpha release at this stage.
Keep up the great work Andre & others!
ps - slowly re-inventing the wheel a little, but all roads do lead to Rome apparently!
Darren
Alex,
Unfortunately, I don't have compilation notes. It would take a good effort to document it.
Chris,
Can you please clarify what you're asking?
Darren:
I initially thought about picking up a Thecus, and working osol onto it, but in the end, I built my own. I am looking at EON, but it is a little too small (86M is very impressive! - but I have 4G of flash space). So I am also re-inventing the wheel. EON is a great starting point, but also add the ZFS admin pages, one of the package systems etc.. such luxuries as top and less even.
If you want help, I am interested. Send me a mail, I think I opened my profile.
Hi Andre
Nothing complicated. Specifically:
My understanding is that I cannot redistribute EON based OS images due to your "all rights reserved" copyright. (For example /usr/bin/install.sh includes this and is part of EON.)
Assuming my interpretation is right, have you or would consider licensing for redistribution for:
- A credit and a link
- A donation or one off fee
- A per copy license fee
- A postcard, a charitable donation, something from your Amazon wish list, anything else (I've seen all sorts of surprising EULA's over the years).
Kind regards
Chris
Lundman, all,
I posted a thread at distro discuss, to try and understand use and more. Feel free to contribute thoughts, wants and ideas.
http://www.opensolaris.org/jive/thread.jspa?threadID=106680
Chris,
Feel free to ping me at eonstore@gmail.com where we can discuss this further.
Hi,
I really like your effort. I decided to build my storage on opensolaris, because of iscsi COMSTAR. Are you heading into this direction or you want to stay on CIFS only?
Where can I find the current build kit. I tried the cloud.github link listed in an earlier post, but I get a permission denied error.
Thanks,
-Rob
Vorcigernix,
EON currently supports iscsi targets. Depending on the amount of people that request the feature it will be tested. The COMSTAR bits are fairly large and would add to boot time and more important use more memory.
GleNN,
Also, requested the iscsi initiator. Would you mind linking the tutorial you are using and share why you would like the iscsi initiator added?
Rob,
I will look into the permission denied error.
Please feel free to post questions, suggestions or more over at opensolaris forums regarding eon.
http://www.opensolaris.org/jive/thread.jspa?threadID=106680
Thanks
Andre,
http://probably.co.uk/howto-set-up-iscsi-targets-on-solaris.html
Here's the tutorial. There's a section there that calls for iscsiadm to setup discovery of the target. So far I can set up everything up to that point and I can't find the target with my Macbook using globalSAN iSCSI initiator.
Andre,
I was also wondering if you could take a look at getting jumbo frame support for rge driver. I've tried setting mtu manually through ifconfig but always giving me error. I can't give you the error right now because my server is currently down. Maybe you could also take a look at the gani driver for Realtek GigE chipsets.
http://homepage2.nifty.com/mrym3/taiyodo/eng/
I've been getting some GEN-ATA error on my Flash-IDE drive. It also started to affect one of my SATA disks with the same error. I booted with the Opensolaris LiveCD and the pool works fine. SATA driver is pci-ide since its an ICH5 chipset and native ahci driver doesn't work for it.
Any update on the build kit availability ?
Thanks,
-Rob
GleNN,
The iSCSI client initiator section is needed only if you plan to use EON to connect to a target initiator (already included).
Are you sure you will use this? It has been added but fairly large.
Looking into COMSTAR but that may have to wait a release.
Hi Andre!
I've got a new mobo for my nas (D945GCLF2). And there are some probs with it. Under some circumstances one core of the cpu gets stressed. top shows that it's taken by the kernel (user processes are near idling), prstat doesn't show info about kernel, but reports idling too and average load the same as top does. hotkernel dtrace script shows this http://pastebin.com/m200dfb2b
full output is http://pastebin.com/m6cd5d7e8
Also powering off doesn't work - it says some error about acpi which I can't quote at this moment.
But both these facts point that there is something wrong with acpi. What could you suggest?
the error on poweroff is:
APIC error interrupt on CPU 0. Status 0 = 0, Status 1 = 40
Hi,
I'm trying to install EON on a CF-IDE adapter, without sucess.
The flash boot but go to the grub prompt asking to the kernel image.
I have tryed to manually specify the image, without sucess too.
Someone have any idea to solve this problem?
Thanks in advance.
scf,
Which bit kernel and release are you using? Try disabling ACPI at boot to test?
http://blogs.sun.com/danasblog/entry/configuring_solaris_acpi_at_boot
DJ Cassiano,
Sounds like it is not installed properly on the CF. It's hard to say what has gone wrong.
Feel free to start a thread on Opensolaris forums where you can post more output.
http://www.opensolaris.org/jive/forum.jspa?forumID=210
Hi Andre,
Thanks for help. acpi-user-options=0x8 seems to help. I only have this output in the log http://pastebin.com/m3dd3fe3a
are the lines at the end harmful?
Hi all,
I'm having some trouble working with EON - I ran the setup as described in a previous post (http://eonstorage.blogspot.com/2008/11/eon-storage-embeddable-onopensolaris.html) to the letter, and even though I specified an IP address, it still looked to DHCP and even though I set the hostname, it still gets reset to "eon". What could I be doing wrong?
Fantastic work!
I've got two questions:
1. Are the si3124 drivers installed?
Because osol2009.06 finds the drives attached to my si3132 controller, but eon doesn't (and i don't find it in /etc/name_to_major).
2. I got a little problem with the setup script: If I enter an address in the 192.168.0.X range as static ip I get an "invalid ip octet: 0" error.
Bye^^
Matteo,
The si3124 is there and should work. I'll double check on s13132. What make, model card is this?
You are correct on the setup and 192.168.0.x net. I will file as a bug. As a workaround you will have to use a non x.x.0.x net or comment the validate_octet check.
Tnx for your help.
The controller is a silicon image 3132 (1 internal sata + 1 external sata), on the abit ab9 pro (in pure ide mode). Today I've double checked: the controller works out of the box with any other solaris distro I've tested (opensolaris 2009.6, the preview releases, and pulsar).
If I've to test something specific let me know. Bye^^
Matteo,
It's my mistake there the sil3124 drivers were not a part of the last release. As a workaround you can add them from the matching opensolaris snv_114 release or wait a few days when 119 will be released.
Matteo,
You can use these drivers in combination with adding your own drivers if you really need it now.
http://cloud.github.com/downloads/eonstorage/eon/sil3124-snv_104.cpio
http://eonstorage.blogspot.com/2009/02/adding-your-own-drivers-to-eon.html
Tnx for your help.
I've added the drivers as per this guide:
http://eonstorage.blogspot.com/2009/02/another-way-to-add-drivers-to-eon.html
Added si3124 in /kernel/drv and in /kernel/drv/amd64/, added a line to /etc/name_to_major, added these files to /mnt/eon0/.backup and ran updimg.sh
The changes survived reboot, the files are there, name_to_major is modified, and if I do add_drv si3124 i got a message saying that the driver is already present but with modinfo is not listed.
I've tried with both your cpio archive and extracting the SUNW3124 package from sxe_114 dvd.
I'll try to gather some logs. Bye^^
A couple of logs:
http://pastebin.com/d74dbf2f
http://pastebin.com/m5266078a
Bye^^
Hi Andre!
I have another problem. Sometimes my box crashes (outputs something to console, reboots and I need to press reset to revive the box). It happens like once in day or two. And I noticed the console output only once because it disappears fast. Can I enable some debug or at least redirect logs to hdd or flash?
scf,
There is no mdb, Can you see if you can capture any part of the message?
Another thing you could do is
zfs create -V 1Gb pool/dump
and then use dumpadm to assign this zvol as your crashdump location.
Matteo,
Only the 2nd link contain modinfo output. I'm not sure what I'm supposed to be looking for there. If it's no 3124 loaded that is correct. It is however possible to add it.
Andre,
I have mdb installed using IPS. How can it help me?
scf,
Hard to say as we have no clue what we are chasing, so a crashdump. Is the screen completely blank with no messages at all?
Andre,
There was a lot of output. Then last lines of it, I think, was message about reboot. And screen went blank. The box has now a 1.5 days uptime, will try to catch it...
Found the problem: the driver doesn't attach. If I force it manually with add_drv -i pci1095,3132 si3124 it works. Is there a way to make this "link" between the loading of the driver and the identify_name permanent? I'm very new to solaris... Tnx a gain.
Matteo,
After you added the driver manually with add_drv /etc/driver_aliases contains parameters you specified to add_drv. So you only need to add driver_aliases to .backup and do updimg.sh. This will put new file into boot image and your device should work automatically after reboot.
Thanks scf,
fileserver up and running :)
Hi Eon,
Can you please possible to include the mega_sas driver into future release?
The snv_130 is out. The Current EON version of 0.59.9 is based on snv_129. Where to download mega_sas of the snv_129?
Thanks,
Alan
Hi Alan,
I will try.
You can get SXCE releases while they last by changing the bxxx number in the URL
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=Sol-Express_b129-SEG-x86-SP-G-B@CDS-CDS_SMI
Andre, I can see that since 59.1 you've had the Marvell 88sx drivers, Have these changed in different SNV's, and does 59.9/60.0 have the latest drivers?
I've just started using EOS with a AOC-SAT2-MV8 card, and I'm having hotplug problems with channel 0 and 1, they lock the console. the other 6 sata ports work fine and detect the unplug/plug events, and I understand there have been fixes for the 88SX driver.
Morpheus256,
The driver used in the EON release would match the 88SX driver available in the SNV release. So for example, if you used 0.59.1 based on snv_114 it would use the 88sx driver available in SXCE snv_114.
Do you know what release the fix is in?
Hi,
Thanks for making is blog site devoted to zfs solaris based storage! It really helpful to have all these useful links in one place!
I have a beginner question.. what is the differnce between running full solaris install and running an Eon install besides the benefit of running the OS on non volital media. I am wondering what is best?
Hi Matthew,
Well there are numerous differences. To highlight a few:
-EON installs, boots and is fully configured in minutes. This process would take hours for a beginner with a full install.
-A great deal of the storage and services are pre-configured to best practices. Again something that would take time for someone new to research and configure through trial and error.
-EON makes it easy to cut straight to storing data with enterprise grade features. A full install, you are responsible for maintaining and restoring (in a failure scenario) the OS. Restoring or re-installing would take a good deal of time.
What is best, only you can truly determine. You have to evaluate your requirements and see which aligns more with your vision and comfort.
Thanks for creating this - I've just got it running well on some old IBM hardware (x235 and x245 servers) with SCSI drives, and now I'm just waiting for a couple of supermicro sata2 adapters to arrive to complete my NAS
You've done an excellent job, and I certainly appreciate all the work that's gone into this. Even for a fairly new Solaris user, this was a pretty simple install.
Dak.
Post a Comment