Paulitix

Thanks for looking. Should I consider replacing the USB stick?

Can someone advise where the failure was? Does the disk need replacement? apollo-diagnostics-20221007-1728.zip

Can anyone help to see why my server periodically becomes unavailable via smb/ssh/cifs shares, yet the web GUI is always available. It has been fine for years, and suddenly this issue arose. FYI: Im currently running unRAID via vm on ESXi, but others VMs are not exhibiting this failure. apollo-diagnostics-20220705-0132.zip

Can anyone help to see why my server periodically becomes unavailable via smb/ssh/cifs shares, yet the web GUI is always available. It has been fine for years, and suddenly this issue arose. Im currently running unRAID via vm on ESXi. apollo-diagnostics-20220705-0132.zip

I came home from vacation and my cache drive seemed to be dead (showing unmountable filesystem). I thought I disabled cache, but maybe this is why it failing; cuz the mover is trying to access a cache drive that is inoperable?

Can anyone advise why my shares keep disappearing. A reboot restores them for a short while and then they hide again. The syslog is spamming an issue with my boot USB. Does this mean it's dying? May 18 19:50:13 Apollo kernel: sd 0:0:0:0: [sda] 15240576 512-byte logical blocks: (7.80 GB/7.27 GiB) May 18 19:50:14 Apollo rc.diskinfo[3920]: SIGHUP received, forcing refresh of disks info. apollo-diagnostics-20220519-0257.zip

I hope this is not in the wrong place: Im going away next week. My dad's sytem just took a nosedive (built it almost a decade ago) so he wants me to source him out another one (HDDS still good). Due to time constraints, I'm just gonna have to travel with the parts and build when I get there. Can anyone give me quick suggestions for MOBO + CPU + RAM. I think I'd prefer to use intel but not 100% opposed to AMD based. Main Use: Media Storage + Playback (Plex) Basic dockers used (SAB + Sonarr + Couch/Radarr) Further Virtualization (Windows VM) would be a nice to have but not necessary as this is basically used as NAS. Thanks in advance

I previously built a server for my father using an AZZA Helios 910 case with 9 hot-swap trays. Theres also a cache SSD that floats in the case. The case mechanics of the case power has kicked the bucket. Can anyone suggest a case that I can use as a replacement? Thermal efficiency is priority, as usual.

Earlier today I got email notification about read errors in the array and now my shares are unavailable. It's strange that it's a cluster of drives on the same controller which makes me think it could be a connection. Can someone please advise if I need to be worried. apollo-diagnostics-20210731-2207.zip

Yup, stop array, unassign, start array, stop, add, start, and rebuild should commence.

No, the server has been shutdown for over a month. So whayyu think, can i just re-enable and rebuild?

I possibly had a seating issue resulting in HBA errors... Shutting down and reseating everything has brought me back to somewhere more navigable. I will link the post to that prior issue which has the diagnostic from before the shutdown.

Disk 1 (sdc) apollo-diagnostics-20201030-1806.zip

My parity looks screwed at this point...do I just force a shutdown and start to work from there?

My array is doing some alarming stuff. The disabled/emulated drive is a somewhat straightforward fix, but the trillions of errors and unassigned drives are concerning. Can anyone tell me whats going on here. I can't even stop the array or pwerdown. apollo-diagnostics-20200919-0348.zip

New diagnostics as requested. aramis-diagnostics-20200319-1449.zip

Hi, Trying to help my pops troubleshoot his system. Is it time to swap out disk5 (sdj)? aramis-diagnostics-20200315-1353.zip

This all started with a parity upgrade. I wanted to swap out a 4tb for an 8tb, so i just replaced the old drive with the new and rebuilt parity. When it was done, my drive 8 (heretofore md8) was red-balled. The filesystem was corrupt and couldnt be repaired in-place. Using UFS I was able to save some data, but not all, which is currently sitting on a spare 8tb that is also eventually supposed to make its way into the array. The array is currently in maintenance mode while I try to figure out whats next (re-formatting md8, I'd guess.) During the parity rebuild, disk 7 also showed read errors, so my new parity is most likely corrupt. What are my best steps from here? I still have the original parity drive which may or may not be valid since I've written nothing to the array since the upgrade. I also have a spare 8tb (currently holding the recovered data from md8) and I will pick up a replacement 4tb for disk 7 tonight. Can I tank the whole array by trying to revert everything back and rebuilding md8 from original parity? What impact will the read errors on disk 7 have (currently passes short SMART, will not complete extended). Seeing as I might not have valid parity, should I try to mirror the contents from disk 7 onto the replacement and then proceed? The compound issues have me questioning what to do next as I dont want to do more damage by doing the wrong thing. I've attached two diagnostics: one following the parity rebuild, and one with the array in maintenence after recovering some data from md8. I've posted about each issue previously to which johnnie.balck replied (thanks!) but I figured I should inquire about the whoel picture. apollo-diagnostics-20191016-2013.zip apollo-diagnostics-20191027-0357.zip

The short test passes. The extended craps out and says to check SMART report. I've attached the result. apollo-smart-20191027-1411.zip apollo-diagnostics-20191027-0357.zip

Ugh, the remaining disks are showing minimal writes, but writes nonetheless. My array is currently sitting in maintenance mode. How should I go about this copy? What sould be my next steps to recover as much as possible (including kissing that drive's contents goodbye)? Right now I have a fresh disk that I was going to add after the parity upgrade, as well as the old parity drive that was replaced. Everything until then was in good wokring order, or so I thought. Is there a way I can try to save any files off the disk by connecting elsewhere (say another PC/Windows), putting the disk back, re-formatting, and then rebuilding parity? Or do disk 4 and 7 complicate that as well?

Would it make any sense to put the original parity drive back and try to rebuild from there?

Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... ....found candidate secondary superblock... unable to verify superblock, continuing... ...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................Sorry, could not find valid secondary superblock Exiting now.

After upgrading parity a disk (md8) was returning red ball. I tried to run xfs_repair and it says it couldnt find a valid secondary superblock. Any tips as to my next course of action? I've attached the most recent diagnostics, but I have a few from the last few days, including one right after parity was rebuilt. apollo-diagnostics-20191016-2013.zip EDIT: Looking back at an older syslog, it starts to get messy at the end. The log just ends, but I did nothing but clean shutdowns on the array. I also still have the old parity drive if theres some kind of rollback I can perform apollo-diagnostics-20191015-1159.zip

I'm having the same issue, yet mine is set to Yes. Any where else I can look? I've tried manually running the mover. When I display folders in the share via the unRaid GUI, I do see that some of them are using the cache drive, which has been there from day one and always set to yes. EDIT:: Currently investigating split settings. Will update results. ANSWER:: Yup. Split was set too tight so it kept files on cache (Had it set to 3 levels, i just opened it right up and said split whatever you want).

Plex never works for me after a reboot. I have to manually remove and install the plugin and I've been doing so despite knowing that this should not be... Nevertheless, now I can no longer even do this. When trying to removepkg, I get the following: root@Aramis:/boot/extra# removepkg PlexMediaServer-0.9.9.7.429-f80a8d6-unRAID.txz Removing package /var/log/packages/PlexMediaServer-0.9.9.7.429-f80a8d6-unRAID... Removing files: sort: write failed: standard output: No space left on device sort: write error sort: write failed: standard output: No space left on device sort: write error sort: write failed: standard output: No space left on device sort: write error It is currently set to install to /mnt/user/ and I read somewhere that /mnt/cache/ is a better option. I am currently unable to retrieve a syslog, but the last one I have is inundated with lines like this: rsync: recv_generator: mkdir "/mnt/user0/unApps/install/plex/library/Application Support/Plex Media Server/Media/localhost/9/816530c0571d6f7a307190bab1d9a7e0fb358ff.bundle" failed: No space left on device (28) I cant even post that file since it is 1.5MB zipped. Any help on how to get Plex removed from my system?