jkeigs

That worked thanks.

I have a working 5.0 setup and the machine is currently running. Below is the a link that I found to view flash drive permissions. My output is as follows: http://lime-technology.com/forum/index.php?topic=22677.0 ls -al /boot total 4 drwxrwxrwx 9 root root 4096 2013-02-17 09:49 ./ drwxr-xr-x 16 root root 0 2013-10-26 15:31 ../ Other posts all had the boot drive showing the standard unraid folders. My gut is telling me that I didn't setup vbox or simple features correctly (never got it working and had to stop troubleshooting for a few weeks) and that it was reading and writing heavily from the flash drive. Looking at the main page my read counts on flash = 4,294,967,296 and my write counts = 17,314,547,890 which are much higher than I'd seen on this drive with an always on machine for the last ~5 years. Is there anyway to confirm that my flash drive is dead? And if so, recommended steps on how to proceed to minimize the risk of losing data? Thanks

I figured out why I didn't think it was that issue, I was looking at the size and expecting it to be around the 1tb mark. Anyway, I tried the command line fix which didn't work and decided to try 5.0 which did so this issue is solved. Thanks again for the help.

Hmm, I searched hpa on the syslog and found it but it didn't seem that the drive with the error is the drive that was failing. I found the help page for the HPA issue here: http://lime-technology.com/forum/index.php?topic=10866.0 and will follow those steps to remove from impacted drives. I have had gigabyte motherboards and these drives are all pulled from various systems so likely this came from one of the pulls. I still am confused by which drive is impacted but will follow the instructions and post back. Thanks for the quick responses.

I want to upgrade to 5.0 and read the recommendation to get to 4.7 first. I was using 4.4.2 for Bubbaraid and it just worked. I want some 5.0 features and so am now willing to put in the effort to upgrade. I can succesfully boot after removing bubbaraid (complete overwrite of usb with config files copied back into config folder) and am now getting this error: Replacment disk is too small. Initial forum search indicates that it's a HDPARM error but I'm on a supermicro board and a search of the syslog does not indicate that this drive contains HDPARM data. After further searches I can't seem to find the solution and would appreciate some help. Here is my info: Version 4.7 Syslog attached. Thanks in advance for the help. 2013-09-14-1742Syslog.txt

I'm very interested in trying the bubba raid add on but am not sure how to go about installing with my Mac. I only have Mac computers in the house and don't think I'm willing to find a windows install just for this. Can anyone help? Thanks

Hi, I'm trying to create a test usb stick using the basic server download and can't figure out how to run syslinux on OS X. The instructions appear to be for windows only. Can anyone point me in the right direction. Google didn't help on this one. Thanks