joelones

Thanks, the pre- and post commands now get executed when the sleep button is pressed. However, I'm experiencing the same issue when executing the command. /usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/s3_sleep -S I notice the switch: -b name execute shell script 'name' before sleep So I assume I need to create a script with "/etc/rc.d/rc.libvirt stop" and pass that on to the s3_sleep command. I'm assuming that's the correct way to go about it? EDIT: Just tried it, it seems to work as well. Thanks for the great work.

So I basically have my Windows VM on, invoke the sleep, VM doesn't gracefully exit (as /etc/rc.d/rc.libvirt stop would normally do if I execute on the command line), then server sleeps. Upon wake, I'm presented with a BSOD on the Windows VM (gpu passthrough) monitor. Screenshot of S3 sleep config screen: syslog.txt

I'm trying to gracefully shutdown the VMs when sleep occurs and added /etc/rc.d/rc.libvirt stop to "Custom commands before sleep" and /etc/rc.d/rc.libvirt start to "Custom commands after wake-up". I'm noticing it's not running "/etc/rc.d/rc.libvirt stop" before sleep. Thoughts?

Must we add a script for proper VM shutdown/resume when S3 sleep occurs? or is that handled by the plugin? I guess the same question when wake occurs.

Thanks for the guide. Very helpful.

Forgive me if this has been answered already, but what happens to the VMs when the S3 Sleep happens and consequently when the machine is awaken via the WOL? Are they sent a shutdown commmand? As upon inspection it would appear that the VMs aren't gracefully shutdown and restarted with sleep/wake. Is that something difficult to implement?

Just a question, I'm assuming this plugin is for bare metal installs? I'd like to pull IPMI data from my supermicro IPMI board (via IP) and react on events, as I'm running unRAID in a virtualizated manner.

RobJ, I precleared the Toshiba three times, here's the output: ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdp = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 35C, Elapsed Time: 67:54:01 ========================================================================1.15 == TOSHIBADT01ACA300 == Disk /dev/sdp has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdp /tmp/smart_finish_sdp ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 171 136 0 ok 35 No SMART attributes are FAILING_NOW 8 sectors were pending re-allocation before the start of the preclear. 8 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, a change of -8 in the number of sectors pending re-allocation. 48 sectors had been re-allocated before the start of the preclear. 48 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. I no longer see the pending, and I assume I should just keep it at this point, instead of going through the hassle of rma'ing it.

Thanks RobJ, I have replaced the Toshiba and in the process of rebuilding. So to clarify, you suggest running the preclear on the Toshiba to clean out the pending sectors? It's still under warranty, I had in mind to RMA it. Is it worth keeping at this point? I was planning on just writing zeros (with the -W switch) and sending it back. Would the zeroing of the drive alone fix the pending sectors? Have yet to RMA a Toshiba drive, do they send you a recertified one back like seagate?

I just upgraded from v5.0.6 -> v6.1 and I'm now noticing SMART warnings for two disks. I'd like some help 1.) Parity drive - ST3000DM001 (reported uncorrect is 1) 1 Raw Read Error Rate 0x000f 105 099 006 Pre-fail Always - 9702136 3 Spin Up Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start Stop Count 0x0032 095 095 020 Old age Always - 5286 5 Reallocated Sector Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek Error Rate 0x000f 047 043 030 Pre-fail Always - 1859744137980 9 Power On Hours 0x0032 073 073 000 Old age Always - 23749 (2y, 259d, 13h) 10 Spin Retry Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power Cycle Count 0x0032 100 100 020 Old age Always - 55 183 Runtime Bad Block 0x0032 099 099 000 Old age Always - 1 184 End-to-End Error 0x0032 100 100 099 Old age Always - 0 187 Reported Uncorrect 0x0032 099 099 000 Old age Always - 1 188 Command Timeout 0x0032 100 100 000 Old age Always - 0 0 0 189 High Fly Writes 0x003a 099 099 000 Old age Always - 1 190 Airflow Temperature Cel 0x0022 069 058 045 Old age Always - 31 (Min/Max 21/35) 191 G-Sense Error Rate 0x0032 100 100 000 Old age Always - 0 192 Power-Off Retract Count 0x0032 100 100 000 Old age Always - 55 193 Load Cycle Count 0x0032 014 014 000 Old age Always - 172046 194 Temperature Celsius 0x0022 031 042 000 Old age Always - 31 (0 15 0 0 0) 197 Current Pending Sector 0x0012 100 100 000 Old age Always - 0 198 Offline Uncorrectable 0x0010 100 100 000 Old age Offline - 0 199 UDMA CRC Error Count 0x003e 200 200 000 Old age Always - 3 240 Head Flying Hours 0x0000 100 253 000 Old age Offline - 5201h+54m+36.322s 241 Total LBAs Written 0x0000 100 253 000 Old age Offline - 37836775592 242 Total LBAs Read 0x0000 100 253 000 Old age Offline - 227760941004 2.) Data drive - TOSHIBA DT01ACA300 ( reallocated sector ct is 48 / current pending sector is 8 ) 1 Raw Read Error Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput Performance 0x0005 139 139 054 Pre-fail Offline - 73 3 Spin Up Time 0x0007 133 133 024 Pre-fail Always - 430 (Average 430) 4 Start Stop Count 0x0012 100 100 000 Old age Always - 2798 5 Reallocated Sector Ct 0x0033 100 100 005 Pre-fail Always - 48 7 Seek Error Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek Time Performance 0x0005 124 124 020 Pre-fail Offline - 33 9 Power On Hours 0x0012 099 099 000 Old age Always - 9679 (1y, 38d, 7h) 10 Spin Retry Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always - 17 192 Power-Off Retract Count 0x0032 098 098 000 Old age Always - 2799 193 Load Cycle Count 0x0012 098 098 000 Old age Always - 2799 194 Temperature Celsius 0x0002 181 181 000 Old age Always - 33 (Min/Max 19/42) 196 Reallocated Event Count 0x0032 100 100 000 Old age Always - 49 197 Current Pending Sector 0x0022 100 100 000 Old age Always - 8 198 Offline Uncorrectable 0x0008 100 100 000 Old age Offline - 0 199 UDMA CRC Error Count 0x000a 200 200 000 Old age Always - 0 Thoughts? Which should I be more concerned about?

For the time being you can manual create the swap, http://lime-technology.com/forum/index.php?topic=39341, preferably on a cache drive EDIT: Doing it this way, you'll have problems stopping the array if the swap file is located on the cache drive, so I guess we'll need an update to this plugin. I'm assuming this plugin unmounts the swap file during array shutdown?

Speaking of which, I'm in the process of testing the UPS and it does not appear to shutdown the unRAID server despite getting the proper events. I detailed the problem here: http://lime-technology.com/forum/index.php?topic=42429.0 Now, I'm curious as to whether it has something to do with the s3_sleep plugin, which I currently have set to disabled? Or is this unrelated? Edit: This could be related to a rc5 bug, please disregard post

Just finished testing. Working well. Thanks for a great plugin & for the help. Now on to setting up the UPS, picked up a CP1500PFCLCD.

Thanks, much appreciated.

Just need some clarification concerning the Excluded Days/Hours dropdown for the sleep plugin. Currently all is unchecked. In essense I'd like to schedule sleep of the server from 3am->3pm, everyday. Not sure what needs to be done to accomplish this. I can wake the server via a crontab wol command from pfsense.

Not sure if this has been asked or not. So forgive is so. I'd like to invoke the sleep functionality (button) via the command line preferably with curl or ssh (public keys), bascially without logging into the GUI. How would I accomplish this? Thanks for the great work.

Great guide, I was able to get this to work, but just want to point out a few things. For me I wanted to pass in two top side chasis ports, which I found to be on bus 007 and on 00:16.2. The IOMMU group was: /sys/kernel/iommu_groups/14/devices/0000:00:16.0 /sys/kernel/iommu_groups/14/devices/0000:00:16.2 When adding the controller in via the xml file, I needed to only add device 00:16.0 as adding both (00:16.2 as well) would cause an error. I assume it was enough to add 16.0. Second, /usr/local/sbin/vfio-bind was not there by default. I just created the script: (hope this is what everyone else here is doing) cat << EOF > /usr/local/sbin/vfio-bind #!/bin/sh modprobe vfio-pci for dev in "\$@"; do vendor=\$(cat /sys/bus/pci/devices/\$dev/vendor) device=\$(cat /sys/bus/pci/devices/\$dev/device) if [ -e /sys/bus/pci/devices/\$dev/driver ]; then echo \$dev > /sys/bus/pci/devices/\$dev/driver/unbind fi echo \$vendor \$device > /sys/bus/pci/drivers/vfio-pci/new_id done EOF chmod +x /usr/local/sbin/vfio-bind And then adding this to the go file? Lastly, I'm assuming this would work with a usb 3.0 controller, no caveats there?

Didn't realize there was an Android UI, will have to try it. Thanks!

I just wanted to report back to the OP (from http://lime-technology.com/forum/index.php?topic=31257.0), and confirm that indeed proxmox 3.1 works with grumpybutfun's unRAID vhd file (from http://lime-technology.com/forum/index.php?topic=30715.0). I guess no reason why it wouldn't as proxmox uses KVM. In any case, I decided to try proxmox because of the overall smaller footprint compared to the opensuse's graphical installation, as well as better suited for a headless server install. As the underlying OS (debian) is installed for you as part of the install, I found the whole install to be relatively painless. Obviously special thanks goes out to user grumpybutfun for creating the unRAID vhd file in the first place. This is a quick & dirty guide and not tremendously thorough and I assumed that the user is able to copy files via scp or winscp and able to use vi or nano. All in all, the proxmox Web UI is not as functional as ESXi's or Virt-Manager for that matter, so some command line editing skills are necessary to change the configuration file. I am also using an AMD cpu so some things may not entirely follow for intel users, I'll try to indicate those differences. Installation: Download the Proxmox VE 3.1 ISO Installer and write it to a USB flash drive, you can google the download link. Because I used Windows, I used SUSE Studio ImageWriter from https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe to write the iso to the usb. Just make sure your USB contains no partitions. I deleted all the partitions on my usb with the Home version of Minitool Partition Wizard, again you can google the link. The installation is very straight forward and consists of selecting your timezone, installation disk (see partitioning below), ip address and setting a root pasword. See here for a complete guide: http://woodel.com/my-linux-how-to/proxmox_vidz/vid1/ Partitioning (Hard Way): After initial installation I did the following: I resized the Logical Volume's that were initially created by the proxmox installer, specially in the PVE volume group. I didn't like how it partitioned my 120GB SSD. So I booted up with GParted (http://gparted.org/download.php) and opted to work in the terminal as GParted is unable to alter Logical Volumes (at least it was in my case with the lastest gparted-live-0.17.0-4-i486.iso. By default, the proxmox installion creates: /dev/pve/root /dev/pve/swap /dev/pve/data In short I did the following from a terminal window while booted from the GParted iso: vgchange -a y (make the LVM disk visible to the kernel) e2fsck -f /dev/pve/root (check the filesystem) resize2fs /dev/pve/root 8G (shrink root to 8G) resize2fs /dev/pve/swap 2G (shrink swap to 2G) e2fsck -f /dev/pve/data (check the filesystem) lvextend -L+40G /dev/pve/data (expand data with an addition 40G of space) resize2fs /dev/pve/data (resize data - where VMs go - occupying the rest of Volume Group) Leaving about 5.50 G in the VG for snapshots. I still haven't messed around with snapshots yet, so I'm not sure if it's too little. Partitioning (Easy Way): If you want to simplify your life and save some time when it comes to partitioning, you can pass arguments to the boot: prompt right before booting and avoid the above. The above example linux ext4 maxroot=10 swapsize=20 configures the partition filesystem to ext4 (ext3 is the default), creates a root partition of 10GB and swapsize of 20GB. Some more options: Install webmin (Optional): Download webmin from http://www.webmin.com/download.html Copy it via scp or winscp and install with the following from a ssh shell logged in as root: dpkg -i webmin_1.670_all.deb If the above complains about missing dependencies, execute the following: apt-get -f install Prior to that you'd probably want to run the following to update your system: apt-get update apt-get upgrade Log in with your root password, as created during the installation process, at (https://IP:10000) to administer your proxmox server. Make sure iommu is activated: Log into a ssh shell as root, if not done so already and do the following: vi /etc/default/grub Change: GRUB_CMDLINE_LINUX_DEFAULT="quiet" To: GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on" I believe for intel it's: intel_iommu=on Then: update-grub echo "options kvm allow_unsafe_assigned_interrupts=1" > /etc/modprobe.d/kvm_iommu_map_guest.conf reboot Install an unRAID VM: Create your initial VM for unRAID at https://IP:8006, of course log in as root. You will find the Create VM button at the top right corner. I'll let you follow the wizard. This is how I configured mine: Copy over grumpybutfun's unRAID vhd file via scp or winscp to: /var/lib/vz/images/100 Here, 100 is a Virtual Machine ID and stands for the first VM created in my case, it may be different for you. I also deleted the .qcow2 file and the line in the conf file representing the disk as it was created by the wizard. I renamed the unRAID vhd file to vm-100-disk-1.raw with the command line, not sure if that's necessary though. Then I modified the configuration in: /etc/pve/qemu-server/100.conf Compare yours with the following: The net0 (NIC mac address), usb0 (unRAID usb), hostpci0 (HBA) and cpu lines may be different in your case. bootdisk: virtio0 cores: 1 cpu: Opteron_G5 hostpci0: 02:00.0 memory: 1024 name: unRAID virtio0: local:100/vm-100-disk-1.raw net0: virtio=56:74:22:0A:65:22,bridge=vmbr0 ostype: l26 sockets: 1 usb0: host=0930:6545 Configure Passthrough: Note: The hostpci0 line (device passthrough) is for my M1015, which can be found via lspci. This is necessary if you are passing in a HBA/RAID card for unRAID to use. The usb0 line is for the unRAID usb (which must have a label of UNRAID and is mandatory to get unRAID booting correctly). The usb address could be found via lsusb. lsusb in my case: lcpci in my case: Note for Intel Users: Change your cpu from Opteron_G5 to the appropriate setting if not running an AMD processor. This can actually be done via the Web UI. Start unRAID: Click on your unRAID VM and hit the Console button on the far right (not shown on the image below), then the Start button (you will need Java installed for the console to work on your system). If everything works out, you should see the following: Disclaimer: I don't know what I'm doing so I'm sure there's something I'm missing. But it works. Licensing: There's a way to get rid of the nag in 3.1, but I digress. What I'm not sure about it is the ongoing support for non-subscription based installations as the enterprise repository requires a license to update from. You can uncomment the line from /etc/apt/sources.list.d/pve-enterprise.list to ensure that apt-get update doesn't fail. All updates will be from the non-subscription repository which are publicly available I assume. Additional Resources: Also. Here is a tutorial series I found on proxmox for noobs like me: http://woodel.com/my-linux-how-to/proxmox_vidz/ Good luck!

It has been a lot more than 4-5 hours patiently waiting.. Not quite sure I understand the need to for this when you can make a .vmdk file yourself and use a program like winimage to inject the new bzimage/bzroot. And besides rc13 uses a different kernel so you will likely need to wait for a new vmtools package. Edit: http://lime-technology.com/forum/index.php?topic=7914.0

I'm still having a problem with the preclear (although, I only see one occurrence of this error so far). I'm not sure what to do anymore as I just got a replacement backplane! unraid 4.7 Norco-4020 supermicro:x8sif The preclear isn't finished bu this is what I see in the log Error: Attached is the syslog. Any suggestions, please? syslog-2012-01-04.txt.zip

So I finally narrowed it down to the first SATA port on the first backplane. Thanks for all the help guys! I pulled out the backplane to take a look and notice that the backplane looked "used" in many respects (scratches, discoloring, etc...). It just didn't look like a new circuit board. Countless wasted hours later, I contacted Norco via telephone, I was told to send an email to their customer service address by some individual who had difficulties with the English language. A fellow got back to me, he wanted pictures, then said I was responsible for buying the replacement and shipping back the defective unit, shipping of which would not be reimbursed. Build quality of the case and customer service are subpar in my book, will not be buying Norco again. Live and learn I guess. Again, thanks for all the suggestions.

Since he says it is in the "writing" of the disk where errors occur, reading from it using "dd" as you described will probably not help. Instead, for a quicker test, simply use the "-W" option to the preclear script to ask it to skip the initial "reading" of the disk. It will then start with the "writing" of zeros. preclear_disk.sh -W /dev/sdX Thanks for this JoeL., this will surely save some time. I just tried the second backplane and no errors. So I guess I can conclude that the first backplane is damaged, come to think of it, I did notice it being loose upon touch. It should of occurred to me to check that first as a root cause. I notice that the backplanes have two thumb screws, should I bother to loosen and inspect it further? Now, having it bought at Newegg.ca, what would be the process? Contact newegg and ask for a RMA (could only imagine the shipping from Canada) or the manufacturer for a replacement backplane? EDIT: Will probably just call norco and ask for a replacement. I'm now worried about the other backplanes. Will need to test each I guess.

thanks for the suggestion, but doesn't there have to be a filesystem on the disk for this? these are new disks.

Hi RobJ, Woke up this morning to the same errors. I need to somehow verify if this is a backplane problem or not. It could be power related too, however, each backplane has 4 sata connectors and two molex connectors and as far as I can tell, the connectors are seated properly. I am however using one molex to sata power connector for this backplane, (btw the PSU is 750W), I will try using two molexes. I have been testing the same backplane and same sata connector, I will try the next backplane connector and then without the backplane at all (seeing how two disks exhibit this problem, I doubt it's related to the disks. Could it be a motherboard problem, I don't think anything needs to be set in the Bios?). Do you know of a way testing this without using preclear, as each time I test, I have to wait until until "Step 2 of 10" before these errors appear in the log??? It makes this process more difficult, waiting 5-10hrs before I see the errors. Thanks again.