Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Do have this box already?
A lot of energy needed for less CPU power (compared to newer systems), only one pci-e slot and the 1068 is limited to 3G and max 2TB disks
If you can live with that, it should work
I had the same problem suddenly.
The above fix worked for me.
Is napp-it working for you beside that message on login?
The /dev/null is only needed to send unwanted console messages to.
This is probably a crazy question. But, how come there isn't much discussion of using proxmox with napp-it for an all-in-one build?
I know ESXI has quite a bit of information posted for a Napp-it all-in-one build. (Heck I'm currently running one myself). But, I'm just kind of surprised given the growing popularity of Proxmox and the shrinking (very slowly - especially in the actual business world) popularity of ESXI.
Not tied to ESXI and I'm kind of interested in seeing what Proxmox / Xen can offer but, at the same time the complete void of information is making me wonder if I'm missing something. (Like not even posts of how terrible proxmox & napp-it might be together)
Dear Gea,
I hope all is well! I am still on R151014 using ESXi 5.5. Was thinking to update to latest 6.0 of ESXi.
Since there have been so many changes with OmniOS, think I should do a fresh VM of R151020 or should I just update the R151014 following the instructions? I am aware about switching over to OpenSSH before updating per release notes. Just wondering if I am better off just doing a fresh install/VM?
Thanks!
The current hype is lightweight container based virtualisation for Linux guests.
This is something that a type-1 hypervisor like ESXi or Xen does not offer, the offer full OS virtualisation (of any guests). In case of ESXi you addionally have the best pass-through and driver support for guest OSs what makes it a perfect base for a storage VM.
If you use Proxmox (or the Illumos distribution SmartOS), you can use ZFS as native filesystem, so you do not need a storage VM if you only want ZFS. This is different if you want a full featured Storage NAS/SAN appliance. In this case you need pass-through to assigne the disk controller and disks to the storage VM.
There are reports (google "proxmox napp-it") who have done this but I have no experience myself about pass-through on Proxmox.. As an alternative you can use ESXi as a base for full virtualisation of any guests and a guest (can be even be OmniOS with LX container or any Linux) for container based virtualisation on top. You only need around 2GB addiotionally for ESXi with a very low impact on performance. The plus with ESXi is the very easy way to reinstall after a crash and to restore VMs by a simple copy on an NFS share.
root@filer:/aggr1/Folder1/Home/geofile# rm geofile.prc
rm: cannot remove 'geofile.prc': Permission denied
root@filer:/aggr1/Folder1/Home/geofile# chown root:root geofile.prc
root@filer:/aggr1/Folder1/Home/geofile# ls -lh
total 16G
-rwxrwxrwx+ 1 root root 16G Apr 16 07:13 geofile.prc
-rwxrwxrwx+ 1 andrew staff 0 Apr 16 07:28 a.txt
-rwxrwxrwx+ 1 andrew staff 0 Apr 16 07:32 b.txt
root@filer:/aggr1/Folder1/Home/geofile# chmod 777 geofile.prc
root@filer:/aggr1/Folder1/Home/geofile# ls -lh
total 16G
-rwxrwxrwx+ 1 root root 16G Apr 16 07:13 geofile.prc
-rwxrwxrwx+ 1 andrew staff 0 Apr 16 07:28 a.txt
-rwxrwxrwx+ 1 andrew staff 0 Apr 16 07:32 b.txt
root@filer:/aggr1/Folder1/Home/geofile# rm geofile.prc
rm: cannot remove 'geofile.prc': Permission denied
root@filer:/aggr1/Folder1/Home/geofile#
root@filer:/aggr1/Folder1/Home/geofile# /usr/bin/ls -v
total 33531322
-rwxrwxrwx+ 1 root root 17150952929 Apr 16 07:13 geofile.prc
0:user:root:read_data/write_data/append_data/read_xattr/write_xattr
/execute/delete_child/read_attributes/write_attributes/delete
/read_acl/write_acl/write_owner/synchronize:file_inherit
/dir_inherit:allow
1:eek:wner@:read_data/write_data/append_data/read_xattr/write_xattr/execute
/read_attributes/write_attributes/read_acl/write_acl/write_owner
/synchronize:allow
2:group@:read_data/write_data/append_data/read_xattr/execute
/read_attributes/read_acl/synchronize:allow
3:everyone@:read_data/write_data/append_data/read_xattr/execute
/read_attributes/read_acl/synchronize:allow
-rwxrwxrwx+ 1 andrew staff 0 Apr 16 07:28 a.txt
0:user:root:read_data/write_data/append_data/read_xattr/write_xattr
/execute/delete_child/read_attributes/write_attributes/delete
/read_acl/write_acl/write_owner/synchronize:inherited:allow
1:everyone@:read_data/write_data/append_data/read_xattr/write_xattr
/execute/delete_child/read_attributes/write_attributes/delete
/read_acl/synchronize:inherited:allow
-rwxrwxrwx+ 1 andrew staff 0 Apr 16 07:32 b.txt
0:user:andrew:read_data/write_data/append_data/read_xattr/write_xattr
/execute/delete_child/read_attributes/write_attributes/delete
/read_acl/write_acl/write_owner/synchronize:inherited:allow
1:user:root:read_data/write_data/append_data/read_xattr/write_xattr
/execute/delete_child/read_attributes/write_attributes/delete
/read_acl/write_acl/write_owner/synchronize:inherited:allow
2:everyone@:read_data/write_data/append_data/read_xattr/write_xattr
/execute/delete_child/read_attributes/write_attributes/delete
/read_acl/synchronize:inherited:allow
root@filer:/aggr1/Folder1/Home/geofile#
root at console can always delete, does not matter the acl/permission setting. This is different to Windows where even admin respects acl settings (but can always modify). The main reasons that hinders root to delete is a readonly filesystem or when the file is busy/opened by an application.
You can use Windows computer management (connect as a user that is member of Solarish SMB group administrators) to check for open files
To remotely manage ACL on Windows you need a Pro (not Home) edition, optionally SMB connect as user root for full permissions.
root@filer:/aggr1/Folder1/Home/geofile# rm geofile.prc
rm: cannot remove 'geofile.prc': Permission denied
pkg unset-publisher omnios
pkg set-publisher -P --set-property signature-policy=require-signatures -g package repository omnios
pkg update
reboot
ok scrub 1490197372 time: 2017.04.23.13.04.16 info:
ok scrub 1490197372 time: 2017.04.23.13.04.16 info: resilver in progress since Sun Apr 23 13:04:10 2017
ok scrub 1490197372 time: 2017.03.24.06.10.35 info:
ok scrub 1490197372 time: 2017.03.24.06.10.35 info: scrub repaired 2.16M in 1d18h with 0 errors on Fri Mar 24 06:10:30 2017
Yea I definitely like that ZFS works out of box without issues on Solaris based OSs, but I'm being more and more tempted by ZoL because of wide hardware support.
Unfortunately even with pool failure, my Napp-it doesn't send a message. The testscript that sends a test message does work though.
I just tested in a VM. Made two pools fail by removing the storage and no message was sent via Pushover.
test1 - -/ 0 - - - 0 [ /] - - - - - 17534799520560085192 FAULTED n.a. clear errors - 'test1': 'test1':
test2 28 1008M/ 0 461K - - 0 [976M /1.1G] 1.00x wait off off - 11282111706698191978 SUSPENDED n.a. clear errors - 'test2': 'test2':
Hi _Gea, Just trying out napp-it on OI with Supermicro server and Seagate AP2584 JBOD's connected to LSI SAS3 HBAs. The drives in the system are WD 4001FYY-01SL3 drives that have "Drive Trip Temperature" set to 40 in the firmware. So after a while I found that 48 of the 168 drives were disabled by fmd. Have you run into this before? It looks like it is a known issue in illumos: https://www.illumos.org/issues/7327 and a patch was suggested but it never was merged. Any suggestions?
Two other issues: 1. I installed the sas2ircu and sas3ircu utils but they don't seem to find the controllers. These are LSI 9300 HBAs. I downloaded sas3ircu from the Broadcom site for this HBA and tried using the sas3ircu_solaris_x86_rel. The program works (shows program usage if I just run the program without any parameters) but not sure why it doesn't find the controllers.
2. Any easy way to reset the admin password from the command line?
Thanks a lot.