Karyudo

Members
  • Posts

    190
  • Joined

  • Last visited

Everything posted by Karyudo

  1. Ah! That's something I didn't try, of course, having been scared off by the warning when I moved the first. I'll give that a try. Thanks!
  2. Recently, my single 500 GB SATA SSD btrfs cache drive (identified by Unraid as 'Cache') had a minor SMART error, so I upgraded by adding two 1 TB NVMe m.2 btrfs drives to the cache pool ('Cache2' and 'Cache3'). I then followed instructions to remove the original drive. Now I'm left with a Cache Pool that shows three slots, with only slots 2 and 3 populated. Like this: https://imgur.com/a/oAb1Xx6 I tried to move 'Cache2' to 'Cache', but Unraid reported that all data on the drive would be erased. Umm... that doesn't seem right! How can I tidy this up so that the two 1 TB drives are correctly seen as 'Cache' and 'Cache2' in a two-slot cache pool?
  3. I have the same error (that's why I'm here), and I haven't yet taken any steps to try to fix it, but I wonder if file/folder permissions have something to do with it? On the same day I believe my Sonarr started not grabbing things and throwing this error, I had Unraid support do some maintenance, including running chmod and chown on all my files.
  4. Oof. Thanks for the quick diagnosis. Guess I'll either have to solve it on a Windows machine, or copy everything off the drive.
  5. OK, so now I have two problems: my original problem, and I don't know what "look at the log" means. I definitely didn't do anything on purpose to mount the drive RO. I'm now also increasingly sure that I got the drive back from the data recovery place with it write-protected. Alright, I found the log, and it says, "Jan 17 09:13:56 <servername> unassigned.devices: Mount warning: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) Could not mount read-write, trying read-only"
  6. Today I mounted an NTFS drive that I got back from a data recovery service probably a year or so ago, which I received write-protected. I see in UD that it's mounted as 'RO'. How can I un-write-protect this drive, so it mounts read/write in UD?
  7. For about two months now, my Plex server (in Docker) doesn't parse new materials from -arr Docker instances and add them from the unRAID file structure. A second Plex server on separate hardware (non-Docker) has no issues. It's like the Docker instance is read-only, even though I don't see anything that explicitly says "your Docker instance of Plex is now read-only." This all used to work just fine. I didn't change anything. Can someone please help me step through a fix? Thanks!
  8. Yes... ish. There's important and irreplaceable, and then there's IMPORTANT AND IRREPLACEABLE. Personal photos and documents, hell yes I've got other backups! 40+ TB of Linux ISOs that are going to take forever to redownload? No—considering the size and fact they're technically replaceable, parity is my reasonable hedge against loss.
  9. Ah, good to know! Thanks. And yeah, I guess that makes sense. Sort of collapses steps 1, 3, and 4, and saves a bunch of time. I usually preclear new drives to fend off infant mortality, but considering the drives being added were until recently healthy parity drives, that shouldn't be an issue.
  10. OK, more detail... I have four disks in my system right now: 2x 4TB array drive, BTRFS 2x 10TB former parity drives I want to end up with those same drives in this configuration: 2x 10TB array drive, XFS 2x 4TB drives retired from system Current parity is two 18TB drives, just rebuilt last week (one at a time) as I swapped out the 10TB drives. There is just over 6.5TB free in the array currently, with each of the 4TB drives at 3.69 TB full. My plan would be: 1) Stop array. Use New Config to remove both 4TB BTRFS drives. 2) Restart array, and wait for parity to rebuild (about 40 hours). Not thrilled I'll be without any parity protection at all for nearly two days, but I guess that can't be helped. 3) Can I preclear the two 10TB former parity drives at the same time the parity is being rebuilt, while they're Unassigned Devices? 4) Stop array. Add both 10TB former parity drives as array drives. Format XFS. 5) Mount both removed 4TB BTRFS drives in UD. 6) Using Krusader (sorry, Midnight Commander: I think it's going to be easier to copy things to the right places with a GUI...) copy data from 4TB drives back into the array. Seems tedious but not complicated. Unless I'm missing some finer point like, "do this important step at the beginning, otherwise several irreversible steps later you won't be able to do something crucial, and you'll lose a whole bunch of data." Or has BTRFS matured enough that it's now at least as good a choice as XFS? If so, maybe I change my plans and just swap in the 10TB drives in place of the 4TB drives, and rebuild from parity...?
  11. This sounds important, and I don't know how to make sure I've got it set up right. Is there a quick summary someplace that would run me through the setup? Or is there something better than Krusader that I should be using these days (that can handle UD)?
  12. Y'know, I have no idea why I've never tried reloading the page! I should have figured this out on my own, since I did notice that moving to a different page and then back got rid of the persistent notifications. A smarter person would have made the mental leap to a simple page reload. I'll keep this in mind next time a half-page of notifications won't go away. Thanks!
  13. How can I remove some smaller-capacity BTRFS drives and swap in some larger-capacity XFS drives? I recently completed some parity drive upgrades, and I'd like to now use the two former parity drives as data drives, replacing two existing smaller-capacity data drives. The wrinkle is that the two smaller-capacity drives are formatted BTRFS, so I'd imagine merely swapping drives and rebuilding from parity would result in the new drives being BTRFS, too. Not what I want: after I had a BTRFS drive write errors due to a flaky, not-completely-supported SATA controller, I was advised that XFS is still a safer/more robust format than BTRFS, so I'd like to take this opportunity to switch to XFS. I'm guessing it's something like: • stop array, remove BTRFS drive from configuration, add new XFS-formatted former parity drive as data drive to configuration, restart array • mount BTRFS drive under Unassigned Devices • use Krusader to copy data from UD-mounted BTRFS drive to array ...right? Any insight or advice or admonishment is appreciated!
  14. Can the notifications please be put someplace else, if the close all and 'X' buttons almost never work? Pisses me off that the notifications cover up useful information, but can't be closed or moved.
  15. Well, dammit. I started using that disk in UD 'cause I didn't think I cared much about anything on it, but now I have remorse. Even though I didn't lose anything personally valuable. Thanks for certifying the death.
  16. Extended SMART test results attached. For real this time. shinagawa-smart-20210815-1156.zip
  17. Arrgh. I wish I'da noticed yesterday, when I was free at home all day. Now I'm at work, and don't have access to the file. I'll fix that in about 11-12 hours.
  18. OK, extended SMART test results attached...shinagawa-smart-20210815-0855.zip
  19. I've got the 2021-08-05 version of UD, which is marked as "up to date," and I do see the check mark, so I think I'm good to go. I have spare cables and SATA ports on a different controller... if you think it looks more like either or both of those things is a possible issue, I assume I should try switching those things up first, before I do any chkdsk /f stuff?
  20. "In the first case run chkdsk /f on Windows then reboot into Windows twice." Sooo... it can't be dealt with using UD or even while attached to my unRAID machine, and I need to connect it to a Windows machine instead?
  21. Ah, yes. But of course.... It's 'sde' that's the drive I'm asking about here. shinagawa-diagnostics-20210815-0625.zip
  22. I'm having trouble mounting a certain NTFS drive with UD under 6.9.2 that previously mounted. Before rebooting to install 6.9.2 I also had a problem with Transmission giving me an I/O error, so I suspect this drive isn't in great shape, although running a SMART test seems OK? Now when I reboot unRAID, I get a 'current pending sector' error popping up that seems to resolve itself. I'd like to mount this drive, copy everything off it, and then decommission it. But I can't seem to mount it under UD: When I click on the orange 'mount' button, it goes grey and the spinner spins for a bit, and then it goes back to orange 'mount' like nothing happened. How can I solve this problem?
  23. Well, that's weird: I typed 'powerdown -r' in the same session I started yesterday (i.e. still logged in, still in a not-root sub-directory), got the "The system is coming down NOW" message, and then... nothing. It's been something like 20 minutes, and the system is still not actually powering down. Does that suggest any other problem? What's the next step? (Since everything is still running except the WebUI, I'm not quite as frustrated or antsy as if nothing were working....)