my filers are always up, but i suppose your options are either
a smaller second pool (ex a mirror) for critical data without spin down
or a job that disables spindown on use time.
Or maby you can chante the timeout on the client?
I recently built up a server using OpenIndiana and Napp-It, and I'm seeing some weird behavior with the low cap alert.
I have a 40GB SSD drive with the root pool on the first 30GB, and the rest will be sliced up for ZILs.
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
rpool 31.2G 14.8G 16.4G 47% 1.00x ONLINE -
zpool0 65T 4.53T 60.5T 6% 1.00x ONLINE -
Pool capacity from zfs list
NAME USED AVAIL MOUNTPOINT %
rpool 27.5G 3.29G /rpool 11%!
zpool0 3.75T 49.2T /zpool0 93%
Why, when I have over 16GB free on my rpool do I see errors saying I'm down to <15%?
If you open the file and go to line 1221 in that file, you will find nearly the same code (only difference is that in the original file, the nfs-share-name is always the same)
It should be easy to replace the old code with the new one.
Keep the original file so you can go back in case of syntax errors.
On next update, the file will be replaced, so no problem.
what is the easiest way to test the Email Alert Feature in napp-it? I have to servers running napp-it. On one it is possible to just click "run now" in the auto tab, where the alert job is registered.
On the second system this doesnt work. How is is possible to test, if it is really working?
Sorry for the long post... but honestly, I am kind of desperate by now, and hope anyone can help me.
It's now 4 months I am fiddling and tuning on my Sol 11 based home NAS enhanced with Napp-it, to no avail. I seem to be unable to get it to a stable and reliable state, although I followed lots of recommendations and tips in this forum and on the napp-it website.
The problem with the ipmiview app is the "discovery" function never finds the host. No idea why and a straight up browser connect works fine. Refreshing my memory, not only does the 'discover' function not find the host, if I give the explicit IP, I get some error about 'the device is offline, connect anyway?'. If I say yes, I get the a progress bar for a bit, then a fail.
Approaching my wit's end and haven't found the answer here or anywhere else I've googled.
First of all, pertinent hardware:
Intel S1200kp motherboard, latest firmware
8 GB Kingston unbuffered ECC RAM
LSI SAS9212-4i4e HBA, latest IT firmware
1 Mushkin 120GB SSD
5 Seagate ST2000DM001 SATA drives
I'm installing OpenIndiana oi_151a from a USB stick, prepared using OpenSolaris Live USB Creator (I've tried this twice so far with the following results). According to the OI Wiki, the install media should detect that I have >1GB RAM and give me x64 installation options. However, GRUB presents only x86 (32-bit) options, and my >2TB hard disks are not dealt with, as only the 32-bit OS is installed. Gparted doesn't see them either, of course.
I'm pretty unfamiliar with Solaris, so I'm not sure what I can troubleshoot or how I can correct this. I can't believe I'm the only one who has experienced this, but I can't find any clues online.
What should I try next? What additional information should I post here? Any advice?
Many thanks, OI gurus!
are you sure x86 is refering to 32 bit, is there a 32bit version if OI 151? I though it is 64 bit regardless and x86 refers to an intel-type cpu vs spark.
on my system (solaris 11) I have
SunOS name... 5.11 11.0 i86pc i386 i86pc Solaris
32-bitTo tell which kernel you are running:
# isainfo -b
Try Solaris11 or OpenSolaris - do they only see 1GB or is the issue specific to OpenIndiana?
No, the installer will install either depending on how much memory it detects. But despite the 8GB I have, it's only installing x86 (32 bit).
After I changed network interface napp-it stopped working, it wont load. I have set it to the same IP as old interface and removed the old interfcae from the PC. I updated napp-it but still, wont load.
Great minds think alike, although I was going to try Ubuntu first. But Solaris 11 installs properly. All disks are recognized (of course, since Sol11 is 64-bit only). Same USB stick and installation method as with OI.
Problem with the Illumos kernel, do you think? Or something else?
As far as i know, the boot process is currently always 32 bit so x86 do not refer to 32 or 64 bit.
This will change in future to support large boot disks
Maybee its a problem with USB booting (have not tried ever)
Can you try the default ISO and boot from a DVD drive?
1) Easy to maintain configure (web based)
2) Easy to monitor (possibly by sending email about failure)
3) Support thoses features: Windows Active directory ACL (Permissions), SSD caching, iSCSI, NFS
4) Long term support (no out of support product)
Does napp-it support windows domain integration with the free version?
i meant a sata DOM. they work great for OS storage. get two and mirror the root pool.