trashman

Members
  • Posts

    5
  • Joined

  • Last visited

trashman's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I just setup a new SAS controller and did not do enough homework before purchasing since 'find common problems' pointed out to me that uNRAID and Marvell SAS controllers have compatibility issues. I decided to use it for a few days while I waited for a replacement and noticed that one of my disks became disabled. I tried switching it back to SATA with no luck. There was previously an option to format the disk on the main page (the format unreadable disk checkbox), but that is no longer available. I understand I can get the disk back by removing it from the array then adding it back and formatting, but all my previous disk issues have been resolved without full reformats so I'm optimistic that that's possible here too. Thanks for any help! trashmetal-diagnostics-20210607-1003.zip
  2. Thanks guys! So two followup questions: 1. Should I start using XFS for my cache pool, or is BTRFS fine if your RAM isn’t shitting the bed? 2. Should I expect the drives to start functioning again after I identify and remove/replace the faulty DIMM? If not is there anyway to recover the appdata folder before reformatting?
  3. So to clarify, corruptions with my RAM are causing the issues with my NVME drives?
  4. Running it right now and it is finding what looks like a lot errors (see attached).
  5. My cache pool went read only after having some docker issues that lead me to reboot. This happened to me previously and I solved it by moving all my shares to the array, formatting the drives, then moving them back. Now, before I could move my appdata share to the array, I started getting this message in the Main tab: Unmountable disk present: Cache • Samsung_SSD_970_EVO_1TB_S5H9NS0NB61321J (nvme0n1) Cache 2 • Samsung_SSD_970_EVO_Plus_500GB_S4P2NG0M218576P (nvme1n1) And the following message when I try to mount manually from the console: $ mount /dev/nvme0n1p1 /mnt/tmp mount: /mnt/tmp: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. This is the second time the cache pool has randomly crapped out me on going read only so I’d love to hear any steps I should take to avoid having that occur again. My diagnostics are attached. Thank you for any help! trashnet-diagnostics-20210226-1311.zip