• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Stubbs's Achievements


Apprentice (3/14)



  1. Can someone tell me how I'm supposed to disable this annoying error? Usually it's meant to be infrequent and occurs maybe once a day. Now I'm seeing it all the time, constantly. From what I understand, it's a bug with Crucial SSDs and not actually a real problem. The real problem is the stupid error messages they keep producing. For the record, I attached an extended SMART test.
  2. Can it be smaller? What if I wanted to replace a 10TB drive with an 8TB drive?
  3. Also, does the replacement drive have to be the exact same size as the failed drive? Or can it be any size above the used space?
  4. I made probably my biggest, most costly mistake recently. I was upgrading my case to cool my drives better, but when re-connecting the HDD power connectors, I got my modular cables mixed up (they look exactly the same) and I ended up using cables from a Thermaltake 600W Gold PSU when my server uses a Seasonic 550W Gold PSU. Initially, the server wouldn't even power on (the fans would flicker once but that's it). I eventually figured out the cables were the problem, and I've since been told what I did was extremely dangerous for my hard drives and could easily brick one. Sure enough, one of them did brick, but the rest are fine. My question is, with the presumably irregular voltage they were taking in, will that likely have any long-term effects on the drives? Are they now more likely to fail in the future or have some kind of data loss? The still seem to be functioning normally now and I haven't noticed any data loss.
  5. I currently have 30TB of storage and it shows in my array page. But my Rootshare on Windows shows 27.2TB. Does anyone know what might be causing this? I recently removed a 3TB drive from my array using this method: Could that have something to do with it?
  6. Is it possible for a molex connector to not deliver enough power to an HDD? I recently upgraded my server from 3TB WD Reds to 10TB Seagate Ironwolfs, and the Ironwolfs kept returning errors in my server. Sometimes I'd get the parity sync working, but it would work at about 800kbps which would've taken about a year to finish. I fixed it by taking the Seagates out of the Hotswap Bay and into the case's internal 3.5" bay, and connecting them directly to both the motherboard (SATA) and the PSU (SATA Power connector). My Hotswap Bay has two SATA power connectors, and one of them is powered by a Molex connector (because that's all I could fit). Could a Molex cause a power bottleneck for higher capacity drives?
  7. If I wanted this container and the Rclone Nacho GUI container to use the same rclone.conf file, what should I be doing? For the Rclone-Browser container, the path looks like this: /appdata/Rclone-Browser/xdg/config/rclone/rclone.conf For the Nacho-Rclone-Native-GUI container, the path is just /appdata/rclone/rclone.conf
  8. I want to power down my Disk 1 because it keeps running hot and I'm not upgrading my case for at least a month. The problem is it keeps making small reads every 7-8 seconds and I don't understand why. Even when nothing should be using it, it's still making reads. I assume it's maybe some kind of background check in a docker application, in which case, how can I tell which container is making these reads?
  9. I'm inclined to post an issue here because it's a problem that occurs across every single docker container that enables audio streaming (Jellyfin, Navidrome, Gonic, Airsonic, all of them). I can stream video just fine. But when I try to stream a simple mp3 file, I get a message saying Playback Error This client isn't compatible with the media and the server isn't sending a compatible media format. In the Jellyfin logs, it says: [16:57:08] [ERR] [61] Jellyfin.Server.Middleware.ExceptionMiddleware: Error processing request: Could not find file '/music/Edwyn Collins - A Girl Like You.mp3'. URL GET /Audio/e2d30d0adc1e2d5c82d8247f7f4ec72f/universal. And a similar error is produced by all the other music streaming containers. I can tell you for a 100% fact that the folders are mapped correctly. They are showing up in Jellyfin/Navidrome just fine, they're just not playing on any device or browser. What is going on? Why is Unraid having such a hard time streaming audio?
  10. [edit] Don't worry about it. Restarting the server fixed it, and I probably should've done that before freaking out with this thread. Can someone please help? I tried moving a file using the dynamic file manager plugin, it produced a weird error and as a result my entire user folder got purged. All the data still seems to my on the disks, but my server is currently completely non functional. Please help.
  11. In Disk Settings, we have the option to change the "Default Spin Down Delay" to spin hard disks down after a set period of time. But this setting applies for all hard disks connected to the Unraid server. If I wanted this setting to only apply for two specific disks, what should I be doing? Would it require some kind of user script? Also, separate question, but is spinning down generally not encouraged? I see a lot of conflicting information on this subject. Some people say having disks in a spun-down state increases their lifespan, while others day it can degrade the disk quicker because the spin-up is the most likely action to physically break the drive.
  12. The frustration continues. First, I tried connecting the Seagate to SATA_1. This was the port my cache drive was connected to. I connected the Seagate to it WITH the cache drive's cable. Same errors (1st FIS failed) (hard resetting link), along with 150KB/s parity rebuild. Diagnostics attached (sixth attempt). Then I reverted back to the exact same configuration where the parity build appeared to be working. Seagate connected to SATA_2 on the motherboard with its original cable, and I brought back the old orange SATA cable to connect the data drive to SATA_4. I powered the server back on, and it wouldn't even start the rebuild. The parity disk (seagate) was stuck in a disabled state. Stopped and started the array, and it was still disabled. Diagnostics attached (seventh) (disabled). Finally, I tried a different cable and a different port again, this time SATA_5. I powered the server back on, and initially it started rebuilding just fine at 90MB/s. But after about 30 seconds, the same errors shows up again. Oct 1 08:42:59 Tower kernel: ata9: softreset failed (1st FIS failed) Oct 1 08:43:05 Tower kernel: ata9: found unknown device (class 0) Oct 1 08:43:06 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 1 08:43:06 Tower kernel: ata9.00: configured for UDMA/133 Oct 1 08:43:06 Tower kernel: ata9.00: exception Emask 0x10 SAct 0x60000000 SErr 0x90202 action 0xe frozen Oct 1 08:43:06 Tower kernel: ata9.00: failed command: WRITE FPDMA QUEUED Oct 1 08:43:06 Tower kernel: ata9.00: cmd 61/c8:f0:c8:c5:14/00:00:00:00:00/40 tag 30 ncq dma 102400 out Oct 1 08:43:06 Tower kernel: res 40/00:e8:88:c0:14/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Oct 1 08:43:06 Tower kernel: ata9.00: status: { DRDY } Oct 1 08:43:06 Tower kernel: ata9: hard resetting link And the parity build got slower and slower. 90MB/s to 30MB/s to 13MB/s and so on, so I cancelled it. Diagnostics attached (eighth attempt). (eighth) (seventh) (disabled) (sixth)
  13. I agree, which is why I'm going to keep trying to get it working the next chance I get (I can't power it off right now). I'm hoping if I can get parity built, the storage drives will be less trouble. I have an HBA Card but I really don't want to install it yet. The only PCIe x16 slot is currently occupied by a NIC, which I use for a virtualized router. I'm really not keen on using a backup router without all my firewall stuff set up. This is the main reason I'm going to buy a new motherboard on black friday/cyber monday.
  14. Unfortunately no. The 4th attempt was the first time the parity check actually started running, but it was at 300K/Bs and errors kept repeating in the log. I shut down the server, plugged the Seagate into SATA port 2 with it's original cable, powered the server on, and parity started building properly. I didn't save a diagnostics file because I thought the problem was gone. I cancelled the parity build and shut down the server again (the case was open and laying on the floor). The only other thing I did was swap out the SATA4 cableto a newer cable. This was connected to a data drive and was unrelated to the Seagate. (fifth) is the most recent diagnostics. Exact same cable and port for the Seagate when the parity build worked. For some reason it went back to this: