Hello,

 

I am not an expert. Not sure what happen. Array was running for a long time without any issues. Today in AM, noticed that I cant connect to a VM. Check array and it was shut down with error for a missing drive. I rebooted and it found the disk and came up fine after that. But now I see that shares are not showing. Not sure where to start. 

If this happen before, maybe someone can direct me to another thread for this issue. I saw a few about permissions issues on mnt/user but I did not touch anything. 

 

Thank you 

tower-diagnostics-20231017-2025.zip

I shut down docker and restarted the array. Now I can see my shares. I am guessing an auto update happen on docker and maybe it screwed up my array. my VMs having issues now as well. They keep crashing and going into recovery   .  Array parity started I figured i let it run to make sure all my drives are ok. Then i will enable docker one at a time to see which one is crashing the array.  Also probably need to rebuild my VMs?

 

 

tower-diagnostics-20231017-2159.zip

You appear to me to have a problem with your flash drive  (sda is your flash drive).  I would suggest shutting down the server, pull the drive and plug it into your PC.  Make a copy of its contents.  Then run chkdsk on it.   If that does not fix it, report back. 

 

Oct 17 21:35:41 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Oct 17 21:35:41 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
Oct 17 21:35:41 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0
Oct 17 21:35:41 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 4c e0 00 00 f0 00
Oct 17 21:35:41 Tower kernel: critical medium error, dev sda, sector 19680 op 0x0:(READ) flags 0x84700 phys_seg 2 prio class 2
Oct 17 21:35:41 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Oct 17 21:35:41 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
Oct 17 21:35:41 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0
Oct 17 21:35:41 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 4d 50 00 00 08 00
Oct 17 21:35:41 Tower kernel: critical medium error, dev sda, sector 19792 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

 

Thank you.. That helped..  I fixed my Flash. Then i also tried to update code to stable version and was getting MD5 error. Suspected Ram issue. Ran MEMTEST and Ram failed it. I took out the sticks and tried to test each one separately and they both passed on their own :).  I put back both and tested again and MEMTEST passed. Strange. Maybe Ram is about to fail soon or maybe was not very well seated in the slots. 

 

After starting OS , i am able to update to highest stable level and VMs started as well after a little repair of the bad shutdown.

 

Thank you again for directing me in the right direction.