TheFreemancer

Members
  • Posts

    116
  • Joined

  • Last visited

Everything posted by TheFreemancer

  1. It isn't? I solved it by disabling my onboard network adapter. It worked and I still don't have the interface rules. I've tried creating network-rules.cfg on /boot/config but this file is deleted at every boot. As I've seen in other threads this is a long lasting bug of unraid.
  2. Hey, I have an onboard lan interface that I believe is Intel on my Asus motherboard. I recently got a Intel 2.5gbit NIC and as far as I can see it is blinking when the cable is plugged in. Besides that I can't see it on system devices and can't select it under network settings. There are several topics here saying you need to change it under interface rules but there's nothing of sort under network settings. I'm attaching the diagnostics here to find out what's going on. tower-diagnostics-20230709-1819.zip
  3. Answering my own question XFS is faster compared to BTRFS: root@Tower:/mnt/cache# dd if=/dev/zero of=/mnt/cache/test2.img bs=3G count=1 oflag=dsync 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB, 2.0 GiB) copied, 1.59658 s, 1.3 GB/s and doing a different test: root@Tower:/mnt/cache# dd if=/dev/zero of=/mnt/cache/test.img bs=1M count=5120 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB, 5.0 GiB) copied, 2.34594 s, 2.3 GB/s Almost the same speed I was getting on windows.
  4. Sorry to revive this topic but I need to ask one more question. I have replaced my kingston nv1 snvs/1000g for a adata XPG gammix s11 Pro that I was using in another PC. The XPG is much faster compared to the Kingston, I was getting 3GB/s with it on Windows. The m.2 connection on this motherboard is PCIE 3.0 X4 so it should max out at 32gbit/s and from previews tests with the kingston I was getting 1.3GB/s if writting directly to the cache. After replacing it: root@Tower:~# dd if=/dev/zero of=/mnt/cache/INCOMPLETE/test1.img bs=3G count=1 oflag=dsync 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB, 2.0 GiB) copied, 2.32709 s, 923 MB/s Much slower. Before I try anything else, this cache drive is formated as BTRFS and I don't remember if the previews one was XFS. Should I go XFS for this drive to max out it's performance? Or file system matters little in this case?
  5. That's fine, and thanks for the info. As I use it mostly for incomplete downloads from sabnzbd and for the rclone cache, which is already limited in size, this is fine.
  6. Disk share would be the case I need better performance from another device on my LAN. That's a good info there. Mapping to /mnt/cache seems to be the answer. On Sabnzbd I've mapped to /mnt/cache/INCOMPLETE and the most performance difference I'm seeing is instead of using /mnt/user/rclone_cache is using /mnt/cache/rclone_cache/ Is there any complication that can come from using direct disk access instead of the user folder in the cache drive? I'm aware this is a problem when writting files to disks that are indeed part of the array.
  7. It is set to only. Even tried prefer. As I understand this only changes how the mover will treat the folder. I want it to be outside of the array but still on the cache drive so I don't have to buy another NVME SSD just for this.
  8. I replaced my 240GB SATA SSD with a 1TB M.2 NVME drive and I use it as cache drive. This cache drive is used for appdata, system, isos, VM img, docker img, all good part of the unraid system. But I also used it for partial downloads (incomplete folder) and for rclone cache. Now here's the problem: root@Tower:/tmp# dd if=/dev/zero of=/mnt/user/INCOMPLETE/test1.img bs=3G count=1 oflag=dsync 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB, 2.0 GiB) copied, 4.36276 s, 492 MB/s and if it's outside of the array: root@Tower:/tmp# dd if=/dev/zero of=/mnt/cache/INCOMPLETE/test1.img bs=3G count=1 oflag=dsync 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB, 2.0 GiB) copied, 1.68525 s, 1.3 GB/s How can I still have the INCOMPLETE folder but don't have it inside the array?
  9. I've been reading the cache and cache pool FAQ but I still have some doubts and really would like some advice for my scenario. Right now I have a 240gb SSD sata drive as cache and a 2TB as unsigned device outside of the array. I don't use mover and only my appdata is on my cache drive. What I use my cache drive is for partial usenet downloads (incomplete folder) and I set on my unsigned device the complete folder. Usenet requires large unpaking and now that I'm getting a gigabit internet I want to improve my download speeds and specially unrar speed on completed downloads. I'm considering add a ssd nvme m.2 500gb drive and set it as cache. My question is, if I add it as cache pool the size missmatch will be a problem, right? If using raid0? Also this wouldn't be ideal because it would download on both and unpack on both. So, would be best to leave the 240gb as a complete download drive, and leave it as unsgined device and partial download on the new ssd nvme 500gb drive as a cache drive? And one final question, if appdata is not in any drive of the array, only on cache disk, if the cache disk dies, all data is gone, right? So, the best way to back it up, excluding the backup plugin and storing elsewhere, would be creating a script to copy it's content to the array every 24 hours, right? So if the drive dies, you just add another drive, set as cache and copy from the array to the cache drive. Does it sound as a good alternative?
  10. So far so good. If the drive indeed fails, I can get another one and start rebuilding again, right?
  11. Ok It's rebuilding now. Thanks for the help, hopefully everything goes well.
  12. How do I do it? When rebooting the server I can assign the disk to the same slot but it is still disabled. Do I have to start it once with the slot disk set to none, reboot and assign the disk to that same slot again? Also when I set the disk4 slot to none the drive shows up as unsassigned device. Can the unassigned devices plugin do any harm to the files?
  13. tower-smart-20220915-1037.zip tower-diagnostics-20220915-1039.zip I've rebooted the server and the drive wasn't showing up. I replaced the SATA cable and it showed up again but good 15 UDMC errors, I remember this drive had UDMC errors before. The drive is showing up again but still disabled. There's an option I never seen before "Read-check", I'm starting it as I don't think it will hurt, if I shouldn't do it I'll stop it. EDIT: I remember something similar when a drive got disabled and the solution was to rebuild on top of that particular drive. But this is dangerous because if it starts to rebuild and the drive actually fails, all data is gone if I remember correctly. Tbh, I don't remember how to do this and I'm not sure if this is the right thing to do.
  14. This happened to me today, also running 6.10.3. I'll reboot my server and see if it come back online again.
  15. Just now I received a pushbullet notification for an error with a particular drive. I haven't done anything, didn't reboot nothing as I'm coming here to ask what should I do and since some logs disappear after I reboot I've done nothing so far. Here's the log I got: Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] 4096-byte physical blocks Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] Write Protect is off Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 1 15:05:44 Tower kernel: sdf: sdf1 Sep 1 15:05:44 Tower kernel: sd 5:0:0:0: [sdf] Attached SCSI disk Sep 1 15:06:15 Tower emhttpd: ST8000DM004-2CX188_ZCT128DJ (sdf) 512 15628053168 Sep 1 15:06:15 Tower kernel: mdcmd (5): import 4 sdf 64 7814026532 0 ST8000DM004-2CX188_ZCT128DJ Sep 1 15:06:15 Tower kernel: md: import disk4: (sdf) ST8000DM004-2CX188_ZCT128DJ size: 7814026532 Sep 1 15:06:15 Tower emhttpd: read SMART /dev/sdf Sep 1 15:10:02 Tower emhttpd: shcmd (259): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:18:47 Tower emhttpd: shcmd (8734): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:18 Tower emhttpd: shcmd (8772): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:24 Tower emhttpd: shcmd (8789): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:28 Tower emhttpd: shcmd (8810): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:36 Tower emhttpd: shcmd (8840): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:36 Tower emhttpd: spinning down /dev/sdf Sep 4 13:19:42 Tower emhttpd: shcmd (8876): echo 128 > /sys/block/sdf/queue/nr_requests Sep 4 13:19:51 Tower emhttpd: shcmd (8924): echo 128 > /sys/block/sdf/queue/nr_requests Sep 7 09:28:49 Tower emhttpd: read SMART /dev/sdf Sep 7 18:28:50 Tower emhttpd: spinning down /dev/sdf Sep 10 09:57:19 Tower emhttpd: read SMART /dev/sdf Sep 10 20:47:15 Tower emhttpd: spinning down /dev/sdf Sep 12 10:44:08 Tower emhttpd: read SMART /dev/sdf Sep 13 03:43:08 Tower emhttpd: spinning down /dev/sdf Sep 13 11:16:35 Tower emhttpd: read SMART /dev/sdf Sep 13 20:17:37 Tower emhttpd: spinning down /dev/sdf Sep 14 11:15:44 Tower emhttpd: read SMART /dev/sdf Sep 14 19:18:15 Tower kernel: sd 5:0:0:0: [sdf] Synchronizing SCSI cache Sep 14 19:18:49 Tower kernel: sd 5:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Sep 14 19:18:49 Tower kernel: sd 5:0:0:0: [sdf] Stopping disk Sep 14 19:18:49 Tower kernel: sd 5:0:0:0: [sdf] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Is the drive dead? Replace? I can't access any SMART data because the drive is offline. Drive is connected using SATA, as I've googled some questions with this error on the forum and it was related to USB. So, what do I do?
  16. I do have a cache ssd (240gb) but that's for downloading only. When I transfer files to the array those surpass 240gb very easily and even a 1TB cache would be filled in a day in some cases. So no mover here. My workaround is have an unassigned device with a 4TB drive that I work and when it's done move to the array. But sometimes I need a file that's on the array and have the spin the drive up, work on unassigned, drive spin down during the nighttime and in the morning, spin up again. So, just a few more options would help.
  17. I believe this is easy to implement but not sure if many people would use it. Sometimes I work on something on my NAS, go to bed, eat breakfest and start working again. Part of my work is in a drive I use a lot, some are not but I can use it in the middle of the morning and this routine isn't very fixed. So, to me a 12h, 16 and 24h inactivity spindown option would be awesome because it would spin down the drives when I'm off for the weekend. Or if I don't need that content so often. The 9 hour limit, to me, causes more spin downs and ups than I would like, so I'm leaving my drives 24/7 spinning. Can we get those options or a custom menu?
  18. So, I'm not exactly a dev but I just tested it this does work. The problem, when DSD is sent as x-dsd many renderers like Jriver, BubbleUPnP, USB Audio Player, even receivers that should support DSD properly over DLNA are actually receiving PCM 352Mhz instead of 2.8Mhz. I forked somebody's copy of MiniDLNA (since the original source isn't on github) and made the changes here: https://github.com/fandangos/minidlna/commit/0f402a51120ca19d15d70291ae3d9cd629d76062 I tested it inside Unraid but since I compiled it on Ubuntu it required a lot of dependencies. After copying all to binhex-MiniDLNA docker container alongside my compiled binary - deps went to /usr/lib - binary went to /usb/sbin/minidlnad I can say it worked as it should I created a snapshot from binhex-minidlna container on my server but this resulted in a 1.5GB tar file and this isn't pratical to share. So, if anyone knows how to build a docker image I can share here for anyone interested in pure DSD playback.
  19. Hey Binhex, do you have a guide of how I could compile this from source?
  20. Quick question, can you buy just the enclousure of the Storinator? My system is ready with all the drives, mobo, sas card etc.. I would like to have a more elegant solution that is easy to add or remove drives.
  21. I don't. I actually keep the unraid tab open and look at it a few times a day since I work from my PC.
  22. One of those is WD. I don't see 200, only 199. 1 is Raw read error rate which is zero. and 199 which is UDMA CRC error count that is 5 and this happened when I swapped the sata cable. This value is like that for a few months now.
  23. Hey big hard drives are not cheap in my country so I'm having a good chance that a friend is bringing me one from Europe. So, my array is: Parity 1x 16TB Data: 5x 8TB 2 of those 8TB already shows Reported uncorrect 4 and another one 8 but doing a SMART extended self-test completes without error. So, basically I have 3 questions: 1. Should I replace one of those 8TB with a 16TB one or can I just add the 16TB into the array for more space? 2. IF one of those drives die, and let's say I have 10TB free on this 16TB one. Can I recover the data into this disk and just remove the old drive from the array? Or is this a bad pratice? 3. I think this is correct to assume but, it's ok to replace a 8TB with a 16TB one, as long as it is smaller than the parity drive. Correct?