Alexandro Posted May 19, 2022 Share Posted May 19, 2022 Hello, Just upgraded from stable to 6.10.0. Many problems after the upgrade. I was able to login but on the array screen got "Flash drive offline or corrupted" message. The array has started, dockers and VM too, but no usual information for the disks in the array are visible anymore. No control over the array. Buttons for start/stop array disappeared. Please kindly see my diagnostics and some screenshots. unraid-diagnostics-20220519-0914.zip BB267506-C135-4A75-9ABC-F569362B6780.heic 28CC8DE8-57EA-4DB7-ABEB-9EE50F436B43.heic Quote Link to comment
Alexandro Posted May 19, 2022 Author Share Posted May 19, 2022 (edited) The screenshots uploaded wrongly. Please find them uploaded again. Edited May 19, 2022 by Alexandro Quote Link to comment
JorgeB Posted May 19, 2022 Share Posted May 19, 2022 Nothing obvious, make sure you don't have multiple browser windows open on the GUI, also try booting in safe mode. 1 Quote Link to comment
Alexandro Posted May 19, 2022 Author Share Posted May 19, 2022 Unfortunately this is not the problem. Cleared browser cashe with no result. Sent from my iPhone using Tapatalk Quote Link to comment
Alexandro Posted May 19, 2022 Author Share Posted May 19, 2022 (edited) What I've noticed is that the server initiated parity check, because (after the restart following the update) an unclean shutdown has been detected. As a result according to my observations the parity check is blocking the normal view of the web interface. Once I press on "restart", a moment before a restart is completed the normal web interface page view is showing up. In this moment the parity check is stopped. As no buttons for "stop parity check" are available at the moment (but the check is in progress) How could I stop parity check via command line? Haven't found any command for this. All disk although mounted, are reported by unraid as "off-line" 10 years unraid user here and never had any problem with update so far. Edited May 19, 2022 by Alexandro Quote Link to comment
Alexandro Posted May 19, 2022 Author Share Posted May 19, 2022 Downgraded back to 6.9.2 and issues solved. Reading other users issues we might conclude that 6.10 is buggy enough not to be considered as stable. 1 Quote Link to comment
GrimD Posted May 19, 2022 Share Posted May 19, 2022 I can't even complete the boot process on 6.10 and went back too. Reading all these other issues I don't think I will look to move to 6.10 for a while even if my boot issue is fixed. Quote Link to comment
ljm42 Posted May 19, 2022 Share Posted May 19, 2022 4 hours ago, Alexandro said: Downgraded back to 6.9.2 and issues solved. Everything you described sounds like a flash drive going bad. I would make sure you make a backup and get a new one on order. Quote Link to comment
Lenny Williford Posted May 20, 2022 Share Posted May 20, 2022 I'm having the same issue with 6.10. A parity check started and took my system offline. I had to do a hard reboot, everything loaded back up so the parity check started again after which my system went offline again. Now I can't get it to boot up again. 7 year user of Unraid and have never seen anything like this. Quote Link to comment
Alexandro Posted May 20, 2022 Author Share Posted May 20, 2022 (edited) 20 hours ago, ljm42 said: Everything you described sounds like a flash drive going bad. I would make sure you make a backup and get a new one on order. Although I was very much confident it is not a flash drive related decided to follow your advise. New flash drive prepared. Booted to the same behavior. Once again went back to 6.9.2. No more experiments with the production server for me. Edited May 20, 2022 by Alexandro Quote Link to comment
Lenny Williford Posted May 20, 2022 Share Posted May 20, 2022 1 hour ago, Lenny Williford said: I'm having the same issue with 6.10. A parity check started and took my system offline. I had to do a hard reboot, everything loaded back up so the parity check started again after which my system went offline again. Now I can't get it to boot up again. 7 year user of Unraid and have never seen anything like this. Update: Got my system to boot up again. My issue seems to be related to the parity check so I have disabled parity check on my system. I may go back to 6.9.2. Quote Link to comment
ljm42 Posted May 20, 2022 Share Posted May 20, 2022 51 minutes ago, Lenny Williford said: Update: Got my system to boot up again. My issue seems to be related to the parity check so I have disabled parity check on my system. I may go back to 6.9.2. Please start a new thread to discuss your system. Be sure to include your diagnostics.zip file (from Tools -> Diagnostics) Quote Link to comment
ljm42 Posted May 20, 2022 Share Posted May 20, 2022 2 hours ago, Alexandro said: Although I was very much confident it is not a flash drive related decided to follow your advise. New flash drive prepared. Booted to the same behavior. Once again went back to 6.9.2. No more experiments with the production server for me. I am not sure why, but your flash drive is dropping offline in 6.10. The diagnostics are from before the problem happens so they don't show the error. If you decide to try again at some point I'd recommend going to Settings -> Disk Settings and disabling array auto start first. That will allow you to test the system but if/when the flash drive drops offline it won't trigger a parity check because the array won't be running. Quote Link to comment
Squid Posted May 21, 2022 Share Posted May 21, 2022 17 hours ago, Alexandro said: Although I was very much confident it is not a flash drive related decided to follow your advise. New flash drive prepared. Booted to the same behavior. Once again went back to 6.9.2. No more experiments with the production server for me. Here's a simple test: When the "flash drive offline or corrupted" banner appears. Does it disappear if you navigate to another page (eg: Settings). If that banner does disappear then what you've got is not a flash problem, and safe to ignore. Rather it *thinks* it's corrupted because another process somewhere is changing a file on the flash at the exact same time as the OS is checking to see if it's corrupted.. (ie: a race condition that needs to be accounted for if we could replicate it) 1 Quote Link to comment
Alexandro Posted May 28, 2022 Author Share Posted May 28, 2022 On 5/21/2022 at 4:32 PM, Squid said: Here's a simple test: When the "flash drive offline or corrupted" banner appears. Does it disappear if you navigate to another page (eg: Settings). If that banner does disappear then what you've got is not a flash problem, and safe to ignore. Rather it *thinks* it's corrupted because another process somewhere is changing a file on the flash at the exact same time as the OS is checking to see if it's corrupted.. (ie: a race condition that needs to be accounted for if we could replicate it) Just saw now 6.10.2 available and decided to try to upgrade from 6.9 to not much different result. The bad flash drive banner appeared again (brand new flash drive). The VMs and Dockers started and working although unraid itself tells me that to access the docker/VM page the array must be started first. The drives are reported by unraid that are offline, which is false (the drive appeared to be online and user shares presente). I do not know what exactly has been changed but obviously problems are still there. Take a look on some screenshots and also the diagnostics log attached. Back to 6.9.2 again. unraid-diagnostics-20220528-1423.zip Quote Link to comment
Squid Posted May 28, 2022 Share Posted May 28, 2022 Shot in the dark, switch from using a docker image file to instead using a docker folder. In theory it shouldn't actually make any difference, but trouble with other users using a ZFS unassigned device to store an image and it doesn't work whereas a folder does. Not that you're using ZFS, but doesn't hurt to try it. Settings - Docker, switch the type then Apps - Previous Apps and check off what you want. 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.