SickPup404

Good morning, I currently have an array with 12 data drives and want to remove the 8 smallest ones. They do not have any data on them right now except for the XFS overhead (0 objects/directories/files). I am following along with the remove drives and rebuild parity method and had a question. At what point in the procedure do you shut down the server and physically remove the drives? Somewhere in the middle, or AFTER the parity rebuild in step 9? TIA!

Good morning! Just had another question come to mind in regards to cache pool configuration. I have two WD SN770 1TB NVMe drives and two (or three) Kingston A400 240GB SSD drives that I planned on using for cache. I plan on having the server running Plex, four Minecraft servers, and a handful of other containers (MakeMKV, MKVToolnix, etc). I was watching one of Space Invader One's YT videos (https://www.youtube.com/watch?v=jgRSr7yBZfs) for cache pool ideas. He had four cache pools defined. He used one NVMe drive for Docker containers, one NVMe for VMs, a single SSD for download and array share write cache, and a mirrored pair of spindle HDDs for array share write caching on critical data. Do you think that video is recent enough (3 years old) for valid suggestions in my use case? How would you configure cache? Thanks again for replies and suggestions!

The one that power cycles behaves fine in a USB dock on a Windows box, passing all the Seatools tests. It's just when in the UR box that it keeps power cycling constantly and flooding SysLog with the events. My end goal is to retire my two WD EX4100's which currently have 4x WD Red 6TB and 4x IronWolf 8TB (which would then be replacing the smaller capacity drives in the UR box). These drives currently installed in UR are just going to be there long enough to start migrating all the data from the EX4100's. New breakout cables should be here today, so I'll give them a shot. If I've still got the same issues with #1 & #2, I think I'll remove them as well and just use a cold spare 8TB that I was holding on for the EX4100 array. Thanks for the comments and expertise!

Good morning, UnRaID n00b here and just getting my first server up and running. Taking it slow and want to make sure everything is good to go. I'm using a bunch of my older drives to be data drives and have been running preclears in UR and Seagate/WD tools via a Windows box to try to find bad ones before bringing them online. Most are good to go. I had one (WD Green 3TB) that I pulled out due to failed preclear and failed extended SMART tests. Now I have these four and am looking for suggestions: 1. IronWolf 8TB - Floods SysLog with power cycle messages when hooked up. Seatools on Windows passes extended SMART, and also doesn't power cycle. 2. WD Red 5TB - Passes preclear and extended SMART tests in UR and Windows. When first booted a couple days ago, it had Reallocated Sector Count of 26, now at 28. 3. IronWolf 8TB - Passes preclear and extended SMART tests in UR and Windows. When first booted a couple days ago, it had UDMA CRC error count of 1. No change. 4. WD Green 3TB - Passes preclear and extended SMART tests in UR and Windows. When first booted a couple days ago, it had UDMA CRC error count of 627. No change. I "think" what I should do: 1. Try different port on 8087 breakout or swap cable out. I'm waiting on a spare now. 2. Clear messages. Ok to use, but monitor for changes. (This is one I'm not sure about.) 3. Clear messages. Ok to use, but monitor for changes. 4. Clear messages. Ok to use, but monitor for changes. Just in case it's needed, diagnostics are attached, and server specs in Part Picker link. Thanks very much! My server: https://pcpartpicker.com/list/QGTBjn nasbox-u1-diagnostics-20241219-0819.zip

Just an update. Now that most of the clears are done (16TB still running) and I removed the drive that was flooding the SysLog, the web GUI is responsive and unassigned drives isn't having any response issues. I was able to change the tunable polling attributes rate with no problem, as well as date/time settings. I think this can be resolved and marked as a n00b issue doing 13 simultaneous preclears....

Thank you both for your replies!

So, in the Unassigned Disk Devices list screenshot below, this is a drive that I've cleared. What are the black check, "1", log, and pencil icons for? None are active/clickable/hoverable. thanks!

Looked over the SysLog and looks like I have a drive flooding it with messages. Going to wait for another two drives to finish their post read, shut down, and re seat cables to try to clear that message. [EDIT] So far, pre-clear succeeded on 5/6 of the WD Greens, failed on one of them, and I aborted it on the one flooding SysLog.

Another update - I just noticed the Time Zone and NTP Server changes from last night actually were applied... Apparently clearing that many drives puts a bit of a strain on resources for updates. I think I'm just going to let them finish and see how things are then.

Good morning, Diagnostics attached. I was going to wait until the clears/zeroing completed, but that may be a while longer. (Status bar is showing I've got some in post-read, some zeroing, some still in pre-read, and one error drive.) Thanks very much for the quick reply last night! (Apologies since I started the thread and then bailed to watch some TV with the wife.) [EDIT] Wonder if I'm just asking it to do a lot with zeroing 13 drives simultaneously? nasbox-u1-diagnostics-20241216-0806.zip

Hi, A new lifetime user and setting up my first server. I've got a few questions/issues so far. - I can't set the time zone or NTP servers in Settings...Date and Time. I change the TZ to UTC-5 Eastern US, add pool.ntp.org to the list of NTP servers, and click Apply, then they are reset back to UTC-8 Pacific US and time.google.com. - The Unassigned Devices Plus app (in destructive mode) can't see any of the drives most of the time - it returns "Timeout: Failed to get unassigned devices information - check the syslog." I managed to get Clears running on all the drives one time, but this was happening before the Clears were running. - The server has been running about 3-4 hours so far and the web GUI has gone unresponsive 4-5 times and gets an http refused connection. (I've got a static IP assigned in the server, and the router. Any ideas? I've searched both the forums and Google and the solutions/ideas I've found haven't helped. Server specs: Gigabyte B760M DS3H AC DDR4 motherboard Intel Core i5-12600K CPU Corsair Vengeance LPX DDR4 32GB (2x16GB) RAM Corsair 750D Tower Thermaltake Toughpower XT 875W PSU LSI 9207-8i in IT mode (x2) HBA (below drives are all unassigned right now, pending clears; all the storage drives were previously used and had old data on them) WD SN770 1TB (x2 for cache) Seagate Exos ST16000 (x2 for parity) Seagate IronWolf ST8000 (x3) WD Red WD50EFRX (x3) WD Green WD30EZRX (x6)