TheBaldFox

Agreed. Anyway, I'm going to make a backup of the thumbdrive so I'll have it and just hope nothing else strange happens. Thanks for the help.

Well, I'm too impatient and decided to reboot. For some reason the machine decided that it just doesn't want to boot from the USB automatically now... going to have to dig into the bios. However, I could select it manually to boot from usb and when I did everything started up just fine. Attached is the newest diag file. tower-diagnostics-20240328-1531.zip

I have never messed with that plugin that I recall. But if you're telling me that it should be ok to shutdown and restart without screwing everything up then I'll give it a go and post the new diagnostics.

Should I turn that off? If so, how do I do that? Would it be safe to shut the server down and reboot with the drive in a different port?

Was watching a video on Plex when it stopped and could not be restarted. Checked the server and was greeted with a popup message that there is NO FLASH, and to contact tech support. So here I am. Any ideas? The server is still up and running, though I cannot access shares or dockers. Thanks. tower-diagnostics-20240327-1945.zip

Well, when I left the server out of frustration yesterday, the array was not started, would not start, and it basically just sitting there idling. I agree that at some point it must have restarted or it was finally able to complete the reboot that I had initiated yesterday after clearing out some room... maybe? I don't know and have never had a similar issue. I'll look into moving the docker info to the cache drive. What seems to be the issue with the flash drive? Age?

Hello, thanks for getting back with me. So, this is so weird. I woke up this morning to the kids watching a tv show playing from my plex server. I was dumbfounded as had left the server on over night with the boot drive full and unable to operate properly. I just checked things out and at some point during the night the server must have cleared the /tmp folder or something and basically fixed itself. Everything is up and running for the most part as usual, however, I saw that my cache drive was still unassigned. I have no idea why it became unassigned, and I ran a SMART test on it which returned: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 32066 - I added the cache back to the pool and restarted the Array. It seems to be working properly, but I checked the Fix Common Problems app and it found this error: Default docker appdata location is not a cache-only share. I set the appdata default to ONLY cache, and hopefully that will solve the issue, but now it says: "Share appdata set to cache-only, but files / folders exist on the array" and I'm not sure how to go about correcting that issue. Also, my boot device flash is an 8gb Cruzer and it shows that it has 7.48GB free. I've attached a diagnostic in the hopes that you can glean something useful. Thanks for the help. tower-diagnostics-20210930-1441.zip

More info.... While attempting to troubleshoot I found that the "Fix Common Problems" plugin will not complete a scan and I get this on the plugins screen: Warning: file_put_contents(): Only -1 of 5084 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139 Warning: file_put_contents(): Only -1 of 447 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139 Warning: file_put_contents(): Only -1 of 15742 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139 Warning: file_put_contents(): Only -1 of 703 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139 Warning: file_put_contents(): Only -1 of 3172 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139 Warning: file_put_contents(): Only -1 of 72767 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139 Warning: file_put_contents(): Only -1 of 2629 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139 Warning: file_put_contents(): Only -1 of 874 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139 Warning: file_put_contents(): Only -1 of 1565 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.phpon line 139" It does seem that the Boot Device is full, which is wierd because if I recall correctly it had several gigs of space left on it the last time that I checked and I don't know what would have been writing to it. What is the best method to clean the mess off of the root drive while making sure to not delete anything that shouldn't be deleted?

Earlier this morning I was moving a movie from a desktop computer to my Unraid Server with a 4TB storage drive and a 4TB parity. I received an error that the drive was full, which was odd because I had some 90GB of space available on the storage drive. I went into my media share folder, deleted some unwanted movies and tv shows just to make some extra room in case the issue was caused by some unkown Unraid storage data cap on the drive, and attempted to move the movie over again.... Same error. So, I attempt to log into the Unraid WebUI and am greeted by a screen reading three errors, one of which was something along the lines of "Warning session_write_close(): wrtie failed: No space left on device (28)" in one of the /usr folders. I attempted to log in again, but this time I was greeted with the same error. Somehow I was able to successfully log in on my different computer. I attempted to download a diagnostic but the page showed "downloading..." for a full 30 minutes and never pulled a diagnostic report for me to view. While waiting for the diagnostic I noticed that the cache drive was not showing up properly on /Main and figured that the issue may caused by the cache drive having gone out and that the system could not write to the drive and had a serious error. I gave up on the diagnostic and rebooted (probably stupid but I didn't know what else to do) but this time the /Main page no longer showed any Array Devices, Boot Device, or any Array Operations other than Reboot and Shutdown. No shares or Users shown either as the array is obviously not started, and no option to start the array is given. At this point I am at a loss on what to do. I have never had this type of error in the past. I have not changed configurations lately and have been running this server for 4 or 5 years with the same basic setup. Most recent parity check was successful with no errors as well. Any and all info on how to go about troubleshooting would be GREATLY appreciated. Also, I have no reason to think that the storage or parity drive are faulty, and would be willing to rebuild the server from scratch if needed as long as I can be assured that the info on the drives is not affected. Thanks in advance.

I have loved using unraid for the last three years... No issues, great support, fantastic product. Keep up the good work!

With the advent of 6.2 and 6.2.1 I've seen several posts about new shutdown methods of Unraid. I'm a little confused about what all the different methods are at this point. Could we get a quick list of all of the now proper ways for clean shutdown and restart? I haven't found all of this information in the update announcements or posts. I'd never used the "shutdown script" before and I believe that it has been rendered defunct with this update, correct? Also, will the server do a clean shutdown by briefly pressing the power button? Also, what is the best prompt command to type in? Thanks in advance.

I want to thank all of you guys for helping me out and I am sorry for the late resolution post but I've been pretty busy at work. Anyway, I followed the given advice, New Config'd with the old partition disk as the data drive which worked like a charm. I them created a secondary backup of the data onto an external hard drive, which took a loong time thanks to slow usb write speeds, and rebuilt the parity with the new 4TB drive. I have a second 4TB drive on the way and plan to use it as the new data drive. I will be New Config'ing again, installing the new data drive and rebuilding the data to the new drive from the parity. At the moment that gives me three seperate coipies of the data between the Old Parity, the New Parity, and the external hard drive. Thanks again for everyone's help. If anyone has any other sage advice on how to create a better backup copy of a data disk by instaling a drive to the server and having unraid create a copy that would be usable in windows would be helpful for future backups.

Understood. I have my new parity drive running the long smart test which should be done when I get home. After that completes I will attempt the new config with the 1TB parity in the first data slot by its lonesome and see what happens. Would you happen to know, should this be successful, if the file shares and etc be found as they should be by unraid and by devices on my network?

I've been trying to do some more research on this as I find spare time at work. I've been reading the Fixing File Systems tutorial here: https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems It says in very large red letters: Very important!!! Do NOT run these tools on the parity drive. It does NOT have a file system, and running ANY file system repair tool on your parity drive will likely corrupt it! So, my concern here is that if the parity drive does not have a file system how could it then be used in a new config in a data slot? Would Unraid recognize that it does not have a file system and attempt to build it or is it, like was stated, that it is a like-for-like copy of the data disk so long as there was only one disk to parity? Another thought. If I only insert the current data drive and then restart with no parity drives installed will it still show as unmountable and if so is there a way to run something like xfs_repair or other utility to repair it? I think that it is written in XFS, but I'm not sure how to check that info with the logs. I've also read of an Unassigned Devices plugin that may let me view the data on the disk. Would that work to allow me to view/copy the data from the disk into a windows format? I'm sorry to keep asking so many questions, but I just really don't know Unraid/Linux well enough to figure this stuff out.

I think that you are right. The long smart test on the data drive also returned no errors. I will attempt a new config with the old parity drive and I'll check back in when I get a chance to try it out. I just don't understand why it sees the data disk as being unmountable. Thanks.

Tower system log, diagnostics log, and data disk smart report attached. Tower is still running 6.1.9. Smart short test shows no errors, but array sees data disk as unnassigned and unmountable and wants to format it. 4TB parity still shows as invalid. I will run a smart test on it as well after the data disk extended test is completed. The old 1TB parity is not installed at the moment. tower-syslog-20160925-1530.zip tower-diagnostics-20160925-1533.zip tower-smart-20160925-1613_-_data_disk.zip

I can tell you for sure when I get back home this evening. I believe that I upgraded to 6.2 the other day. I also seem to recall originally purchasing Unraid 6 back in July of last year, but don't count on that until I can get home and verify.

I'll still be checking the original data disk first, of course, but in the event that I cannot get it to work I will try this. I was not sure how well this would work since I was under the impression that the parity did not have a file system on it. If I unassign and pull the 4TB parity and the 1TB Data disk from the array, and leave the old 1TB parity installed what would the actual process for doing this new config? I know go to Tools --> New Config, then I would assign the old parity to one of the data disk slots and it will just see the old parity as a data disk without touching the files in any way?

The drives all gave a good Smart checks at original installation as well as the last time that I looked at them. I am fairly certain that I ran a disk check on the original drives when first installed but that was over a year ago. I will double check connections and disk seating this evening. I simply did not have time to do anything else this morning before heading to work.

I'm sitting here at work about to puke because I'm worried that I'm going to lose all of my family pics and videos from my hard drive. Until last night I have been running Unraid 6 on an Intel server tower with one 1TB Parity and one 1TB data drive. I'll apologize right now for the lack of exact details and logs as I cannot access my tower since I am at work and will be here all day but need to get some info now so that I can develop my plan of action. Ok, backstory: I had to restart my tower about a week ago after a power outage and noticed that the parity drive was not found on restart. Both of these drives were previously used drives and I have been planning to uprade the parity drive to a new(er) 4TB WD Red in order to prevent data loss should one of the older drives fail and to allow for expansion of my array size. Since the parity drive was showing unnasigned I went ahead and purchased a virtually new 4TB Red, pulled the old parity, inserted the new parity, restarted and began the parity build process last night before bed and saw that it should take around 12 hours. I went to bed and dreamed of my newly revamped server and the wonderful times that were to come. I wake up this morning at 5am to get ready for work, decide to check in on the parity rebuild process when I notice that it was finished... no, wait, not finished, stopped. The parity showed an orange triangle and (I believe) saying that the parity is invalid. The data disk stated "Device is disabled, contents emulated." I immediately went into freakout mode and stopped the array in the hope that restarting it might do something (yes, I realize now that that was probably the worst thing that I could have done ) and restarted the array. The parity status remained the same but (if I remember correctly) the data disk now shown unassigned. Just not there. I restarted the tower (I realize now that that was dumb too as I did not save the syslog that I now know we need) and the bios does not find the data disk at all and the parity drive is incomplete since, I assume, it did not complete the build process as the data disk may have fried in the middle of it. I've never had any issue with the data disk in the past and had a good health check on it when I started this evolution. At this point I still have the old parity drive which I reinserted into the array just to see if it would be found on reboot, which it was and is currently there as an unassigned drive, which SHOULD have all of the data on it. I've shut down the machine to allow things to cool off, though my drives usually read out at about 30 C, since I'm at work all day anyway. I'm extremely concerned about data loss, obviously, and while most of whats on this data drive are movies and such there are thousands of family pics and videos that I absolutely cannot lose. We had a Samsung laptop HDD go out on us in the past that lost birth pics of one of our daughters and my wife was devastated over that... which was the impetus of my Unraid server build. I have to ensure that I don't lose this data and I am fairly hesitant to do anything more due to this concern without assurance that it can be retrieved with a secondary back up. So, as things stand I will be going home after work and assessing the data drive's connections and trying to figure out why the data drive is not showing up as being installed at all. I'm hoping that maybe jostling the drive bay a bit while moving parity disks around might have loosened something which cause the data drive to stop communicating. If I cannot get it to revive is it possible to pull the 4TB parity and the 1Tb data drive, purchase a new 1Tb drive, reinsert and assign the old parity into its old slot and then rebuild the data drive from the old parity? If so, what is the correct process? If I CAN get the data drive to restart and reassigned to its former slot what do I do next? I have a HDD portable case that I can put the data drive (or perhaps the old parity drive) into and try to copy the data to another location like cd's, but will the files be recognized in such a way that I can do that? This is the first real issue that I've had to deal with since setting up this server, I do not know the program all that well as I haven't had to learn it and I really haven't had the time with work, kids, and life so I'm not particularly adept at troubleshooting this stuff. ANY help and suggestions at this point are greatly appreciated. I am sorry for not saving the syslog, but I didn't know that I would need to until I started reading up on troubleshooting this morning on the rideshare to work. My desktop at home is an older dell optiplex which does not have nearly the storage space to do a hard drive backup to it and the cd drive will not write at all, so I'm just hoping against all odds that at the very minimum the data drive will work in the portable shell so that I can make a copy somewhere else. Please tell me that I can settle down and that this is fixable. Thanks.

I am planning to be able to access it from outside my LAN, if possible. I want to be able to share pics and vids with family offsite. I will look into your suggestions and try to get everything configured and I will check back in. Thanks a lot for the time, guys.

Hello, all. New Unraid user here. I have successfully installed Unraid 6 Server Trial and setup Docker this morning along with OwnCloud, which is the primary reason for my going in Unrad to being with. While I know my way around computers well enough I am not sure how to go about securing my OwnCloud connection. I used the standard OwnCloud installation template and when I click to go to the OwnCloud WebGui I get an HTTPS/ privacy error stating "Your Connection is not Secure. This server could not prove that it is 192.168.1.57; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection." Does anyone have a good way to go about setting up security certificates or whatever it is that I need to do to be able to use OwnCloud going forward? I am at a loss as to what to do. Thanks.