January 9, 20233 yr Hi all, posting on behalf of a freind. We powered down his unraid after a disk had failed so we could disconnect it as it kept making a clicking noise. We then powered on the server to make sure data was being emulated etc. All fine at this point, so powered it down as we're waiting for a replacement drive. This was Friday. Fast forward today and my freind notices that that the array was stuck on 'Array Stopping. Unmounting disks...', we could access the UI so tried to run 'powerdown' via command prompt, no result, couldn't get any further so did a hard power down. We then power the server up, all disks were present (bar the one that had been removed due to failing, data was being emulated), go to start the array as there was some important data we needed to access, only to be given a warning that the array has 1 drive with read errors. The Main tab looks like this None of the other drives should have issues, though when veiwing the syslog, we are given these errors, one cpu core is also pinned at 100%, HTOP tells us that it's the syslog utilising the core (This snippet was taken at 9pm): I've attached diagnostics taken when we found the errors/just after we started the array. Any advice, on how to move forward will be appreciated. The server is still running, we have not tried to shutdown or anything. Thanks in advance, Myles tower-diagnostics-20230109-1842.zip
January 9, 20233 yr Author A small update, we tried to issue power down command via command line, as it had completely frozen, UI is inaccessible and on the screen connected to the server we have this. Any advice is appreciated as always. Thanks, myles
January 9, 20233 yr Community Expert Make sure your current directory at the cli is not on one of the disks. pools, or user shares
January 9, 20233 yr Community Expert Parity disconnected and reconnected as a different device, so it isn't part of the array currently. And so disk2 can't be emulated. Check connections, SATA and power, both ends, including splitters.
January 11, 20233 yr Author Hi trurl, thank you for the response, we checked connections and it was still having issues, I then switched the drives from a power splitter to sata plugs wires directly and parity was then detected properly, no read errors etc. so we’ve gotten a new splitter to replace the previous one (a new psu is going to be ordered VERY soon) and all seems to be running as expected! thank you for your response again
February 17, 20233 yr I got a similar situation on both of my servers. One of them is brand new from yesterday and when i start the arrays its telling me that it stopped but all my docker containers is still running. I don't understand I didn't change any of the config on my arrays.. I'm running 6.11.5 on both. svr-unr-001-diagnostics-20230217-1009.zip
February 17, 20233 yr Community Expert Do you have other tabs or browsers accessing your Unraid webUI, including other devices?
February 17, 20233 yr Community Expert None of your disks mounted except for cache Feb 16 19:54:20 SVR-UNR-001 emhttpd: /mnt/disk1 mount error: Unsupported partition layout Feb 16 19:54:20 SVR-UNR-001 emhttpd: /mnt/disk2 mount error: Unsupported partition layout 08:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS 2008 [Falcon] [1000:0073] (rev 03) RAID controllers NOT recommended for many reasons
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.