live4soccer7

Wouldn't the mere fact it didn't show up in the boot menu at all when other devices do that don't have anything bootable suggest that the drive wasn't even functioning at all at that time?

I believe my USB, which I got based on test for the most reliable USB, is failing. I had to upgrade it maybe a year ago due to the one I had in there for 10yrs only being 1GB and it not having enough room to update the OS anymore. Today the server crashed, highly irregular, and upon reboot it said "This can not be fixed automatically", then i saw references to sda1, which the USB is sda. Then saw something regarding bits and disabling something. I did have to attempt boot a couple times. The second time the USB boot option did not show up at all on the boot menu. It finally booted, complaining of bad bits (or something along those lines). Once it booted I got a fresh backup of the USB. It has been a couple hours, but I don't know what else it could be. I highly doubt it is actually the USB port. I'll probably head to walmart (closest place to get a usb stick). This is probably my best/quickest option right now: https://www.walmart.com/ip/SanDisk-64GB-Cruzer-Glide-USB-2-0-Flash-Drive-2-Pack-SDCZ60-064G-AW46TW/331396621

Thank you very much. I have never used Dynamix File Manager. What a great addition!

I just want to remove the files on that specific drive, leaving the contents on the rest of the server alone.

I've got a share that I have only specific drives that are on that share. I want to remove one of the drives from the share and then delete the contents on the drive so I can add it to my main unraid share. What would be the best way to go about doing this? I don't think I've really had to do this before and wanted to ask before going about it. Can I just simply remove that disk from the inclusion list of that share? What would be the best way to delete the contents that are on that specific disk?

I'd prefer a docker setup for unraid, but it's just how I was able to get it setup.

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.

I have lost connection to MOST of the disks now, but the disk errors aren't showing up yet in the disk logs. Here is the current syslog. I believe the lost connection started yesterday or late the day before, which would be the 6th/7th. syslog (3)

Syslog after rebooting with it starting w syslog service active. syslog (2)

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.

I probably won't have more logs for at least a few days. We have a planned power outage here and I'll have to take the server offline for a bit, restarting this process.

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

I have enabled syslog services to log locally on a cache drive. I'm not sure if it takes a reboot, but I didn't not see any in the folder I selected.

These logs won't contain the disk shelf root issue from when it started, however it may have clues as to why it is impossible to take the array offline. tower-diagnostics-20231219-1542.zip

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.

Thanks. I'll take a look.

@JorgeB It seems to have cropped back up again. The entire shelf offline with the same errors as the original post in this thread. I'll have to reboot and try and catch it when it happens, which can be quite tough since it takes a while and doesn't notify me.

I just upped the docker img size.

Will do. Thanks.

The issue is resolved.

While going to reboot this morning I noticed 6.12.5 was available. I applied the update and rebooted. It seems things are back to normal.

Thank you. I will get it rebooted today and report back.

@JorgeB Thank you for taking a look. You were there when I had a couple questions regarding this setup 2-3 yrs ago (the netapp shelf and the stats).

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.

I didn't really solve this issue, but it is plex doing it. I bumped up the docker image another 30G or so and plex does whatever processing it is doing and it reverts back to normal. At least it isn't completely filling up the docker image and potentially causing issues.