UR v6b15.

 

When my system reboots, even though parity check has completed, it starts parity check over.  I'm also seeing SMART errors - http://my.jetscreenshot.com/12412/20150510-y1fh-185kb.  All these disks have passed preclear.  I've run smart test and not seen any issues reported.

 

I'm also seeing that /dev/md5 takes a long time to unmount when I shutdown the server.  Is there a way to connect /dev/md5 to the /dev/sd??? device name to ID the disk so I can do a smart test?  LSBLK shows both sets, but does not connect them.  This is a screenshot of lsblk.  Is the red arrows in this a correct assumption - MD5 is SDE?  http://my.jetscreenshot.com/12412/20150510-6ocs-65kb. 

 

I found a discussion on drive symbols in the wiki (https://lime-technology.com/wiki/index.php/Drive_Symbols), but though it mentions MD/SD it does not define them.

 

Syslog at https://dl.dropboxusercontent.com/u/35207785/syslog-2015-05-09%20%282%29.txt.  I tried to attach, but too large.

This is in your syslog

May  9 21:54:28 HunterNAS-6 emhttp: unclean shutdown detected

Either you are not performing a proper restart / shutdown (ie: just pressing the reset button), or your flash drive is marked as read-only.  Take you flash drive to your desktop and run chkdsk on it.

I'm very careful to shutdown or powerdown the system all the time.  Whether unraid or windows, OS's like to cleanly shutdown.

 

Almost ALWAYS, even after shutting down properly, if I pull the USB and put it in my windows machine, windows wants to 'fix' it.

 

So your point is very interesting.  Why would this be reported - assuming I'm not lying! ?

 

 

 

 

I'm very careful to shutdown or powerdown the system all the time.  Whether unraid or windows, OS's like to cleanly shutdown.

 

Almost ALWAYS, even after shutting down properly, if I pull the USB and put it in my windows machine, windows wants to 'fix' it.

 

So your point is very interesting.  Why would this be reported - assuming I'm not lying! ?

Do you let windows "fix it"?  Its either some sort of corruption which both Windows and unRaid are catching (difference is that unRaid unlike windows marks the drive as read-only to prevent any further corruption) or the drive is bad.

 

My personal feeling (could be wrong however) is that the majority of flashdrives you can buy out there are cheaply made.  Always go with a good brand name drive.

 

I *think* that I saw somewhere in one of the threads that unRaid now does report the read-only status of the drive.  Probably somewhere in the flash drive section.  But, since mine works properly I can't confirm.

I read about the importance of the brand.  So i bought a good one.  SanDisk Extreme 16GB.

 

Yes, I let windows 'fix it' each time.

 

Not sure what else to do...  The drive is definitely not read only, as I can edit files (i.e. config) and save them from a telnet session, or windows/flash smb share.

I read about the importance of the brand.  So i bought a good one.  SanDisk Extreme 16GB.

 

Yes, I let windows 'fix it' each time.

 

Not sure what else to do...  The drive is definitely not read only, as I can edit files (i.e. config) and save them from a telnet session, or windows/flash smb share.

Not quite sure.  I guess what I would do would be to stop the array. restart it.  See if it starts a parity check.  If it does, I would stop it, restart the array in SAFE mode, and then stop / restart in safe mode again and see if it starts one up.

 

 

To answer one of your questions, md5 is always disk5, but sde may not be. The drive letters get assigned in the order the device responds, but unRAID tracks the drive numbers by serial number.

 

Actually, md5 refers to a logical drive or something like that. If disk5 is disabled, it will refer to the simulated drive that unRAID "constructs" from parity and the other drives.