yoshi68

but as the USB drive is set to read only, it cannot write to the super.dat file to say that it has performed the clean shutdown. As far as the behavior of the shutdown, I would assume all is good, It successfully stops the array and unmounts the disks, and I shutdown and the computer shuts down without displaying an error. There is no other indication that the USB drive has failed, except UNRAID only boots it as read only, but that might be because it can't change the .dat file to reflect a successful shutdown. Can I copy the contents of the config folder except for the super.dat file? can I modify the super.dat file to change whatever flag it sets to signify bad shutdown, can I create a new super.dat file?

I have had this error before, and I got around it by backing up my config folder, formatting the USB boot drive and reinstalling from scratch before replacing my config folder. This time, I have shutdown correctly (stopped the array, and then powered down) and when it booted back up, I have the Unclean shutdown detected message. I have tried chkdsk g: /f and chkdsk g: /markclean and in ubuntu i have tried fsck /dev/sdb1, and both result in no change to UNRAID starting up with Unclean shutdown detected. So I made a copy of the contents of the USB drive, and reinstalled UNRAID to the usb drive, and copied the config folder back on, and I get the same boot up again. I can't edit any settings in my system while I have this. Is there any other advice on what to do? Can I back up just selected files from the config that will keep passwords, network and disk configurations intact, and remove all of my plug ins? Should I replace my USB for a different drive?

OK, thanks, I'll look again for newer instructions.

Hey guys, I am having trouble install unmenu on 6.1.9. Following from this thread https://lime-technology.com/forum/index.php?topic=27051.0 I downloaded the latest build from https://code.google.com/archive/p/unraid-unmenu/downloads'>https://code.google.com/archive/p/unraid-unmenu/downloads and followed these instructions https://code.google.com/archive/p/unraid-unmenu/ I don't get very far at all, I created the folder /boot/unmenu/, I copied the installer to the folder and when i try and run unmenu_install -i -d /boot/unmenu I get the following error Unable to download release list from http://unraid-unmenu.googlecode.com/svn/trunk/release_list If I run ping -c 5 google.com or ping -c 5 googlecode.com I get the proper results, and I have manually set DNS to either be my router, or googles public DNS and I get the same result. I have also tried the previous few builds of unmenu from the download site.

Hey guys, I am having trouble install unmenu on 6.1.9. Following from this thread https://lime-technology.com/forum/index.php?topic=27051.0 I downloaded the latest build from https://code.google.com/archive/p/unraid-unmenu/downloads'>https://code.google.com/archive/p/unraid-unmenu/downloads and followed these instructions https://code.google.com/archive/p/unraid-unmenu/ I don't get very far at all, I created the folder /boot/unmenu/, I copied the installer to the folder and when i try and run unmenu_install -i -d /boot/unmenu I get the following error Unable to download release list from http://unraid-unmenu.googlecode.com/svn/trunk/release_list If I run ping -c 5 google.com or ping -c 5 googlecode.com I get the proper results, and I have manually set DNS to either be my router, or googles public DNS and I get the same result.

As I am far more familiar with diagnosing Windows environment problems, I took the easy route out this time and copied all of my configurations, made notes on all settings, reinstalled and set all up again. Everything went 100% smoothly as far as that went, and I already have my VM up and running. Thanks for attempting to help with it everyone who did.

The reason why I can't install a VM is just because my boot drive is mounting as read only. It is perfectly fine in another computer (Ubuntu or Windows). The file that cannot be written is in /etc/ so it is just a problem with writing the configurations to allow the VM to be created. I'll look into just a reinstall of the OS I think. just work out the safest way to approach it before I do.

Ill get onto that tonight when I get home from work. I am trying to have my VMs not parity protected. My plan was 4TB parity -4TB data -4TB data -2TB data -2TB data 1TB data Using the Unassigned Devices app, you can still mount the unassigned devices and create user shares on them, but they are not parity protected. I mounted the drive, I added a share on it (that I will use to share info between my VMs and not touch the rest of my shares parity protected shares). Once it was mounted, I could choose that disk as a VM location, but it wouldn't install. I don't think the parity scan has anything to do what problems I am having now, I was just listing out my procedures. I correctly removed a data disk from my parity protected array before doing what I suspect led me to this problem

Hi, I was trying to configure VMs on a non parity protected drive. I asked the other day if there was a way to do this and I was pointed towards the App "Unassigned Devices". I pulled one disk out of my array, and recalculated parity, I added the unassigned disk to the Unassigned Devices list. I created a user share on it called VM, when I hit save, I got an error that the share was deleted. Researching this on the forum, I came across someone saying that I should restart the server after a fresh parity check and this would be solved, It was. Then I tried to create a VM, and I got an error, When I tried to restart the server again, I had an error with "Retry unmounting user share(s)" over and over, I found a thread where people said just to hard reset and check the USB boot drive for errors with chkdsk in Windows. I did that and all has come up OK. but now when I boot to UNRAID, I get this error "Alert [TOWER] - USB drive is not read-write". Now I can't change any settings because all of the configs are on a read only drive. I have attached my diagnostics zip file. tower-diagnostics-20160622-0037.zip

Because the cache drive will copy itself into the array, I just want these drives accessible, but not protected.

Powershell has more capabilities than Command Prompt, I still don't know if it is possible, but I would look into a powershell script over batch file. https://www.reddit.com/r/powershell is where I get some tips for small stuff.

I am newly onto Unraid 6, and I wan to play with VMs. I came across a comment in a forum post that wasn't really related to this that I haven't bee able to find again while looking into one of the problems I ran into. The comment said that I should not have my VMs installed onto a drive that is parity protected, I understand why, but I can't work out how to configure that. I have a 1TB drive that I was planning on using as a dedicated VM drive and fire most of them up one at a time when I want to play with something specific. So my question is, How can I have a drive in my system that is accessible to UNRAID, but not part of the parity protected array that isn't a cache drive. Thanks in advance.

I connected a keyboard and monitor up to the unraid box and I ran preclear from there. The 1TB drive took about 8 hours to complete fully. I could start the array up (with that drive unassigned) and connect to the shares while the preclear took place. Once it finished I was able to assign it to the missing drive in my array and the array has been rebuilding since. I tried to avoid doing anything at all with the server while this has been going (just in case). I will test the other 1TB drive tomorrow and see how it is. Thanks Everyone, I will mark thread as closed

If the temp listed there is the HDD temp, I would suspect it overheated. But I am also relative noob for this kind of stuff. wait for the brilliant people to chip in.

Just an update. I figured while this was all out I would put a different 1TB in its place in case that drive was faulty and was causing the red ball. while the drive boy was out of the tower I thought I would do some maintenance to the system, clean fans and put in the shorter SATA cables I had gotten but not put in yet. All turned to Crap pretty fast, and the computer didn't post, I ended up pulling the whole thing apart and testing parts in another computer I have. Long story short, all good again, I booted back in, I have access to the shares again, and in the mean time I have stopped the array and with a monitor hooked up directly to the unraid box, am preclearing from there. My unraid box is a little ITX system, which is why doing anything in it becomes a real pain in the ass. Thanks for everyones suggestions.