sureguy

You need to delete all the files in the share. You can use mc to do this if you're sure that all files should be deleted.

It's good to note that with the addition of the unassigned devices plugin in unRAID 6, you can update unraid 6 final (and some betas) via the menu and then easily mount the VMDK within unraid, and copy bzimage and bzroot to the vmdk from /boot to the mounted VMDK drive. After rebooting you will be on the latest version. IMO there's no need to have someone maintain the VMDK image given how simple this process is now. I guess it would be nice if LT made a vmdk though.

I think this thread should note that some ESXi 5.x and 6.x hosts show USB reset issues with PLOP and USB passthrough on unRAID 6. 2 members have been able to work around this issue by using microsd cards attached to Kingston FCR-HS3 devices,.

I just had success with the same reader (I bought it a couple years ago). Was able to remove a USB thumb drive, and activate this via unRAID's new guid process. This also allowed ESXi 6 to use the media without any reset messages. Thanks again Dan!

Hi Rick, so far so good with the G4? I'm looking to get another mobilelite (already have two G3s) but the G3s are not available anymore. PS: How does Tom know whether a GUID is unique or not? Buy more than one reader and compare? He'd know for sure if he ever got a request with a guid already in what I assume is a database of guids and licences

If you don't have 2TB free on your server, you could always copy 2TB of the data to a USB device temporarily during the conversion

A green check mark and red X would probably work

Since it's happening on the last data drive to be scanned, I suspect it is trying to start a new scan before the current one is finished, that is, timing out on the scan polling interval. As an experiment, try increasing the minimum scan time (eg. /boot/cache_dirs -w -m 7). If that doesn't help then increase it to 8 seconds, then 9, then 10 seconds. If it does appear to be working correctly, then decrease it a second at a time until it doesn't, then change it back to the lowest minimum scan time that does work. Thanks for the help, increasing it to 9 seems to have fixed the issue (I'm going to keep monitoring it). As a side note using -m with a value higher than 10 causes cache_dirs to fail. Low ram shouldn't have any affect on me as I'm running v6.06beta which is a 64-bit OS, and has no low ram. There are ~245000ish files on the array.

For some reason cache_dirs is keeping one of my disks busy. I've got 6 data disks, and cache dirs appears to be keeping Disk 6 busy. inotifywait -mr /mnt/disk6 shows that a few folders keep being rescanned on the disk (every 3-5 seconds), preventing the disk from spinning down. As soon as I stop cache_dirs with -q inotifywait stops updating (the disk is idle) I'm currently running reiserfsck on the drive to ensure it's not a file system problem. Outside of a file system issue, does anyone have any idea as to why this is happening, and what I can do to prevent it? I'm currently invoking cache_dirs via the go script with the recommended command: /boot/cache_dirs -w I have 2gb of RAM, and am running the SSH, and APCUPSD plugins on v6.06beta. Currently using the latest version of cache_dirs

A hidden partition commonly created by gigabyte motherboards to backup the bios. Sent from a mobile device, sorry for any typos.

Because it hasn't happened to them yet. Sent from a mobile device, sorry for any typos.

I would think if you were changing or adding drives it wouldn't be a terrible idea to re-run it.

Thanks for this, currently running it. Also thanks to you and Patilan for not letting your conversation devolve into a petty argument. Sent from a phone, sorry for any typos

Are you referring to UnRAID's boot time? If so, how does it compare to bare metal boot times? Assuming ESXi is already booted up, booting from the VMDK is faster than bare metal boot times. Not having to read the boot image from the USB, instead loading it from a data store, significantly cuts down how much time that takes. It will depend on how fast your usb drive is probably.

If you install to SSD, you can still use whatever is not partitioned and used for ESXi as a datastore. The advantage to using USB is you can back it up more easily as the drive is normally plugged into an external port (don't have to open anything up), plus SSD for booting ESXi is overkill.

BetaQuasi appears to be using ESXi 5.1. Was 4.1 a typo? If not I'd recommend trying 5.1.

A tutorial/HOW-to for screen can be found here: http://www.rackaid.com/resources/linux-screen-tutorial-and-how-to/

When you killed it did you specify any switches? kill -9 pid will usually kill any stubborn hung up processes

I downloaded cache_dirs from the first post in this thread, but when I run cache_dirs -V the version is listed as 1.6.5 - is this just a problem with the script misreporting the version number? *Edit* I just opened the script in an editor, it has notes about 1.6.6 and what was fixed, but the version variable is listed as 1.6.5 in the script.