Living Legend

unraid-diagnostics-20171214-1358.zip

I just had a power failure. Unfortunately, I don't have a UPS. Disk 4 is now disabled with errors. Here are the diagnostics. What is my course of action from here? Last time I had to replace a disk things got royally screwed up and I lost my data.

USB devices connected to the server need to be mapped. Also be sure to give your USB a permanent name so that in the event of a server reset, then device name is not tagged with a different number rendering the device mapping invalid. Below is how my device is mapped in my Home Assistant docker:

Also don’t forget, if they’re on different subnets and there is no route between these subnets then they will not be able to send traffic between each other Sent from my iPhone using Tapatalk

Have you tried reconstructing your old configuration before adding the additional access point? Sent from my iPhone using Tapatalk

Are you able to ping unRAID’s IP address from the client devices that want to access it? Sent from my iPhone using Tapatalk

I did so and saw some memory issues. Took all the sticks out, blew some clean air in the slots and all is good

Let me elaborate on full story. I noticed one of my VMs had crashed. I tried to log into the Web UI. No good. I tried the console. No good. I did IPMI reset. unRAID resets and I'm brought back to the Web UI. I start the array. Everything seems super sluggish and I can't figure out why the Web UI isn't reloading. I try to SSH in after a few minutes. I'm getting nothing. Nothing on the Web UI either. This time I go for a full shutdown. Computer isn't shutting down. After a few minutes I plug monitor in to see that all of the dockers are slowly being stopped. Finally, computer shutdown. Now I've reboot and seem to be okay, but still attempting to decipher why the initial hiccup took place.

Woops wrong one! unraid-diagnostics-20171129-2030.zip

My server randomly crashed on me. No idea why. With no other choice, I logged in through IPMI and went to shutdown. 5 mintues later and it's still going. I plugged a monitor into the server. I see it ever so slowly attempting to shut down each and every docker. It's been about 20 minutes and it's still going. What'd I do wrong this time?! unraid-diagnostics-20171127-2222 (1).zip

Understood. I'll see if I can dig up an old log, or wait until the issue happens again. Where on the diagnostics would I find a failed mount?

Posted unraid-diagnostics-20171127-2222.zip

I have a disk that for the last week or so has been periodically losing its ability to be mounted through the plugin. It will still show up on the WEB UI under unassigned devices, but the circle will be gray, not green, and clicking mount will not mount the disk. It will also show "missing" underneath. Any idea what the possible issue could be? I've attached a smart report on the disk. Could it be the single "reallocated sector"? unraid-smart-20171127-2201.zip

Ahh, very useful. I'll have to look into the "still in use" response. I can see this being the case for files being seeded, but I've had plenty of nzb downloads that for some reason seem to remain in limbo.

I'll preface this by stating that I assume there's user error in my actions, and not a fault of unRAID. All of my downloads go to the cache drive which is an SSD. Mover is scheduled to run once a day and takes things from the cache drive to the array. 95% of the time this works as advertised. Occasionally, I'll take a look at my cache and see there are a few lingering files that mover hasn't moved. Not sure why, but I usually think, "okay, well I guess I can just move the files from /mnt/cache/movies to /mnt/user/movies. When I go to do this it says I'll be overwriting what's already there. Odd since it was listed as being on the cache and not on the array, but whatever. I make the move and the files are no longer on the cache. Good, that was my intention. Now I go to my array drives and BAM! Files are not there either. They magically overwrite themselves and dissappear into the unknown abyss of the hidden hard drive black hole. Any idea what's happening here with: 1. Why not all files are moved? 2. Why moving from /mnt/cache to /mnt/user actually deletes the file rather than move?

I've used Xubuntu and Lubuntu before. Could give those a shot. I'll have to check and see what's taxing the CPU from the VM side.

I'm running a VM which is used strictly for very light web browsing, 99% text based. I should have done so one a lighter weight OS, but went with Ubuntu. I currently have 2 cores in use, as well as 2 GB RAM. The VM performs the jobs thrown at it without a hitch. However, I do feel like when the VM is in use, my server fans are really cranked up. I took a look, and the CPU usage for this VM are very high. Would it make more sense to lighten the load and spread it out over a few more cores? Additionally, I'm also willing to hear any suggestions for a super lightweight OS to be used for nothing but light web browsing. Thanks!

I looked in my log file out of curiosity. I guess unRAID saves certain diagnostics without being prompted? I have one from a few hours after the rebuild was completed on my flash drive. Attatched below: unraid-diagnostics-20171024-0200.zip

This. Last resort for sure. But seems like you got things figured out.

The disk boxed in red was the original disk 3 of array. It currently shows no file system.

Two questions. 1. Why would I need to run this on the rebuilt disks? 2. I assume I need to remove the disk from my server and place into a PC running this software?

Soooooo, does that mean I'm SOL? Any hail mary suggestions?

Is there something specific I need to do to get the diagnostics from the rebuild? Does that differ from current diagnostics? unraid-diagnostics-20171024-0253.zip I'm currently running a parity check with writing corrections disabled. I'm naively hoping that maybe the 3rd disk was somehow built incorrectly and that my parity disk is still capable of assisting in the rebuild of disk 3 the way it's supposed to be Forunately I'm mostly media, so it's of minimal consequence. I do however have a few generic data shares, and really have no idea how to even tell what's missing.

Good to hear, glad I could help. I don't know much about XFS repair. Something I may need to look into myself since I just ran into a big problem replacing an XFS disk. It was going bad so I stopped the array and replaced with a new one. When the rebuild was done, the new disk was under 200GB utilized rather than over 2 TB utilized. No idea what went wrong. With that said, and to reiterate, I know nothing about XFS repair. Before running the XFS repair, make a copy of all of those files and place them somewhere that won't be affected (like off the array) if you were to screw something up with your disk.