Shares are gone... ish

[m1ll3rt1m3]

So I made a bonehead move the other day and accidentally pulled the wrong cord while removing a faulty power cable, and unplugged my server.  When it came back online all my shares were missing from the GUI, and not able to be accessed through the network.  My docker containers, however, are still working as though the shares are present. A "ls -l" of /mnt/user returns "Stale NFS file handle"  I have spent the last few days searching through the forums for any kind information, I have cleanly rebooted the system several times and let it complete 2 separate parity checks. Any thoughts on how I could recover my shares to fully operational would be appreciated.

[Squid]

So I made a bonehead move the other day and accidentally pulled the wrong cord while removing a faulty power cable, and unplugged my server.  When it came back online all my shares were missing from the GUI, and not able to be accessed through the network.  My docker containers, however, are still working as though the shares are present. A "ls -l" of /mnt/user returns "Stale NFS file handle"  I have spent the last few days searching through the forums for any kind information, I have cleanly rebooted the system several times and let it complete 2 separate parity checks. Any thoughts on how I could recover my shares to fully operational would be appreciated.

Post your diagnostics.

 

[m1ll3rt1m3]

Here it is.

mediasvr-diagnostics-20151224-1928.zip

[Squid]

Your cache drive has some issues which is causing this

 

Dec 23 09:25:33 MediaSvr kernel: blk_update_request: critical medium error, dev sdc, sector 62208
Dec 23 09:25:36 MediaSvr kernel: sd 1:0:1:0: [sdc] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 23 09:25:36 MediaSvr kernel: sd 1:0:1:0: [sdc] Sense Key : 0x3 [current] 
Dec 23 09:25:36 MediaSvr kernel: sd 1:0:1:0: [sdc] ASC=0x11 ASCQ=0x0 
Dec 23 09:25:36 MediaSvr kernel: sd 1:0:1:0: [sdc] CDB: opcode=0x28 28 00 00 00 f3 00 00 00 20 00

 

And here's the reason for it:

 

  5 Reallocated_Sector_Ct   0x0033   179   179   140    Pre-fail  Always       -       165
197 Current_Pending_Sector  0x0032   194   194   000    Old_age   Always       -       1017

 

Time to throw it out with all the wrapping paper

 

[m1ll3rt1m3]

So just pull the stop the array and pull the cache drive?

[Squid]

Depending on your hardware, you should also shutdown prior to pulling the drive.

 

After replacing the drive, you'll have to setup dockers, etc again (if you don't have backups of the appdata folder)

[m1ll3rt1m3]

Thanks, that worked perfectly. I feel like an idiot for overlooking it but thanks again.

[Squid]

Its a problem (defect) with unRaid that I ran across once, but after I fixed it I've never bothered to replicate it so I can open up an official defect report.  If the cache drive goes down, all user shares also go down.

[trurl]

Your cache drive has some issues which is causing this

 

Dec 23 09:25:33 MediaSvr kernel: blk_update_request: critical medium error, dev sdc, sector 62208
Dec 23 09:25:36 MediaSvr kernel: sd 1:0:1:0: [sdc] UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Dec 23 09:25:36 MediaSvr kernel: sd 1:0:1:0: [sdc] Sense Key : 0x3 [current] 
Dec 23 09:25:36 MediaSvr kernel: sd 1:0:1:0: [sdc] ASC=0x11 ASCQ=0x0 
Dec 23 09:25:36 MediaSvr kernel: sd 1:0:1:0: [sdc] CDB: opcode=0x28 28 00 00 00 f3 00 00 00 20 00

 

And here's the reason for it:

 

  5 Reallocated_Sector_Ct   0x0033   179   179   140    Pre-fail  Always       -       165
197 Current_Pending_Sector  0x0032   194   194   000    Old_age   Always       -       1017

 

Time to throw it out with all the wrapping paper

OP

Did you not get any notifications for these SMART attributes?

[m1ll3rt1m3]

Possibly, but the cache drive hasn't been used in awhile. So ignored most notifications about it.  Had no idea the cache drive would bring down everything else with it.