JonathanM

They could, but then they would have a bunch more problems with people getting licenses and then finding out that particular flash drive doesn't like their motherboard, or some such nonsense. Much better to know for sure that unraid will boot successfully before going through the motions of issuing a license. A better idea would be a click through link in the unraid gui that would prepopulate the online purchase form with the correct GUID. It could even have big letters like BUY A LICENSE HERE or something.

Her site. Female computer geek. I know, it's not expected.

What I'm getting from reading the FAQ's is that you are assigned a private address in their network, and NATTED out the common internet address of whatever server farm you connect to. That offers some protection from the internet in general, but does nothing to prevent other machines connected to their service from hacking in to your machine. If it were me I'd ask their tech support if they recommend firewalling the connection at your end as well. It really depends on their setup.

I can't comment on the issue you are having, but I did want to caution you to research whether or not the VPN you are using is firewalled at the host end, because if it's not, you will be opening your server up to attack through the VPN. You will be hacked in a matter of minutes.

Yes

Don't know of a GUI solution, but perhaps this might provide the functionality. http://sourceforge.net/projects/wake-on-lan/files/ May or may not work, I've not tested it, but it looks promising.

Yep, because only the first part was cleared. If you actually were able to force unraid into accepting it as precleared, any stray 1's that happened to be on the later portions that hadn't been cleared would be out of sync with parity. Best case scenario would be a correcting parity check would catch them, worst case would be a drive failure and those 1's would cause the rebuilt drive to have corrupt data at those locations.

This works on v6 quite nicely. http://lime-technology.com/forum/index.php?topic=33692.0

Please do NOT automate it, at least not without the option to persistently disable the automation with a gui checkbox. Since the repair process could be run on a failing drive, I'd rather have the option to attempt a backup before any writes are done. There is a good reason why drives are set to read only when corruption is detected.

Sounds like you may have a third party add-on installed that is interfering with setting up the new disk. Try booting in safe mode and try the operation again.

A drive rebuild can only recreate what was there originally, and expand from there. If you reformat the drive, all data on it will be gone. If you would have added the drive instead of swapping, it would have been set up as XFS since that is your setting for new drives. Do you have enough space on the rest of the array to clear off that new drive? BTW, there is a forum section for the 6 beta stuff, this section is for 5.

That's fine as long as you are the only living thing larger than a couple pounds with access to the room. Those of us with pets / kids / etc can't just leave drives laying around.

A hard drive is meant to be read and written, it's not like you are doing anything out of the ordinary, just doing it all in a short period of time. The only caveat would be that temperatures can get out of hand if you keep the drive active and don't have good cooling. Perhaps a native preclear test should also log temperature changes and give a warning if temps climb too much during the exercise. I'd MUCH prefer to find any issues prior to committing real data to the drive.

If you have screen installed, you simply type screen in your telnet session, and it gives you the overview information, and you hit return or space to get back to a prompt. You then execute the preclear as mentioned, and you can hit ctrl-a then d to return to the normal prompt. If you need to get back to that screen session, just login and type screen -r and it will drop you right back where you were. Another option is to simply start the preclear at the local console if you have a monitor and keyboard attached to your server. One cool thing to note is that screen sessions are attachable from local or telnet sessions, so if you use screen at the local console, you can attach to it later using a telnet session.

-c is number of cycles, -C is used to change the start sector from 63 to 64 or vice-versa on an already precleared drive. Case is important.

No, it's the number of pre-clear cycles you want to run. If not specified, one cycle is run. Otherwise, it can be anywhere from 1 to 20 (Note that a pre-clear cycle takes a LONG time ... especially with very large disks). Wrong. -c is the cycle count.

I use preclear_disk.sh -c 3 -m email@address -M4 /dev/sdX I'm not sure if the switches all need to be before the device to be acted on or not. The M argument tells it how often you want emails. -M 1 = Will send an e-mail message at the end of the final results (default if -m is used, but no other -M option given) -M 2 = Will send an e-mail same as 1 plus at the end of a cycle (if multiple cycles are specified) -M 3 = Will send an e-mail same as 2 plus at the start and end of the pre-read, zeroing, post-read -M 4 = Will send an e-mail same as 3 plus also at intervals of 25% during the long tests

If you have email notifications set up on the machine, you can add -m [email protected] -M 4 to get real time status updates emailed to you while it's happening. Also, unmenu myMain tab will allow you to watch the progress.

Yeah, just edit the file manually and don't ever touch anything in the configuration side of the web interface or hit save and it works fine. I use phpvirtualbox to do all my management anyway.

That's what I do these days. I just use SyncBack on a Windows machine to do the backups. Wrote a little script to automatically turn on the backup server; then run Syncback to execute the backup "profile". I suspect it's not too difficult to write a simple Linux script that would execute at a specified time to run a sync between two servers ... but I'm not a "Linux guy" and haven't bothered to do this. It'd be nice if it was a built-in feature in UnRAID ... might even sell a few extra systems to those who'd like the convenience of an automated backup to a 2nd UnRAID server +1 That's what i am working on now, I've gotten a few people in my area to invest in unRaid setup and plan on making a larger backup server off-site to backup the unraid systems around my area.. would be nice to have a baked in feature that supports backup to another unraid setup. Making OpenVPN client and server available stock would be icing on top. You could set up the two units on the same gigabit switch for the initial data load, then cart one offsite and have it rsync the changes over vpn. Having that functionality tested and documented by limetech would put unraid into a whole new category of awesome.

The picture is labled "MoreVMs" not "MoveVMs" 1. "XP" {57133605-735f-4d6f-a8ea-392cb1f54ef3} "MinecraftTurnkey" {0486ab8a-b94b-445c-b13e-1484b57f0806} 2. "XP" {57133605-735f-4d6f-a8ea-392cb1f54ef3} "Slack1337" {b5491bcb-42ec-464e-a0da-b0cd5e2b4f6c} "Pardus" {61ee87f5-b044-4e49-89f4-bd4db8983c3e} "Windows Server 2003" {eaad3b3b-539a-4d25-b7cb-fdc592803e5d} "MinecraftTurnkey" {0486ab8a-b94b-445c-b13e-1484b57f0806} 3. Jul 11 18:37:22 AVFiles in.telnetd[12436]: connect from 192.168.117.3 (192.168.117.3) Jul 11 18:37:27 AVFiles login[12437]: ROOT LOGIN on '/dev/pts/0' from 'WORKSTATION1.lan' Jul 11 18:38:49 AVFiles rc.virtualbox[12476]: Saving state of Virtual Machine: XP ... Jul 11 18:39:03 AVFiles kernel: usb 3-10.1: reset low-speed USB device number 6 using xhci_hcd Jul 11 18:39:03 AVFiles kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Jul 11 18:39:03 AVFiles kernel: usb 3-10.1: hub failed to enable device, error -22 Jul 11 18:39:03 AVFiles kernel: usb 3-10.1: reset low-speed USB device number 6 using xhci_hcd Jul 11 18:39:03 AVFiles kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5. Jul 11 18:39:03 AVFiles kernel: usb 3-10.1: hub failed to enable device, error -22 Jul 11 18:39:03 AVFiles kernel: usb 3-10.1: reset low-speed USB device number 6 using xhci_hcd Jul 11 18:39:03 AVFiles kernel: usb 3-10.1: device descriptor read/all, error 2 Jul 11 18:39:04 AVFiles kernel: usb 3-10.1: reset low-speed USB device number 6 using xhci_hcd Jul 11 18:39:04 AVFiles kernel: usb 3-10.1: device descriptor read/all, error 2 Jul 11 18:39:04 AVFiles kernel: usb 3-10.1: USB disconnect, device number 6 Jul 11 18:39:04 AVFiles kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804088b66c0 Jul 11 18:39:04 AVFiles kernel: usb 3-10.4.3: reset low-speed USB device number 10 using xhci_hcd Jul 11 18:39:04 AVFiles kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 9. Jul 11 18:39:04 AVFiles kernel: usb 3-10.4.3: hub failed to enable device, error -22 Jul 11 18:39:04 AVFiles kernel: usb 3-10.4.3: reset low-speed USB device number 10 using xhci_hcd Jul 11 18:39:04 AVFiles kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 9. Jul 11 18:39:04 AVFiles kernel: usb 3-10.4.3: hub failed to enable device, error -22 Jul 11 18:39:05 AVFiles kernel: usb 3-10.4.3: reset low-speed USB device number 10 using xhci_hcd Jul 11 18:39:05 AVFiles kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880408cc8a20 Jul 11 18:39:05 AVFiles kernel: usb 3-10.4.3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Jul 11 18:39:05 AVFiles kernel: input: DACAL Co. CD Manager? as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.4/3-10.4.3/3-10.4.3:1.0/0003:04B4:5A9B.0008/input/input9 Jul 11 18:39:05 AVFiles kernel: hid-generic 0003:04B4:5A9B.0008: input,hidraw2: USB HID v1.00 Device [DACAL Co. CD Manager?] on usb-0000:00:14.0-10.4.3/input0 Jul 11 18:39:05 AVFiles kernel: usb 3-10.1: new low-speed USB device number 12 using xhci_hcd Jul 11 18:39:05 AVFiles kernel: usb 3-10.1: device descriptor read/all, error 2 Jul 11 18:39:05 AVFiles kernel: usb 3-10.2: reset low-speed USB device number 7 using xhci_hcd Jul 11 18:39:05 AVFiles kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Jul 11 18:39:05 AVFiles kernel: usb 3-10.2: hub failed to enable device, error -22 Jul 11 18:39:05 AVFiles kernel: usb 3-10.2: reset low-speed USB device number 7 using xhci_hcd Jul 11 18:39:05 AVFiles kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 6. Jul 11 18:39:05 AVFiles kernel: usb 3-10.2: hub failed to enable device, error -22 Jul 11 18:39:06 AVFiles kernel: usb 3-10.2: reset low-speed USB device number 7 using xhci_hcd Jul 11 18:39:06 AVFiles kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880408cc80c0 Jul 11 18:39:06 AVFiles kernel: usb 3-10.2: ep 0x81 - rounding interval to 128 microframes, ep desc says 160 microframes Jul 11 18:39:06 AVFiles kernel: hid-generic 0003:0B0D:0000.0009: hiddev0,hidraw3: USB HID v1.00 Device [ProjectLab CenturyCD] on usb-0000:00:14.0-10.2/input0 Jul 11 18:39:06 AVFiles kernel: usb 3-10.1: new low-speed USB device number 13 using xhci_hcd Jul 11 18:39:06 AVFiles kernel: usb 3-10.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Jul 11 18:39:06 AVFiles kernel: input: DACAL Co. CD Manager? as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.1/3-10.1:1.0/0003:04B4:5A9B.000A/input/input10 Jul 11 18:39:06 AVFiles kernel: hid-generic 0003:04B4:5A9B.000A: input,hidraw4: USB HID v1.00 Device [DACAL Co. CD Manager?] on usb-0000:00:14.0-10.1/input0 Jul 11 18:39:06 AVFiles kernel: usb 3-10.3: reset low-speed USB device number 8 using xhci_hcd Jul 11 18:39:06 AVFiles kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Jul 11 18:39:06 AVFiles kernel: usb 3-10.3: hub failed to enable device, error -22 Jul 11 18:39:06 AVFiles kernel: usb 3-10.3: reset low-speed USB device number 8 using xhci_hcd Jul 11 18:39:06 AVFiles kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7. Jul 11 18:39:06 AVFiles kernel: usb 3-10.3: hub failed to enable device, error -22 Jul 11 18:39:07 AVFiles kernel: usb 3-10.3: reset low-speed USB device number 8 using xhci_hcd Jul 11 18:39:07 AVFiles kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880408cc8480 Jul 11 18:39:07 AVFiles kernel: usb 3-10.3: ep 0x81 - rounding interval to 128 microframes, ep desc says 160 microframes Jul 11 18:39:07 AVFiles kernel: hid-generic 0003:0B0D:0000.000B: hiddev0,hidraw5: USB HID v1.00 Device [ProjectLab CenturyCD] on usb-0000:00:14.0-10.3/input0 Jul 11 18:39:44 AVFiles rc.virtualbox[12510]: All running Virtual Machines were saved Jul 11 18:39:44 AVFiles rc.virtualbox[12512]: vboxwebsrv service stopped 4. "XP" {57133605-735f-4d6f-a8ea-392cb1f54ef3} "Slack1337" {b5491bcb-42ec-464e-a0da-b0cd5e2b4f6c} "Pardus" {61ee87f5-b044-4e49-89f4-bd4db8983c3e} "Windows Server 2003" {eaad3b3b-539a-4d25-b7cb-fdc592803e5d} "MinecraftTurnkey" {0486ab8a-b94b-445c-b13e-1484b57f0806} Repeat of runningvms command after pressing stop and waiting for command to return. "Slack1337" {b5491bcb-42ec-464e-a0da-b0cd5e2b4f6c} "Pardus" {61ee87f5-b044-4e49-89f4-bd4db8983c3e} "Windows Server 2003" {eaad3b3b-539a-4d25-b7cb-fdc592803e5d} "MinecraftTurnkey" {0486ab8a-b94b-445c-b13e-1484b57f0806}

I didn't have any issues setting it up on a pretty much stock 6b6.

Apache http://lime-technology.com/forum/index.php?topic=33692.0

Please post a screenshot of the WEBUI when you have virtualbox running and some VMs are shown as in session and others aren't but are running.

A list of all running VMs is saved to vms_session.cfg when: Any VM is started Any VM is SAVESTATEd When VirtualBox is stopped via the WEBUI So if I start and stop VM's using phpvirtualbox, the sessionlist is never updated? I ran into an issue yesterday where I tried to stop the array so I could reboot, and I intentionally left some VM's running to see how the plugin would handle it. The VM's that were on the sessionlist savestated automatically, but a VM that I started from phpvirtualbox was still running, and kept the array from stopping. I manually saved it from the command line, and the array finished stopping.