IG82

Just experienced the same with the beta and very little by way of a report after the 5 runs. Think I will stick with the regular script from Joe and screen without messing around with plugins.

I gave up in the end and pulled the power. I had tried the provided powerdown script. After this the webgui could not be accessed although telnet was still available. Next boot it did not require a parity check so can only assume that the script did most of the job cleanly Would be great to have some more ideas here, not being able to shutdown the server cleanly and at will is an issue.

Yeah, as above nothing returned by lsof, assuming fuser /mnt is the correct way to run that returns nothing either. I have nothing open I am aware of, and wouldn't that report as something being open via lsof or fuser? Also a screen session can cause this - easy to forget they might still be hanging around Yup, have done this many times before so first thing I do is exit any screen sessions before trying to shutdown now

This has occurred before but I have grown impatient and forced it to shut-down by holding the power button. I am running 5.0.6 on a Microserver, no plugins or anything special with the exception of Unmenu. After trying to stop the array it gets stuck at 'Retry unmounting user share(s)'. Attached is my syslog. I have searched for similar problems and although found the same error the resolutions did not work. Running lsof | grep mnt returns nothing. Any suggestions on how to diagnose what is causing this so I can stop it happening on every shutdown would be appreciated. Thanks Ian syslog-2015-04-03.zip

Oops, messed it up trying to embed it, fixed now. I may try and use a fresh usb with some fresh disks and see what happens. EDIT: In case anyone else is worried Tom has confirmed this is not a real problem this thread

Has anyone with a Microserver updated to RC10 yet? Wondering if anyone has had the CPU errors I have outlined in this thread. Mine is an original N36L with the updated AHCI bios with 5 mixed disks and 2GB RAM. Due to these errors I am hesitant to update my main one.

Thanks Joe, guess I was expecting a Cat 5 given that the drive is brand new but sticking it through 21 hours of straight use has probably given it a little wear

Thanks for the script Joe, just used for the first time but plan on getting into the habit. I have just cleared a brand new 1.5TB EADS WD drive, took a little over 21 hours! Here are the details from the Smart tests, the raw error read rate has increased during the test from 0 to 1. None of my other WD non-EADS drives have any errors of this type so I don't think it is an anomaly due to first use. Is it something to be concerned about? > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command from host. 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 1 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 14 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 16 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 =========================================================================