Mundvl

No luck. Had to just hit the reset button. But luckily /mnt/user is back and everything is working, including the web interface, array is doing a parity check due to the unclean shutdown. Noticed a few other users having the same issue as me in some other recent threads - will look at implementing some of the advice there when I get time.

Thanks, will give that a try later.

Hi I'm relatively new to unRAID, having only been using it for a couple of months. I went to access the web interface this morning finding it wouldn't connect (tried typing in the IP in addition to the hostname, also SSH would not connect). But my docker containers still seemed to be working fine sonarr/radarr/etc and I could watch stuff on Plex. But, have noticed now a couple of hours later that I can't access any of my docker apps, plex library or shares on the network, only Krusader still works for some reason and I noticed something looked odd, I had set up my server following spaceinvaderone's guides and noticed that 1_unraid_shares and also .dockerenv were greyed out with a file icon instead of a folder icon. When I tried /mnt/user, had the same issue. My server is setup with a 1 parity drive and 3 in the array. 1 SSD for caching downloads (cach_media) and another SSD with appdata and the rest of the system files on it (cache_system). I'm wondering if the system SSD has become corrupted or failed? I'm looking for some advice on how to recover from this. I do have a backup of the Unraid USB install drive, but never got round to backing up my appdata and other folders on the system. I assume I'll have to setup all my dockers and things from scratch, but I'm hoping my array will be okay, can I use my backup and re-mount it? I can't access anywhere currently to stop it, or even check if it is still running (I assume it is because plex played files off it earlier). My server is hooked up to a UPS so am hoping that the NUT plugin is still working and that will shut the server down cleanly if I pull the power. Thought I better get some advice first though.

That's good to know, you put my mind at ease about running it like that. Can hold off on any upgrades for a couple of years, except for more storage

Hopefully the latter.

No didn't use 'idle=poll'. I've attached the config file. I did a bit of searching and found that it is not ideal to disable the intel microcode (as it can, but I assume not always affect performance and compatibility, it also includes patches for security vulnerabilities), so I'll probably try re-enabling it at some point in the future (probably when I add more storage) after an update or two - but I'm just happy I have a working unraid install again. syslinux.cfg

@itimpi mentioned in the 7.0.0 release thread that standard updates don't touch that config file, so should hopefully be okay on that front.

Yeah, all cores running, same usage as before. Although not really stressing it, because I have only been using unraid for about 2 weeks and had only just finished moving all my files to it from my old servers - so have only setup a few shares and one docker with Krusader in it. Going to start setting up more containers with plex, sonarr etc and see how it goes. But really liking unraid so far and has a great community

Yes, going to leave dis_ucode_ldr on and see how it goes. Will post here if I have any issues with it, but looking good so far.

noapic did not work for me (I left idle=poll after it, not sure if I was meant to). dis_ucode_ldr does work though, thank you. Using it with unraid, are there any downsides though, log term? Also when unraid 7.1 releases @itimpimentioned in another thread it would use the 6.12 kernel, I wonder if that would fix the issues without having to disable intel microcode?

Yeah, @JorgeB linked me to your post, because I was having the same issue as you, thought we probably had similar hardware (my unraid is running on a i7 6700k / Asrock Z170 OC Formula / 16GB). Will try noapic instead of nolapic and post the results here. At the very least I managed to grab a USB backup this time, I was stressing as I thought I had before the update to 7, but I hadn't noticed the 'unsafe file' warning in brave and so it didn't save my 6.12.14 backup.

Tried this fix, it worked on my server thanks itimpi and JorgeB for your help.

That's good. Again thanks for your help will keep an eye on the other thread to see how it goes with Binary100100 as I haven't got time to pull my server out at the moment.

I do have an old first gen Ryzen CPU and motherboard lying about, but I think I'll try your fix first as the intel system has a lot more sata and m.2 ports. Regretting cheaping out when setting up my rack though as I just used 2 posts and the 4U server with unraid on it is kind of anchoring everything else down Going to sort something better out with that first so I have easier access to pull the server out when needed. If I edit the syslinux/syslinux.cfg file as you said, will any changes get overwritten by the next version update?

Thanks for the quick reply, I'll try the fix you mentioned. Or maybe I should get a different motherboard if that doesn't work?