ajtatum

Members
  • Posts

    25
  • Joined

  • Last visited

About ajtatum

  • Birthday 04/17/1984

Converted

  • Gender
    Male

Recent Profile Visitors

322 profile views

ajtatum's Achievements

Noob

Noob (1/14)

0

Reputation

  1. So, what's the process for rebuilding on top? Sorry, I just can't seem to find anything in the UI that says "rebuild" or anything along those lines.
  2. By the way, the parity check completed and reports zero errors...
  3. Yea, I know the USB connection isn't ideal. It was really just a way for me to test out unRAID with the intention of getting something (either a custom-built mini ITX case or a Terramaster F4-423) later on. I took one disk offline, and it's now an "Unassigned Device" and under "Array Devices" it shows "Device is missing (disabled), Contents emulated". Attached are the diagnostics. I appreciate your help in getting this figured out. What's weird to me is that all the Docker containers are working perfectly fine even though all the devices show as "Unmountable". Thanks, AJ xaviertower-diagnostics-20230821-0813.zip
  4. I'm doing a parity check now, would that process rebuild each device? If not, how do I go about doing that? My best guess is that it's due to the 4 hard drives being connected in a 2.5" 4 disk USB enclosure as I'm running it on a mini PC that used to be my router, so I don't have the actual connection capabilities. There's just one 2.5" SATA connection on the device itself. I'm debating about whether or not I should by something like a 4 bay Terramaster NAS and run unRAID on that. As otherwise I'm not enough of a hardware guy to build my own setup. Anyway, do you think the issue could be the USB setup?
  5. Sure, I forgot how I fixed it last time without losing all my data. I recall clicking on "New Configuration", I think. All I recall is that I was 99% sure that it wouldn't recover, but it did. xaviertower-diagnostics-20230820-1256.zip
  6. This is the second time when all the drives in my array are unmountable. Out of the servers and NASes I have or had, none have caused issues like Unraid has. It's literally a maintenance nightmare as I never know what to expect when I log onto the Unraid server.
  7. Yea, I tried that too... Left parity drive on and attempted to boot up with disk 1 & 2, 1 & 3, 2 & 3 but disk 3 continued to not mount correctly and disk 1 & 2 showed "Unsupported Partition Layout".
  8. So, I tried removing the devices from the array but it said invalid configuration. The parity drive may very well be messed up as there's no file system specified for it.
  9. I'll give that a shot, but I'm also starting to think that this got FUBAR'd somehow. It happened after upgrading to the latest version of Unraid, so unless it's just pure coincidence, the upgrade did something that wreaked havoc on my server.
  10. Another thing that's interesting is that I'm 99% sure that my file system was btrfs, as that's what my Cache device is, and for the array disks it shows "XFS" and in the default settings for disks it also shows "btrfs"
  11. When I try to take the array off-line, which I believe is the way I'd unassign them from the array, it just hangs at "Stopping" and doesn't do anything unless I reboot the device. Spinning down all the disks also does nothing. Is there a better way to remove the devices from the array? Under "Historical Devices" there's a "X" to remove a device's configuration, but I'm not sure what that would do exactly. I didn't use Unraid as a NAS server, more like an App Server and have the docker backups on my Synology. So I'm debating whether or not I should just format the disks or not, but what's still disturbing is that Disk 4 has a red "X" next to it saying that the device is disabled, and the contents are emulated. So, somehow 3 of my 4 disks got screwed up.
  12. Ok will do that shortly, but how does this happen? Knock on wood, but I haven't had any issues with Synology or when I was running TrueNAS.
  13. After upgrading Unraid, I noticed that my SSDs are all pretty much unhealthy except for the parity drive. I have no idea what the root cause is besides the upgrade. Attached are my diagnostics. xaviertower-diagnostics-20230720-2113.zip
  14. Is the Reactive Resume the latest version of the project? The docker shows v1 and there's hardly any configuration settings available, as compared to what's on https://github.com/AmruthPillai/Reactive-Resume and reading the installation and the environment variables, etc. I was hoping to try this out... would there be anyway you could update it?