Jump to content

NetApp DS4486 - Having issues after update to Unraid 6.12.4 from 6.10.x


Recommended Posts

I am unable to access these disks in the sense that I can't view data. It shows they are full. There are no temp stats. If I click on the log for a disk it shows this and fills up as fast as "humanly possible". It shows they are there and still in the pools I put them in. It shows they are spun up, etc....

 

Here is one pool I created, so you can see.

 

 

 

Nov 29 09:12:15 Tower kernel: BTRFS error (device sdbh1): bdev /dev/sdbn1 errs: wr 5840, rd 112653, flush 0, corrupt 0, gen 0

 

I have 48 of these disks and they are all acting the same. Again, no issues prior to the update. They were viewable, writable, providing smart data etc... prior to the update.

 

Any ideas at all would be greatly appreciated and helpful.

Edited by live4soccer7
Link to comment
  • 2 weeks later...

I am also getting these on sonarr/radarr imports. This is also on the normal array and not on the disk shelf.

 

[v3.0.8.1507] System.IO.IOException: Input/output error at System.IO.FileSystem.LinkOrCopyFile (System.String sourceFullPath, System.String destFullPath) [0x000b9] in <533173d24dae460899d2b10975534bb0>:0 at System.IO.FileSystem.MoveFile (System.String sourceFullPath, System.String destFullPath) [0x0003a] in <533173d24dae460899d2b10975534bb0>:0 at System.IO.File.Move (System.String sourceFileName, System.String destFileName) [0x00083] in <533173d24dae460899d2b10975534bb0>:0

 

I went into mc and I am unable to create a folder. It gives me an I/O errors there as well.

 

Definitely something wrong. I'll reboot this evening. It takes a while to reboot and bring all services back online when you're running a lot.

 

 

Edited by live4soccer7
Link to comment

after rebooting the radarr and sonarr files (on the unraid array) transferred without issue automatically. I have attached the syslog that is from right after I did a reboot. I set to log to flash since logging to cache didn't work. All of the disks from the diskshelf are, again, recognized after the reboot. These disks are not a part of the unraid array, but are separate pools.

 

everything appears to working just fine right now, but I'm sure that will change. I'll check disk logs once or twice a day and update the latest syslog once I notice the issue comes back.

syslog

Edited by live4soccer7
Link to comment

I have just shutdown the system before our planned outage today. The disks were all working properly and the array was able to be stopped / taken offline, while when there were disks issues (after a few days or a week) I was unable to take the array offline with the Stop array button. I'll post up new logs after a fresh reboot since it will log to the flash as soon as possible. That was only setup after it was booted last time.

Link to comment
  • 3 weeks later...

We lost power again, so everything rebooted. I hadn't gotten the actual error yet. I was thinking it was a preliminary issue to the primary one originally posted. I would try and spin up the disks and it they would just not spin up. If I access the shares/disks/pools on a pc then it actually does spin them up. I have set them now to never spin down as I don't want them to spin down.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...