Tetromino Posted June 22, 2022 Share Posted June 22, 2022 (edited) I had a genius show up at my house and shut off the main breaker without telling me; UPS lasted long enough for me to just get there and watch it shut down... FML. Now I'm getting a stale configuration error when starting the array. I fear I have made it worse by removing a drive and re-adding it; now disk 6 is emulated. How screwed am I? tower-syslog-20220622-1307.zip tower-diagnostics-20220622-0914.zip Edited June 22, 2022 by Tetromino Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 4 minutes ago, Tetromino said: removing a drive and re-adding it Why did you do that? Did you actually remove it physically, or did you just unassign it? Did you start the array without it? Attach diagnostics to your NEXT post in this thread. Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 I did not physically remove it; I unassigned it. Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 2 minutes ago, trurl said: Did you start the array without it? This was actually the most important question Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 3 minutes ago, trurl said: Attach diagnostics to your NEXT post in this thread. Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 tower-diagnostics-20220622-0914.zip Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 It says disk6 is invalid. Did you start the array after reassigning the disk? Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 No, I did not. It says device contents emulated on disk 6. Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 Just now, Tetromino said: It says device contents emulated on disk 6. Where does it say that? Diagnostics doesn't say disk6 is missing or disabled, it says invalid, which leads me to believe it had already begun rebuild. But, from diagnostics, it doesn't look like the array had even been started since last reboot, so nothing was being emulated. Maybe you stopped rebuild and rebooted before getting those diagnostics? Can you give more complete description of everything you have done? Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 Sorry to clarify: I unassigned the disk -> reassigned it -> then started the array in maintenance mode; disk 6 was assigned when starting the array (I did not start the array with an unassigned disk) After which I noticed the "device contents emulated" icon on disk 6. Its quite possible I interrupted something but there was no indication or warning of doing so. Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 The array wasn't started when you got those diagnostics. Is it now? Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 No, its not started now. Shall i start it and upload diagnostics? Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 If you start it with disk6 assigned, it is going to rebuild it. You are probably going to wind up rebuilding it anyway, but it would be useful to know if the emulated disk is mountable, since the emulated contents is what would be rebuilt. Unassign disk6, start the array, post new diagnostics. Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 Starting the array with Disk 6 unassigned results in a stale configuration. tower-diagnostics-20220622-0950.zip Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 Those diagnostics shows all disks mounted including emulated disk6. But the screenshot shows array stopped. Strange. I assume you didn't change anything between taking the diagnostics and screenshot. Is that correct? Let's see if @JorgeB has anything to add to this. Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 Are you supposed to have a cache disk? I assume not since no disk shows up for that and all shares are cache-no Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 No nothing was changed in between diagnostics & screenshot & no cache disk. Been meaning to add one. Quote Link to comment
Solution JorgeB Posted June 22, 2022 Solution Share Posted June 22, 2022 12 minutes ago, trurl said: But the screenshot shows array stopped. That's because of this pesky "stale configuration" error, array is starting, just not showing in the GUI, make sure there are no other browser windows open in the GUI, including phones or tab, also clear browser cache. Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 Omg, yea it looks like my dockers are up and running; although it says "Array must be started to view docker containers" at the top of the screen. Should I reassign the drive and let it rebuild? I'm assuming it will take a while but the GUI wont tell me? Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 Fix the stale configuration before reassigning/rebuilding and the GUI will tell you. 22 minutes ago, JorgeB said: make sure there are no other browser windows open in the GUI, including phones or tab, also clear browser cache. Did you? Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 I closed all browser sessions on my current pc; I may have a session open on a different pc I dont have access to atm. Currently stale configuration error is still there even after clearing browser cache. Quote Link to comment
trurl Posted June 22, 2022 Share Posted June 22, 2022 21 minutes ago, Tetromino said: may have a session open on a different pc I dont have access to atm When? Quote Link to comment
Tetromino Posted June 22, 2022 Author Share Posted June 22, 2022 From earlier this morning on a different pc. Would rebooting unraid + clearing browser cache on my current pc clear the stale configuration GUI error? Thus far I have closed all open browser windows, cleared browser cache & rebooted my machine. Still getting the GUI error. Quote Link to comment
JorgeB Posted June 22, 2022 Share Posted June 22, 2022 This error can be a little elusive, sometimes I can't see a reason for it. Quote Link to comment
Recommended Posts
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.