doubley
-
Posts
28 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by doubley
-
-
27 minutes ago, dlandon said:
Remove the '#' character from the mount points.
Ha, yep, that did it. Just curious - why the change?
-
33 minutes ago, dlandon said:
Are you out of memory? Post your diagnostics.
Please see the attached diagnostics. Server uptime is only about 6 hours so hopefully there isn't too much to sift through.
Memory usage is 10GB/64GB presently, and generally never exceeds 32GB/64GB.
-
Hello!
I'm encountering an issue and I'm in a bit of a pickle.
After a data drive swap in my main array and a UD plugin update, I am no longer able to mount certain drives in UD. I have a total of 10 drives in UD. 2 SSDs, 7 pre-existing HDDs, and 1 new HDD. The 2 SSDs and 1 new HDD mount fine, but the 7 pre-existing HDDs no longer mount. When attempting to mount, the log shows:
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] physical block alignment offset: 4096 Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] 4096-byte physical blocks Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Write Protect is off Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Mode Sense: 73 00 00 08 Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 6 22:08:32 Tower kernel: sdaa: sdaa1 Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Attached SCSI disk Sep 6 22:08:52 Tower emhttpd: WDC_WUH721818ALE6L4_3WKXN7LJ (sdaa) 512 35156656128 Sep 6 22:08:52 Tower emhttpd: read SMART /dev/sdaa Sep 6 22:09:56 Tower unassigned.devices: Adding disk '/dev/sdaa1'... Sep 6 22:09:56 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>' Sep 6 22:09:56 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. ' Sep 6 22:15:30 Tower unassigned.devices: Adding disk '/dev/sdaa1'... Sep 6 22:15:30 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>' Sep 6 22:15:30 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. ' Sep 6 22:18:48 Tower unassigned.devices: Adding disk '/dev/sdaa1'... Sep 6 22:18:48 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>' Sep 6 22:18:48 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. '
This is the same error show for all 7 of my drives which previously mounted just fine. Anyone have any insight? I really need to get this fixed ASAP as these drives contain data I need to access.
I have tried reinstalling the plugin as well as full server restarts, neither seem to help.
-
I hope this gets some attention from @limetech. Seems to be a common issue. Anything we can do to help diagnose?
-
2
-
-
22 hours ago, Migz93 said:
Hmmm, that's interesting. Noticed we both have 1650 variant cards, could be something or could be nothing.
Although checking now, i don't have the ICH Nvidia Driver plugin, i did have the original LinuxServer one but as i'm not using the GPU at the unraid level i've just removed it.
Will see how my crashes go, if i get another one I'll try removing the GPU completely and if it crashes again i should have Plex & related tools setup on my 2nd box and i can try safe mode.
Cool - let me know how it goes. I have my server at a buddy's house ~6 hours away, so it's not as easy for me to swap hardware in and out.
Very interested to see the results.
-
I wanted to add I'm having the exact same experience as you, but haven't had a chance to diagnose hardware issues.
Unraid 6.8.3 is stable as a rock for me, Unraid 6.9 the trouble maker. I first had this issue on 6.9 RC2, figured it was a RC-related issue, and rolled back. Now that I'm on 6.9 stable, still the same thing. I've rolled back to 6.8.3 again as it's seeming like this is a software issue of some kind.
I wonder if this is somehow related to ICH's Nvidia Driver plugin? That seems to be a commonality between your system and mine - both using GPUs.
Ryzen 3950x
64GB 3000Mhz
GTX 1650
EVGA 750w Gold
-
3 hours ago, Maverick0984 said:
.torrents should be saved in your torrents folder by default.
Okay, so I lied a little. I do keep all .torrent files, but I have 11,103 in that folder and I only have ~150 I like to permanently seed. So I'm not really sure how I can easily utilize that.
But I do appreciate the advice!
-
I've got an odd issue going on. The webUI seems to just be... broken? Sonarr can contact qbit just fine, and I can see torrents are seeding via my private tracker, but the webUI just reports nothing.
This occurred after an unexpected shutdown to the server. I've tried force updating the container, but I've been warry to delete the appdata since I have 150+ torrents seeding and I no longer have the .torrent files. Any who, any insight is appreciated.
Below is an image of what I see. Just nothingness. Yet all the torrents are still seeding... lol.
-
9 hours ago, SignedOne said:
As we all know, PIA is currently moving their infrastructure, which results in pretty terribly reliability and constant connection issues when using their CurrentGen Network. Today, however, I discovered that they offer OpenVPN confs for their NextGen servers: https://www.privateinternetaccess.com/pages/download
AFAICT they work reliable. Only way to use them currently is to set the STRICT_PORT_FORWARD ENV variable to "no", since their NextGen network doesn't seem to support port forwarding yet.
For anyone having issues with this container while using PIA, this guy's comment fixed it for me. Switched to a NextGen OVPN file and it now works for me. This was super frustrating!
-
5 hours ago, Squid said:
Docker Tab. Click Container Size. You should be able to see easily which one is at fault.
None of my containers seem to be at fault - at least not to my eye? My docker image is at 20GB currently.
-
Thank you! That fixed it. What causes it to grow so large? I don't have that many containers.
-
Hello,
in the below screenshot you can see the "Docker" bar under the Memory section is at 95%. What is this? This has never been a problem until the last few days. I've tried restarting my entire server as well as disabling all my containers and it doesn't go down.
-
Hi,
My server randomly stopped working the other day and I haven't been able to get it back up and running. At first I simply tried restarting it, and I got to the following screen which showed the ipv4 IP address. When attempting to use that address, I could not access the GUI.
Then I tried booting straight into the GUI from the boot options menu. Once again, it was unable to connect:
Does anybody have any ideas on what I can try to get this back up and running? I'm at a complete loss. I should also add that not only can I simply not access the GUI, I can't access anything. Non of my docker containers start, or the array at all.
-
Any ETA as to when I can expect the docker container to update to 1.9.1.4272? It fixes an issue I've been having and it's been out for close to a week now!
-
4 hours ago, Frank1940 said:
And when you have the next failure and report back on it, give a few details about what time of night the lockup is occurring and what periodic tasks might be running. Have you ever had it lock up at any other time of day? Are you using mover, does it start its task, and does it finish? Does it run a correcting parity check and does it find and fix any errors?
It always seems to freeze between 3-7AM. Plex does it's nightly maintenance during that time, but I can't imagine why that would cause it to shut down. It is currently running a parity check, because the server has always locked up before I can even get the initial parity check complete! (which means my data is unprotected)
I'm unsure has to what the "mover" is so I can't answer that question.
I just ran a memtest and it came back saying there were no errors.
-
6 minutes ago, Squid said:
Also you need to post the exact model of the power supply.
EVGA 500 W1. Not the best PSU, but it's what I have.
7 minutes ago, Squid said:Since this is nice and repeatable, install the Fix Common Problems plugin and toss it into troubleshooting mode and do what it tells you to do. May or may not help diagnosis.
Okay, I have it installed and now I'll just wait until it crashes again.
-
Hello all,
For the third night in a row my unRAID install has just completely frozen. Web GUI doesn't work, shares aren't accessible, nothing. I'm having to go press the hard reset button on my case just to get it up again. I'm still new to unRAID (still in my trial period) so maybe there's something super obvious that I'm missing. Have any of you ever experienced this before? My box had Windows on it before and I've never experienced anything like it. Are there any diagnostics steps you all would recommend? I've read a few similar(ish) posts and in one of them the OP found his memory was faulty. Maybe I should run a memtest? If so, how would I go about doing that?
System specs if needed:
AMD FX 8350
16GB of RAM
EVGA 500W PSU
6x 8TB HDD
1x 1TB HDD
1x 120GB SSD1x SanDisk Ultra 32GB (boot device)
Currently running the following docker images:
Plex
PlexPy
Ombi
Thanks for your help!
Questions about how Unraid handles ZFS with vdevs, pools (6.12 rc7)
in General Support
Posted
Hi Jorge, do you know if this has been fixed as of the latest, 6.12.1? I've been having issues added a vdev of a smaller capacity to my zpool, unsure if due to user error or this bug still existing.