sureguy

http://www.amazon.ca/Kingston-Memory-Card-Reader-FCR-HS3/dp/B005ES0YYA That's what I'm using, I ordered a second for further testing, but the one I bought works properly, and was authenticated via the automated process unRAID is now using.

Thanks a lot Dan, much appreciated! Will look into it shortly. Off to search for a microsd card.... I just used the same card reader with a generic microsd (32GB was all I had on hand). 20 minutes in, no more reset messages, whereas I was getting them about 40 seconds after booting, and then every 30 or so seconds. Running esxi 6, passing through the usb device, USB connected to a usb 2.0 port (wire from mobo header).

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!

Thanks a lot Dan, much appreciated! Will look into it shortly. Off to search for a microsd card....

Dave, I haven't seen errors in the last week. 1. Boot ESXI from USB 2. I use the USB header on the MB 3. Reader Kingston FCR HS3 4. vmdk boot 5. 6.0 final Cannot say when errors were cleared as I did not really followed it. Dan USB Header (which would be pins on the motherboard, perhaps with a cable attached going to ports on a case), or USB Slot, which would be a USB port on the motherboard or USB. Also what speed was the header/port (usb2/3). I have one of these, or a very similar model (looks the same). So I can test it. X9SCM has USB2 only. Sorry to bother you again (I'm remote to where the install is so I want to make sure I have everything I need). Do you have a USB device plugged into the card reader, or something like an SD/MicroSD card? Thanks for getting back to me so promptly.

Dave, I haven't seen errors in the last week. 1. Boot ESXI from USB 2. I use the USB header on the MB 3. Reader Kingston FCR HS3 4. vmdk boot 5. 6.0 final Cannot say when errors were cleared as I did not really followed it. Dan USB Header (which would be pins on the motherboard, perhaps with a cable attached going to ports on a case), or USB Slot, which would be a USB port on the motherboard or USB. Also what speed was the header/port (usb2/3). I have one of these, or a very similar model (looks the same). So I can test it.

Plop and vmdk both show this issue on esxi 6 on my mobo, which is an asrock v77 extreme 4. I've tried an atp nano and Kingston patriot flash drive under both scenarios.

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

Telnet into the server, browse to /mnt/user run mc and delete the share from there

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

You'll need an x64 version of it.

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.

As a Canadian it's interesting to see Canada at 9%, even tough the population is ~1/10th the population of the United States.

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.

When I've formatted disks, the disk says ~90MB have been written if I recall correctly.

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