Everything posted by Shu
-
BTRFS error on NVME Cache drive
Hi Everyone, I woke up this morning to these errors on my nvme cache drive (my cache pool is two drives, one m.2 nvme and the other a sata ssd): Aug 31 03:51:39 520unraid kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=10 block=820606861312 slot=118, unexpected item end, have 3543154555 expect 16251 Aug 31 03:51:39 520unraid kernel: BTRFS info (device nvme0n1p1): leaf 820606861312 gen 46836 total ptrs 258 free space 9769 owner 10 Aug 31 03:51:39 520unraid kernel: BTRFS error (device nvme0n1p1): block=820606861312 write time tree block corruption detected Aug 31 03:51:39 520unraid kernel: BTRFS: error (device nvme0n1p1) in btrfs_commit_transaction:2438: errno=-5 IO failure (Error while writing out transaction) Aug 31 03:51:39 520unraid kernel: BTRFS info (device nvme0n1p1): forced readonly Aug 31 03:51:39 520unraid kernel: BTRFS warning (device nvme0n1p1): Skipping commit of aborted transaction. Aug 31 03:51:39 520unraid kernel: BTRFS: error (device nvme0n1p1) in cleanup_transaction:2011: errno=-5 IO failure I also attached 3 screenshots (0 being the disk info, 1 & 2 being syslog relevant to this issue (a lot of item xxx key ... itemoff... errors)). While researching this issue, I ran a Check-File System for this drive but it came back clean (picture 3) and a Scrub check which also came back clean (picture 4). I do believe something is wrong however, because I when I ran the mover, it came back with a Read-Only filesystem error on all files (they're mostly media files from qBit from last night so not much unrecoverable, I believe - though, I haven't checked for files that are kept on the cache pool...which are probably more vital...) What is the proper guidance here? (Or which guide/thread should I try next?) Edit 9:56am local: I re-ran the mover and it does appear to be moving files albeit at a slow pace (~25mb/s per drive, so ~50mb/s for the pool). I would expect much faster reads for these fast drives (they are writing to a 4tb wd blue which is less than half full, I'd expect at least a starting speed around 120mb/s)
-
[Support] binhex - rTorrentVPN
I've been coming into a problem that I'm not sure how to fix. When editing the rtorrent.rc config file (using notepad++), I get this error: [18.08.2022 10:41:00] WebUI started. [18.08.2022 10:41:02] Bad response from server: (0 [error,getplugins]) [18.08.2022 10:41:12] JS error: [http://192.168.1.3:9080/js/stable.js : 1784] Uncaught TypeError: Cannot read properties of undefined (reading 'scrollTop') For the latest attempt, the only thing I changed was: directory.default.set = /data/incomplete/ To this: directory.default.set = /data/Plex_Downloads/ Changing back to incomplete didn't fix the issue (and Plex_Downloads is a folder in the mapped /data/ directory, I'm fairly certain). When I was trying this last night, the above change didn't throw an error but it did when I changed # Global upload and download rate in KiB. "0" for unlimited. # #throttle.global_down.max_rate.set_kb = 0 #throttle.global_up.max_rate.set_kb = 0 to this: # Global upload and download rate in KiB. "0" for unlimited. # #throttle.global_down.max_rate.set_kb = 0 throttle.global_up.max_rate.set_kb = 900 Any ideas? Thanks!
-
[Support] binhex - Radarr
That worked; thanks! Next time, I'll read through the entire faq before posting haha
-
[Support] binhex - Radarr
-
[Support] binhex - Radarr
Hello, I am having trouble connecting to qBit as a download client in Radarr (or any other arr, for that matter). I have radarr running in unraid and it's being routed through binhex-delugevpn (this setup is all working correctly, as far as I can tell). I have qBit running on a separate windows machine with it's internet traffic running behind NordVPN (the machine is solely used for qBit). Both are connected to my LAN via ethernet. I can access qBit's WebUI on my browser through the IP:Port (192.168.1.4:8080) just fine and login with my username as password but when I test the connection in Radarr, I get an "Unable to connect to qBittorrent" error. I am not using SSL if that info helps. I attached what I think are the relevant logs as a .txt. Unraid_qBit_Error.txt
-
[Support] binhex - DelugeVPN
That worked! Thank you so much
-
[Support] binhex - DelugeVPN
I changed from UDP to TCP. For Key 13, do I need to put "9696" or "9696/tcp"? Okay, so I tried setting Prowlarr's WebUI value to a few different things but none of them worked... "http://localhost:9696" - "localhost refused to connect" "http://localhost:[PORT:9696]" - "about:blank#blocked" "http://[localhost]:[PORT:9696]" - "about:blank#blocked" Or when I just type in my servers IP plus the port in my browser's URL ("http://192.168.1.3:9696/"), I get a "took too long to respond" error.
-
[Support] binhex - DelugeVPN
-
[Support] binhex - DelugeVPN
Here's the docker run command. I found the same issue with other VPN containers (OpenVPN) and with trying to route other apps (Firefox) - the WebUI works when the net is bridged but doesn't work when routed through the VPN docker. Here is docker run for prowlarr Here is docker run for binhex-delugeVPN
-
[Support] binhex - DelugeVPN
Ah, okay; I see now that Q25 meant LocalHost in the url of the browser, not in a specific setting of the docker (although, I could just set the WebUI setting in the docker to be "http://localhost:[PORT:9696]/", right?) However, this still doesn't seem to work? Should I be able to use "localhost:9696" from any browser url on my LAN? It currently says "Localhost refused to connect" When I change the dockers WebUI value to "http://localhost:[PORT:9696]/" and try to open it, I get the same "about:blank#blocked" error. (same for "http://[localhost]:[PORT:9696]" and "http://[localhost]:[PORT:9696]/" When I change it to "http://localhost:9696" and try to open it, I get the "localhost refused to connect" error
-
[Support] binhex - DelugeVPN
Hello. Unfortunately, I am another poor soul who is having issue accessing their "arr" (Prowlarr in this case) WebGUI after having routed it through DelugeVPN. My specific issue is when I try to open the WebGui, I get "about:blank#blocked" instead. I believe the docker is being routed properly as I can use prowlarr's console to "curl ipconfig.io" and I get the same, VPN-ed IP Address as DelugeVPN. This issue is consistent from two different PCs (on chrome), it happens on my iPhone on wifi (using Brave/chromium), and on my Pixel (using chrome on wifi and on cellular). I followed BMB's video and SIO's video as well as making sure to follow Q24 and Q25* from this FAQ (although, I didn't really understand what this portion meant: In DelugeVPN, I have: VPN enabled (I use NordVPN) my username/password enable_privoxy: yes LAN_NETWORK: 192.168.1.0/24 VPN_INPUT_Ports: 9696 (this is what Prowlarr uses) as well as an added port with container port and host port being 9696 (UDP) (and adding in NordVPN's ovpn file into the app data openvpn folder). In Prowlarr, I set: Network Type: None extra parameters: --net=container:binhex-delugevpn And I deleted the port 9696 setting. I'm not sure if my issue is a missed setting, something with Q25 that I didn't understand, or something else entirely. Any help would be very much appreciated. Thanks!
-
Unraid slows to a crawl
(had an internet outage today but) I just updated the firmware! Have never done that before, exciting and nerve-wracking haha. I will monitor for the issue again My PSU came with two 3-port sata cables (enough for 6 devices in total). I attached one 4-port splitter to each native sata cable (so each now supports 6) for a total of 12 across both. My PSU also has one cable that is PSU > SATA - Molex - Molex - FDD (floppy disk?). I suppose I could try the two Molex to two Molex>dual SATA splitter? That would give me 4 but still not enough... Is there a better and just completely different way people power their drives?
-
Unraid slows to a crawl
Darn...I'm using a Corsair 550W power supply that is not modular. Do you know of a good way to power more drives than I have ports for? I'm sure I have enough power (only have the CPU in there and an old AMD gpu (pci power only)).
-
Unraid slows to a crawl
I do use the HBA which goes from SAS to 4 SATA. On top of that, I have this SATA power extender Can I ask where in the diagnostic you found what firmware I'm running. Also, all I can seem to find on Broadcom's website is info for the SAS 9200-8e HBA (whereas I purchased an 8i on ebay years ago). When looking at my ebay invoice, the item's title reads "Genuine LSI 6Gbps SAS HBA LSI 9200-8i = (9211-8I) IT Mode ZFS FreeNAS unRAID US". I *did* find firmware for the 9211-8i. Do you have a better sense for which I should use? Thanks!
-
Unraid slows to a crawl
520unraid-diagnostics-20220810-0123.zip
-
Unraid slows to a crawl
I was monitoring a parity check run just now when I found the webGUI to be extremely slow (to the point that tabs wouldn't load even when given 5+ minutes). I looked into the log and saw this snippet repeated over and over and over again: Aug 3 22:28:04 520unraid kernel: sd 10:0:5:0: Power-on or device reset occurred Aug 3 22:28:05 520unraid kernel: sd 10:0:5:0: Power-on or device reset occurred Aug 3 23:51:09 520unraid kernel: sd 10:0:6:0: attempting task abort!scmd(0x00000000dacc87bb), outstanding for 60050 ms & timeout 60000 ms Aug 3 23:51:09 520unraid kernel: sd 10:0:6:0: [sdh] tag#2298 CDB: opcode=0x12 12 00 00 00 24 00 Aug 3 23:51:09 520unraid kernel: scsi target10:0:6: handle(0x0010), sas_address(0x4433221106000000), phy(6) Aug 3 23:51:09 520unraid kernel: scsi target10:0:6: enclosure logical id(0x500605b0055806c0), slot(1) Aug 3 23:51:10 520unraid kernel: sd 10:0:6:0: task abort: SUCCESS scmd(0x00000000dacc87bb) Aug 3 23:51:10 520unraid kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Aug 3 23:51:10 520unraid kernel: sd 10:0:6:0: Power-on or device reset occurred Aug 3 23:51:10 520unraid kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Aug 3 23:51:10 520unraid kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Aug 3 23:51:10 520unraid kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Aug 3 23:51:10 520unraid kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Aug 3 23:51:11 520unraid kernel: sd 10:0:6:0: Power-on or device reset occurred Aug 4 00:14:54 520unraid kernel: sd 10:0:6:0: attempting task abort!scmd(0x000000006c97dd1d), outstanding for 60132 ms & timeout 60000 ms Aug 4 00:14:54 520unraid kernel: sd 10:0:6:0: [sdh] tag#2306 CDB: opcode=0x12 12 00 00 00 24 00 Aug 4 00:14:54 520unraid kernel: scsi target10:0:6: handle(0x0010), sas_address(0x4433221106000000), phy(6) Aug 4 00:14:54 520unraid kernel: scsi target10:0:6: enclosure logical id(0x500605b0055806c0), slot(1) Aug 4 00:14:55 520unraid kernel: sd 10:0:6:0: task abort: SUCCESS scmd(0x000000006c97dd1d) Aug 4 00:14:55 520unraid kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Aug 4 00:14:55 520unraid kernel: sd 10:0:6:0: Power-on or device reset occurred Aug 4 00:14:56 520unraid kernel: sd 10:0:6:0: Power-on or device reset occurred I attached a syslog file here (note: above, it says Aug 4th but I only found out about it today, Aug 10th. Am just realizing now that it apparently has been going on for a while...) If it helps, I am using this HBA: https://www.ebay.com/itm/123916887273 syslog (3)
-
Parity Check doesn't seem to be reading from all disks
I'm doing a parity check right now and two of my disks (the smallest and least full) don't seem to be getting read. Is that normal? Edit 1: Actually, I think it's probably because of where I'm at in the parity check? "Current Position: 1.88TB" That's probably it; sorry, I missed that when I first posted.
-
User share only filling one disk - split level issue?
Update: I have since finished using rsync and I now run the server headless. Haven't seen an issue yet (but am only at 10 hours uptime for now). One thing odd I noticed was that as I was using rsync, my main pc (from where I ran the CLI), my gpu memory would go up. LIkely a correlation and not causation but I didn't have time to test.
-
User share only filling one disk - split level issue?
No, nor any docker containers. I am still trying to transfer all my data so I haven't had the opportunity to set anything up yet Edit: If it helps, it happened again earlier today (before I did the memtest). Here are those logs (happens near 13:59:30) syslog (2)
-
User share only filling one disk - split level issue?
Memtest86 passed (4 runs, about 3 hours) zero errors. Can I ask what you mean by "limit resources"?
-
User share only filling one disk - split level issue?
When I boot my server, I select Memtest86+ but it doesn't seem to be working? Computer reboots and i get taken back to automatic boot screen. Not sure why Edit: Seems like something with UFEI vs Legacy boot? Will need to research this more (not really sure I understand the difference btwn the two) Edit 2: I made a bootable USB for memtest86. Its running now. Are there any settings or specific tests to run or just the default?
-
Help understanding Memory Widget
Can someone help explain what these are percentages of? I assume overall utilization is the white box (added). Is Flash/Log/Docker the percent of the 12%? Are those all separate and the overall utilization is the summation of the four? I couldn't find an answer in the manual Thanks!
-
User share only filling one disk - split level issue?
Okay, it crashed again last night. I attached the syslogs here. I do notice an Out of Memory error starting at 01:52:48 with the last entry being at 02:20:51. My server hardware is: Ryzen 5 3600 MSI x570-a pro 16gb ddr4 ram I do have a gpu but it's a very old one that I used just for video output when I was on windows (not sure if that's needed with unraid) LSI HBA syslog
-
User share only filling one disk - split level issue?
Turned it on and will report back if (when) it crashes again. Thanks!
-
User share only filling one disk - split level issue?
I'm moving files from an unassigned disk to a share (not any particular disk). The command I am using is: rsync -a -H -v --remove-source-files --progress "/mnt/disks/06_WD_Red_NAS_3tb/[main folder]/" "/mnt/user/[share name]/" (The parts in the brackets are shortened for laziness.) I am experiencing some crashes/freezes from time to time; not sure why. My unraid computer will still be on but the webGUI inaccessible. (When I plug a monitor directly, firefox opens but "localhost" never loads. (This info isn't necessarily relevant to the rsync topic, though; I don't think).