sickbro

Transition Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sickbro

  • Rank
    Newbie
  1. [SOLVED] Install on vmware ESXI

    2014/03/08 09:29:15 Install open-vm-tools 9.4.0-1280544-50 successfully 2014/03/08 09:29:15 Start open-vm-tools: start 9.4.0-1280544-50 successfully Can't get it to work - "Failed to run the package service." Log says: "NAS is not a virtual machine..." "vmtoolsd is not running..." It's running on ESXi 5.5 vmx-9. Do I miss something? I think I just figured this out, might be the same for you. My volume is actually volume2 instead of volume1 like most people have by default. If you SSH into the VM and goto /var/packages/open-vm-tools/start-stop-status and edit that file there is a line that says "PROGDIR=/volume1/@appstore/open-vm-tools". change that to "PROGDIR=/volume2/@appstore/open-vm-tools". This fixed mine, hope it works for yours.
  2. Can you shed a little light on this? I just upgraded to gnoboot 5.0 and I can't get my photo station running. I tried creating "http" through the gui, and it said it was reserved. I found it in the user list via SSH, but I'm not sure what it needs access to. Thanks In my case as I mentioned, the usergroup 'http' was not present. So, I create the usergroup 'http' and then give the usergroup 'http' read/write access on the shared folder 'web'. Then start the web station service. After that photo station still not working correctly. Needed to re-install. Biggest problem for me is MariaDB not working. So not upgrading yet to this release. I went back through and reinstalled the PAT, and managed to get photo station working again. Broke some other stuff in the process, but I think i've gotten it all sorted out. Thanks for the help. Big thanks to gnoboot as well. So far this thing is rock solid, and I am finally able to passthrough my SAS controller to get Smart data.
  3. Can you shed a little light on this? I just upgraded to gnoboot 5.0 and I can't get my photo station running. I tried creating "http" through the gui, and it said it was reserved. I found it in the user list via SSH, but I'm not sure what it needs access to. Thanks
  4. So I played around with a grub delay, but not much help since it doesn't initialize the card and spin up the disks until the mptsas driver loads. I also noticed I have another issue with esxi which you probably don't. Because the is is installed on a virtual disk on a SCSI controller, it is reserving 16 ports for that SCSI controller. Which means I don't think I really have enough ports in the synoconfig. I did notice that all my disks except the one virtual boot drive were all 17+ numbered. I think I only have 20 set right now, so I'll play with that some more tomorrow. Still don't think it should effect the drives jumping numbers though. I like the idea of using the UUID, but have to sleep for tonight. Maybe I'll check that out tomorrow.
  5. Just wanted to chime in on this. I'm having similar problems with the drives detecting as different numbers. I'm running this in esxi 5.5 with 4x 3tb drives on xpen 4. raw disk mappings work just fine, but my goal was to pass through an ibm m1015 (LSI9211-IT) to the guest. This way I would get smart data and temp readings. My issue seems to manifest with the power on/off of the drives. Basically if the host is off and I boot it, all the drives spin up during the host boot. If I then start the xpen VM everything works and is detected fine. In this case the disks are already spinning because they spun up with the host. If I then shut down or reboot the xpen VM, I can hear the drives spin down. When I start the VM again, I can hear the drives do a staggered spin up. After that, the drives end up in all sorts of order in the GUI. Sometimes one will be 12, next boot it'll be 20, but they are all always detected. Reboot the host, and I get another good boot with drives detected correctly. What I think is happening is that the drives aren't really ready when the is is going through the drive detection. If I go into the GUI I can watch as the drives detect well after the GUI has loaded. The first disk it detects is always initialized with a crashed raid warning, and the other 3 are not initialized. My thought was to try adding a boot delay to grub to try and give it time to spin up the drives before it starts the actual boot process. Any thoughts on the likelyhood that may do something? Thanks