strike

Sorry, my bad. You need the unraid connect plugin. I thought I remembered something about it being included in the OS in one of the latest versions, but I think that was for a future version. But the unraid connect plugin features a new notification system. It was released in February.

Sounds like a plan. Don't know what the clicking sound could be. If the smart looks good, maybe just do a smart test, then if good, just put the original disk9 back. But either way, both drives still have to be rebuilt.

You need to start the array in normal operation to be able to see the emulated drives. But since disk9 is replacement drive a rebuild will start once you start the array with it assaigned. So to be able to verify the data on the emaulated drives you should unassign disk9 and 10 and start the array. You should then be able to see both disk9 and 10 emulated. Verify the data is correct, then you need to stop the array and reassign disk10 to start the rebuild on that drive first (since you have the old disk9, disk10 is more important.) . You could rebuild both at the same time since you have dual parity, but I would do one at the time to be safe.

You must be on an old unraid version, try updating once in a while, then maybe you get to see and use new features :)

Ah ok. Sound like you didn't start the rebuild then. Anyway, go over the cables again when you start tomorrow and finish checking the filesystem.

And disk4 has a very high crc error count so proably also cable releated.

When you started the array with the replaced disk9 a rebuild would start. Did you cancel that? Or what happened, and what did you do? Yeah, probably best to call it a night and come back strong tomorrow.

It's been a while since I've checked the filesystem on a drive, but IIRC, you'll get an option to repair it if it needs to. Then, it'll try to do that, and you might get a lost+found directory on the root of the drive, which contains files that were not able to be determined where they should be and what they are, and they could be renamed as random filenames. When repaired, the next step is to check the emulated drive to see if all the files are there, and if they are, rebuild the drive onto itself. And of course, check for the lost+found folder first. Since your first parity drive had read errors also you have to do this one drive at a time to be safe. I've had like 12 drives unmountable at the same time once. And after checking and repairing the filesystem, then rebuilding one drive at a time, I was able to recover all data except for one season of a tv show. And since disk10 is also unmountable, it will not be rebuilt until you have fixed the filesystem on it. The only thing I'm not quite sure about is how your parity drive with read errors will impact the rebuild. Since you have two, it shouldn't matter, but I'm not 100% sure, only 80%.. So, after reconnecting all the cables, you should check the syslog for this kind of message:"error md: disk0 read error, sector=280" Disk0 is parity1. If it still appears in the log, I would wait for the resident experts like @JorgeB or someone else to comment on this before going any further, to be sure you don't lose any data by mistake.

Also looks like the drive with serial 9JG49BVT has some crc errors which usually means a bad cable connection. So check that too. It could be an old value as the crc value never resets. If it increases, maybe try to change cable.

Check filesystem on disk9 and disk10. Your first parity drive also has read errors. But first, check filesytem on disk9,10. And do NOT format any drives.

Reserved

Unraid Disk Space Management Plugin Description: This plugin was created mainly for those who use the split-level feature in Unraid. Due to how split-level works, it will ignore the minimum free space setting and continue to move stuff to disks that are full/almost full if your split-level setting permits it. This is because split-level tries to keep files and folders that belong together (based on your split-level setting) on the same disk, and split-level trumps all other settings. Even if there's little space left on the disk.So to combat this, this plugin will automatically move folders from disks that are below the threshold setting to the disk with the most free space available. It's recommended to set the cron schedule to a time when you know the mover has finished.Features:Intelligent Threshold Monitoring: Continuously monitors array disks and triggers move operations when free space falls below your defined GB threshold. Folder Priority Queue: Features a drag-and-drop interface that allows you to prioritize which directories are processed first. Per-Path Granular Sorting: You can independently configure sorting rules for every folder in your queue, including Smallest First, Alphabetical (A-Z or Z-A), Newest First, or Oldest First. Dual-Layer Disk Exclusions: Provides both global disk exclusions and folder-specific exclusions to give you precise control over where data can and cannot be moved. Interactive Path Picker: Includes a built-in visual folder browser to easily select and add new management paths directly from your Unraid array. Real-Time Status Tracking: A live dashboard badge displays whether the engine is currently "IDLE" or "RUNNING". Advanced Safety Guards: Integrated protection prevents accidental moves to or from /mnt/user and includes loop prevention logic for simulated runs. Smart DRY RUN Mode: Safely test your configuration with a full simulation that logs exactly what would happen without moving a single file. High-Performance File Transfer: Uses rsync to move data, ensuring all permissions, attributes, and hard links are perfectly preserved. Modernized Log Terminal: Features a dedicated log management tab with a high-visibility console, auto-scrolling, and the ability to clear logs directly from the UI. Automated Scheduling: Fully customizable cron scheduling to ensure management tasks run at the most convenient times for your server.

That depends on what files and directories you want to keep together. For a TV show share, you probably wanted to keep all seasons of a show on the same drive, and that's why you set your current split level. If you want to continue with the same settings, you either have to be ok with moving files manually on almost full drives. Or you can test out my new script linked earlier in this thread, and let it take care of it automatically for you. I'm working on a plugin, but that isn't quite finished yet, so for now, the script and the user script plugin will have to do. Or as @itimpi suggested, if it's not that important to you where the files go. You can relax the split level, maybe one directory up, so that individual seasons can go to different drives. Or choose the one that says split everything as needed, but then you have to be ok with files being scattered around different drives. But it also won't need any manual intervention. Keep in mind that split-level also only applies to new files and directories, so either way, you'll have to do something about it manually on your full drives. I like the split-level function, because of my mild OCD :). But I agree with you that it could have been better implemented in mover. But I suspect that is not such an easy task. I've been moving things around manually for years before it came to a point where I had to do something about it. And recently, it became too much work as it has to be done daily if I want to keep my current split levels.

I thought I made it clear what I was tired of, and it was not that. If you absolutely want to discuss my comment further, you can create a new thread so we don't spam this one. I'll happily discuss it in your new thread so you can express your opinion on the matter :), but I won't respond to it anymore in this thread.

That wasn't at all what I was saying, and you know that.

Unless you're using split level, then you always want some free space left to make room for new/upgraded files. This won't help if using split level.

So I finally had some time to work on the script, and it's now completely rewritten. I've implemented the suggestions you guys came up with. So it now features "dry run mode" (enabled by default), support for multiple movies/tv shows directories, and you can exclude one or more drives. I've updated the first post with the script and also the how it works section. I thought about making it even more efficient by checking the disk usage for each movie/show and moving the smallest first, but that would make it slower and more I/O Intensive, and I'm not sure it's worth it, especially for large libraries. Right now, the script itself is very fast (the moving, of course, takes a bit of time), and works well. I will now see if I can focus on how to turn it into a plugin.

If you want to test it further (before I have the time to implement the suggestions you guys came up with), you should pick the drive with the lowest amount of space, then set the threshold a little above that. So it doesn't continue to move a whole lot unless you want it to. And for testing purposes, just make a dummy "Movies" and "TV show" folder somewhere on a share and put a couple of movies and shows there. Just update the path in the variable definition before you run it again.

It checks available space after every successful move of a movie or tv show. But in its current form, it checks ALL drives. So, if you have more than one drive, it will continue to move until all drives are above the threshold. In your case 999GB. So, setting a lower number, what you want as free space on the drives, is what you should do. Or do you have a better suggestion on how I could handle it? So, am I assuming correctly that you have more than 1 drive in your backup server? Since it's continuing to move.. And for movies, it moves in alphabetical order.

I think it would be best to only use rsync because as I mentioned it will preserve hard links. But I'll look into it. And when I said the the mv command it's not the same as its using mover. Excluding drives and add multiple folders for tv shows should also be pretty easy to implement. The script is already excluding disks, which is unassigned drives.

Yeah, I always wanted something like this myself. It just didn't register in my brain until a few days ago that this easily scripted and I could automate it. Sure, a dry run is easy to implement. I might have to change it so it uses rsync instead of the mv command, but that is doable. I might change it to use rsync anyway as it will preserve hard links. I don't think the mv command does that when moving to other drives. I will also look into making it a plugin. It could be a great learning experience as I've never wrote a plugin before. ☺️

What I've learned over the years using UnRaid is two things: 1: You can never please everyone. Some want fewer updates, and some want more. I can almost guarantee you that there will be a post in the forums very soon, "When will unriad 8 come out?". As well as post as "ugh, another release, I'll have to reboot AGAIN".. People are different and have different needs. Unraid started as a media server software, and at its core, it remains that for most users. If you need a stable server software with updates once or twice a year for businesses or similar purposes, then maybe you don't have the right software for you. 2: There will be bugs, even in stable releases. So either take part in testing and squash bugs, or wait until there's a .5 or .6 release if you want stability. Then you don't need to reboot as often :) I'm surprised you haven't learned this yet, I know you have been here for a few years. I, for one, have nothing but praise to say about Unraid and the team behind it. And the release cycle suits my needs well. Perfect balance between new features, bug fixes, and stability. That's my opinion anyway.

Sorry, but I'm getting pretty tired of seeing such comments. The unraid team isn't that big that they can't test a new build for every single thing that may surface during beta/rc releases. They and the rest of the community (us) are dependent on users testing the betas and rc releases for bugs. While testing betas and rc releases may not be in everyone's interest, and are waiting for the rest of the community to iron out the kinks. Bugs will slip through the cracks and appear in stable releases. This is and will always be the case, forever. Even Microsoft Windows, which is used by billions of users, has bugs slipping through the cracks in stable releases, despite having millions of testers in the Windows Insider program. Therefore, I don't have sympathy for users who make such comments. Sorry for the rant, but I just couldn't bite my tongue seeing at least a couple of similar comments in this thread. Thank you for this release, and keep up the good work! :)

Edit: This script is now added as a plugin. You can find it in CA. Users are encouraged to install the plugin instead as I will no longer update the script. I'm using split level to satisfy my OCD :) And with that comes weekly maintenance of moving stuff around on drives that are almost full to free up space for new/upgraded files. Up until now, I've been doing this manually every weekend. But now, with the new Huntarr app, which constantly hunts for new files or upgrades files, moving files around suddenly became a much bigger task and has to be done daily. So I had to do something, either stop using split level and split everything as needed, or write a script that moves stuff around to drives with more space available. So I did the latter, or AI did most of the work. So now I can continue to use split level for my OCD, and never run out of space :) And I don't need to lift a finger anymore. So naturally, I'll share it with anyone who needs it. This Bash script is designed to automate the management of disk space on an Unraid server by monitoring available space on disks, moving media files from full disks to those with the most available space, and creating necessary directories as needed. This ensures that your split-level will continue to organize the files where you want them. Without running out of space. It incorporates robust logging to track actions taken and any issues encountered throughout the execution. It also has a prioritizing logic that prioritizes moving movies first (since a movie often takes less space than a full show). And if it moves shows, it will always move the show with the fewest seasons first to maximize efficiency. It also moves directly from disk to disk and thus bypasses the cache. It only focuses on the drives in the main array and does not include pools. And it assumes that each movie has its own folder, and each show has a main show folder with season subfolders. The majority of my server is dedicated to media, and thus it makes the most sense to me to move media around, as those are the files that take up the most space on my server. The script and variable definition reflect that, and note that the paths are relative, not absolute. Run it preferably after the mover has finished or whatever schedule you like. Here is the script: unraid_disk_space_management script And here is how it works in detail for those interested: How It works

Try to set a firewall rule on your router to allow port 41641 UDP on the WAN interface. If you have pfsense for example it blocks it by defeualt.