jdubbs23

Members
  • Posts

    50
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

jdubbs23's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. Ugh, another disk went disabled and not sure why (sdb). Can you take a look at this diagnostics before I stop the array and shut down again? tower-diagnostics-20220918-1039.zip
  2. Thank you so much for your interpretation of my diagnostic files and your help!
  3. Finally got around to checking the cables and restarting. The SMART is there now. Does the drive seem OK? If so what do I do to re-enable things? tower-diagnostics-20220905-1527-array-start.zip
  4. We had a power failure over the weekend and I just got around to starting my array again. It required a parity check upon restart and during the parity check (read-check) I got disk errors from one disk. Not sure how to tell if this is a real disk failure situation or something that can be ignored because of the recent power failure. Thanks in advance for any help/insight. tower-diagnostics-20220822-1357.zip
  5. Well I feel like an idiot, but that was the wrong drive. What got me thinking about it was the size (not typical SSD size), and after running the fdisk utility the name (spinpoint) made me think of a spinning drive and I knew I had an SSD for the cache. So it seems that something happened with the PCIe adapter board that the SSD is connected to, because I opened the case and reseated it and then the drive showed up, I assigned it to cache, and all is fine. Thanks to @trurl and @JorgeB for all the help troubleshooting this with me, and sorry for the incorrect info and my mistakes/forgetfulness.
  6. Yes I would format the current cache drive and add it back into the array and then do the restore. Just wanted to confirm this course of action. Is there something about the drive I was using for cache that could be failing and why the partition is gone?
  7. Well I did use the CA Backup and Restore plugin, so I can see I have a backup of Appdata from 11/27 along with flash and system. I guess the VMs needed to be backed up manually so I just see one of the VMs there from 1.5 years ago (must have did a manual one then). So should I do a restore of the Appdata to at least get Dockers back? I guess the VMs are gone.
  8. That's what I mean, I'm the only one that accesses the array and obviously didn't delete the partition, so I don't understand how this could happen.
  9. Any idea how this can possibly happen? A fully functional array that isn't even being used most of the time just randomly deletes a partition on the cache drive?
  10. OK Here is the diagnostics with the array started and the cache drive unassigned. I can't do anything with it in unassigned devices: root@tower:~# fdisk -l /dev/sdm Disk /dev/sdm: 298.09 GiB, 320072933376 bytes, 625142448 sectors Disk model: SAMSUNG HD321KJ Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@tower:~# tower-diagnostics-20211210-1012.zip
  11. Appreciate you looking into this for me, just wondering if you had any other suggestions. I don't want to lose the data on the flash drive, but I'm not sure how to go about recovering or if there is anything even wrong or if it just some config issue that got messed up.
  12. Is it safe to start the array with the drive reassigned back to the cache slot? I wasn't sure, but can do that and restart the array. I can't remember if I did encryption for the cache drive when I went through the whole process to encrypt the drives. I want to say that I remember not encrypting that one but I can't be sure. When I reassigned the drive to the cache slot it didn't give me any prompts about filesystem or encryption or anything. I had already passed the passphrase to unraid during the first array start after the reboot so I figured the cache drive would use that passphrase if the FS was encrypted.
  13. Ah ok sorry, and thanks for your help with this. Just to clarify: when I first went to the server and discovered I couldn't start the Dockers I did a restart with no diagnostics (I realize that was wrong). Then upon the restart I just started the array and didn't take a close look at the drive assignments but captured the diagnostics then, that is what I attached to first post. While the array was started I noticed the cache drive was in unassigned devices and there was effectively no cache drive. I stopped the array and then reassigned the cache drive to the cache slot. I didn't see any warnings about data loss, and it said "configuration is valid" so I started the array again. Upon this array start with the cache drive in place I see the btrfs error from the screen cap. I got nervous so I stopped the array again and here we are. Attached is the latest diagnostics from where I am currently (step 5). tower-diagnostics-20211208-1021.zip
  14. It was attached to my first post? tower-diagnostics-20211207-2139.zip
  15. OK I noticed my cache drive was in unassigned devices for some reason. I stopped the array and looked at the config and it wasn't assigning the cache drive to the cache slot. So I assigned it back in, started array and it says it can't mount it: