Hello, Everyone

 

     After coming back from a few days away I turned on my server and ran into issues.   The first sign of something weird was 3 of my Docker's prompted for upgrades and my 4th one was not visible at all.  Only one allowed an upgrade.  When I tried to access my Emby Docker it gave me a login prompt but would not let me in with the correct password.  None of the Docker's would work.  When I started my VM got a BSOD with "Your PC/Device needs to be paired.  File:\Boot\BCD  Error code 0xc0000034."  I went to my console and noticed BTFRS errors.  Here is where I made the #1 mistake and rebooted.  TWICE!  (I had not read how to get support first which tells you not to do this).  Now the Docker menu option won't show me any of the Docker files as if they NEVER existed.   I ran the Fix Common problems including the extended option.  I believe the issue is with my Cache drive (I'm not the greatest at reading these logs). 

     I have a 2nd Cache drive in my uNraid server and thought I had set it up correctly so it could be a backup on the case of failure.  Clearly I have not.

     I am able to access drives via the network from my window computer just fine.  Including the Cache drive (which makes me think I am wrong).  I was able to run a video file that had not moved been moved with Mover yet.  I was also able to access an XML file from my Emby Docker.

    Any advice?  I was tempted run a Parity check, but don't want to make things even worse.  I did reseat the cache drive.  I am also looking into this BTFRS scrub stuff and have been trying to decipher some other stuff from the forum.  I may be making this harder than it is because I have been awake so many hours traveling.  

    I have pasted an excerpt from my syslog but I have also attached the diagnostics info.  

 

Let me also add that this is a Lime Tech server which they stopped selling about two years ago.  

 

Excerpt from Log Files

Jun 25 18:10:00 Tower1 kernel: BTRFS error (device sdb1): parent transid verify failed on 2954323279872 wanted 974484 found 972656
Jun 25 18:10:00 Tower1 kernel: repair_io_failure: 2 callbacks suppressed
Jun 25 18:10:00 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2954323279872 (dev /dev/sdg1 sector 458139616)
Jun 25 18:10:00 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2954323283968 (dev /dev/sdg1 sector 458139624)
Jun 25 18:10:00 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2954323288064 (dev /dev/sdg1 sector 458139632)
Jun 25 18:10:00 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2954323292160 (dev /dev/sdg1 sector 458139640)
Jun 25 18:10:00 Tower1 kernel: BTRFS error (device sdb1): parent transid verify failed on 2953979232256 wanted 974480 found 972648
Jun 25 18:10:00 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2953979232256 (dev /dev/sdg1 sector 457467648)
Jun 25 18:10:00 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2953979236352 (dev /dev/sdg1 sector 457467656)
Jun 25 18:10:00 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2953979240448 (dev /dev/sdg1 sector 457467664)
Jun 25 18:10:00 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2953979244544 (dev /dev/sdg1 sector 457467672)
Jun 25 18:10:01 Tower1 kernel: BTRFS error (device sdb1): parent transid verify failed on 2962357321728 wanted 973098 found 972682
Jun 25 18:10:01 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2962357321728 (dev /dev/sdg1 sector 473831104)
Jun 25 18:10:01 Tower1 kernel: BTRFS info (device sdb1): read error corrected: ino 1 off 2962357325824 (dev /dev/sdg1 sector 473831112)
Jun 25 18:10:23 Tower1 kernel: BTRFS error (device sdb1): parent transid verify failed on 2953940926464 wanted 974479 found 972647
Jun 25 18:10:23 Tower1 kernel: repair_io_failure: 2 callbacks suppressed

Thank you

 

 

tower1-diagnostics-20170625-1828.zip

Edited June 25, 20179 yr by storagehound

Trying to fix a server on only a couple of hours sleep after driving for HOURS was clearly a bad idea.  I think I have now processed all I read yesterday.  I believe there is no physical issues with the drive and will try recreating the Docker image after the system finishes a parity check (I accidentally, killed power last night).  Next time I'll sleep first and try to fix later.  I'll update the forum

These are read/write hardware errors:

 

Jun 25 17:56:23 Tower1 kernel: BTRFS info (device sdb1): bdev /dev/sdg1 errs: wr 7135538, rd 5697740, flush 131769, corrupt 0, gen 0

 

Replace the cables for that SSD, run a scrub, docker image will probably need to be recreated.