paulmorabi
-
Posts
103 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by paulmorabi
-
-
Hi,
I've installed a 10GB NIC (using an Intel 82599) and have connected it via SFP+ to my router. I've been trying different things with the settings but have gotten nowhere with enabling it, apart from needing to remove network.cfg and try again.
If I want to disable the onboard NIC and use the 10G NIC instead, my understanding is this needs to be set to eth0 and then disable bonding between the eth0 and 1. I've tried this but its made unraid inaccessible. Does anyone have more info on how to do this?
diagnostics attached and many thanks in advance.
-
2 hours ago, itimpi said:
When it gets written to will depend on the Allocation Method you have selected for the share and how full your current drives are. It can be some time! You could manually create a folder corresponding to the share name on the drive if you want to force it to show up early.
Perfect! That worked. Thank you!
-
12 hours ago, itimpi said:
Drives do not get added to the size for a share until at least one file or folder for that share has been created on the drive.
I was holding on replying to see if some data would get written to the new disk. I've copied over a lot of files and still nothing added to disk 3. Is there anything I can do to prompt this or is it just a matter of waiting?
-
Hi,
I've been doing some work rearranging disks on my array. In summary, I did the following:
* Disk 3 was a scratch disk and not part of the media2 share. I excluded it specifically from media2. I removed it from the array and added it as a cache pool.
* I added a new disk to my array and as this is the largest (20TB), made it the parity drive by removing the current disk and added it. Parity was successfully re-pgenerated.
* I added the previous parity disk back to the array as disk 3. The pre-clear and formatting all worked and it was added.
* I updated the media2 share to include all disks in the array (so including disk 3)
After all this, I've started and stopped the array etc. but for whatever reason, it's not showing the extra space from the addition of the new drive (in terms of total capacity of the share and free space). The new disk, disk3 also seems to be empty of files so nothing is being copied there.
Diagnostics is attached. Is there anything I can do to fix this? Should I remove it as disk3 and add as the next new disk?
-
1 hour ago, Frank1940 said:
Try googling linux change uid of user and see if you can change the user UID on the VM to match that on Unraid. (I would also suggest making that user-- paul ---be in the 'users' group on Unraid and be in the same GID on the VM.)
Hmm on both systems the uid is 1000 and the "users" group gid is 100. Still though, if I chown to "paul:users" on Unraid, it gives me 99 and group users on the VM. This shouldn't be the case?
-
H, I've created a new cache and some files over to it. I have a Linux VM running that accesses the files by NFS and this is where the problems begin. I have a user paul and group users on both the Unraid machine and the Linux VM but the uid is I guess different. I can change the permissions so they are 777 and can then edit/remove files. The user is listed as 99 so its reflecting the UID of the "paul" user on the Unraid host? If I want to change the owner of the files on the VM to be the "paul" user within it, I get an operation not permitted error. Part of the reason I am looking to do this is because I am running several docker containers on the host and permissions are based off of it being this user.
I'm using the public setting for the NFS share and the fstab entry for the share is as follows:
Quote192.168.1.xx:/mnt/user/media /media/share nfs cto 0 0
I know its probably something simple here but have been searching for hours and endlessly confused.
-
On 11/12/2023 at 11:53 AM, itimpi said:
There should be messages in the syslog about mover starting and finishing. Having said that probably the easiest in this case will be that the 'system' folder disappears from disk6.
You can just set up a drive in a new pool, and then set up the share to have this as the primary storage and the array as the secondary storage. and mover direction to be array->Pool As before running mover would transfer the files to this new pool. Once it has all transferred then you can remove the secondary storage option from that pool. It would definitely improve performance as writing to a parity protected array has large overheads as described here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. It is now not going to interact with accesses to the array or to the cache pool. As long as your downloads go via the User Share and do not explicitly name disk6 this should be all that is required.
Another option to improve performance would be to enable Exclusive mode under Settings->Global Share settings. For shares that have all their content on a pool this can improved performance as it bypasses the fuse layer in Unraid that is used to handle User Shares.
Thanks. I don't have another disk handy so I am going to try moving the 4TB disk to a separate pool as this is the lone disk assigned to the downloads share. I've started backing up its contents to another share on the array. I will remove the disk from the current array (following these instructions) and then add it to its own pool. I understand this will format the data on the disk so I'll need to delete and recreate the downloads share on the new pool and then copy the stuff back over? Is that correct?
EDIT: Above operation seems to have worked reducing the overall server load.
-
36 minutes ago, itimpi said:
Anything writing to the array will adversely affect the performance of other applications using the array. You could definitely put your downloads on a separate drive (in a new pool) to get it out of the array. Having said that I have no idea how large your downloads share is - if it will fit you are likely to get a good performance increase by putting on your existing cache drive.
Another think I notice is that the 'system' share has part of its contents on disk6. You will get better performance from docker containers if it is all on the cache. You have your mover setting correct for it to be transferred to the cache, but since mover will not move open files you can fix this by temporarily disabling the VM and Docker services under Settings so they do not keep files open in that share and then running mover from the Main tab. When that completes you can re-enable these services.
Thanks for this. I've just done the mover operation but there is no way to know its completed?
The current downloads disk is 4TB and its a WD drive. My cache is currently 1TB. I knew this was an option but its probably too small for now. What does moving the downloads share to a new array entail and how does or can it improve performance?
My final option is to move Plex to a separate host but its the last resort option, if possible.
-
I've noticed that a lot of disk activity on the array is causing Plex especially to hang and become very slow to complete unresponsive. This mostly happens when sabnzbd is decompressing files or they are being transferred to the share on the array by Sonarr/Radarr. When the two are happening together, everything slows to a crawl.
I've tried a few different things - pinning cpu cores to Plex didn't do anything but tweaking sabnzbd to pause downloading while decompressing and use fewer threads as remediated the issue somewhat.
Currently, I have my downloads/scratch disk as part of the array but it is its own share so not spread across disks. Can I take this out of the array and make it its own disk? Is there anything further I can do to eradicate this? Diagnostics attached.
-
On 10/16/2023 at 8:37 AM, paulmorabi said:
Last Sunday, I removed a stick of RAM and reseated the CPU heatsink and cleaned a few other areas. I don't want to jinx myself but its been 7 days and no system freezes as yet. Looks like it is probably RAM gone bad and/or cleaning/reseating a few things has fixed it? Either way, I'll give it a couple more days and purchase replacement RAM.
On RAM, is there anything I should look out for when it comes to purchasing? Given this will run 24/7, apart from ECC, anything I need to consider?
Crashes stopped after this and I replaced the RAM so seems like it was a faulty RAM stick.
-
On 10/8/2023 at 12:35 PM, JorgeB said:
Most likely, it would very bad luck to have 2 bad sticks, but of course not impossible.
Last Sunday, I removed a stick of RAM and reseated the CPU heatsink and cleaned a few other areas. I don't want to jinx myself but its been 7 days and no system freezes as yet. Looks like it is probably RAM gone bad and/or cleaning/reseating a few things has fixed it? Either way, I'll give it a couple more days and purchase replacement RAM.
On RAM, is there anything I should look out for when it comes to purchasing? Given this will run 24/7, apart from ECC, anything I need to consider?
-
22 hours ago, JorgeB said:
Since you have two sticks of RAM, try with just one, if the same try the other one, that would basically rule out bad RAM.
OK, had another crash with all of those BIOS changes so reverted the settings and took a stick of memory out. Will alternate if it happens again.
I'm guessing its unlikely both suddenly became faulty so if its happening with both sticks then its somewhere else?
-
1 hour ago, JorgeB said:
Try with Plex disabled, if it still crashes it's likely hardware, if not Plex would be the likeky problem.
I've updated the BIOS and edited the BIOS settings to:
* Disable C states
* Set power supply idle control to typical current
* disabled all over clocking and XMP profile.
* disabled CPPC preferred cores and CPPC
I noticed these were mentioned elsewhere as affecting stability especially on older Ryzen's. However, they've never caused issues before here. I also removed a USB card I no longer use and given it a general dusting inside. High temperature doesn't seem to be an issue though.
The Plex error and the kernel code error occurred again overnight and it only froze an hour or so ago so probably not that either. If it crashes again, I'll revert the BIOS settings and disable all dockers, including Plex, and probably also the VM I have running. If it stays up more than 48 hours then the problem is somewhere there and I need to gradually enable things until it freezes again?
I can also restore from a backup I took about ~2 months ago.
If it's hardware, where do you recommend I start?
-
15 hours ago, JorgeB said:
So it was stable with 6.12.3 or not? If the issue started out of the blue with a known good release it could be hardware related, that usually does not leave anything logged.
Yes, it started out of the blue last Sunday. The only thing I did prior to that was update Plex. And one week before that, edit some of the CPU pinning and isolation settings for my docker and VM.
-
12 minutes ago, JorgeB said:
Without anything logged difficult to guess what the problem is, you could try downgrading to v6.11.5 and see if the same thing happens.
Why that version? 6.12.3 and all other previous versions were also super stable until this started a few days back (and it was on 6.12.3 when this first happened).
-
On 10/4/2023 at 12:02 PM, paulmorabi said:
I downgraded to the previous version and will try this and then if it crashes again, disable.
Downgraded to the previous version of Plex and thought it was ok but has just happened again. Nothing in the logs beforehand that would indicate anything. syslog attached, any ideas?
-
1 hour ago, JorgeB said:
Yep, could still be Plex related, see if it crashes if you leave it disabled.
I downgraded to the previous version and will try this and then if it crashes again, disable.
-
1 minute ago, JorgeB said:
This should be harmless, used to see them in a lot of diags.
Post the complete log file.
Here you go. There is not much additional there. I thought it was linked to the plex issue as the following kernel message is logged at the same second.
-
My Unraid server has been freezing randomly over the last few days. I've enabled syslog and the last lines recorded before the system freezing are:
QuoteOct 4 02:10:04 FatBoy kernel: PMS LoudnessCmd[17642]: segfault at 0 ip 00001513356b3920 sp 00001513301180c8 error 4 in libswresample.so.4[1513356ab000+18000] l
ikely on CPU 0 (core 0, socket 0)
Oct 4 02:10:04 FatBoy kernel: Code: cc cc cc cc cc cc cc cc cc cc 8d 04 49 48 98 4d 89 c1 49 29 c1 48 63 c2 48 63 c9 49 39 f9 76 7c 66 2e 0f 1f 84 00 00 00 00
00 <f3> 0f 10 06 f3 0f 5a c0 f2 0f 11 07 f3 0f 10 04 06 48 01 c6 f3 0f
I'm running Plex via docker on the server with GPU pass through via an NVidia card. I've updated Plex recently also upgraded to 6.12.4. However, on the latter, the first crash happened prior to that.
I've attached diagnostics and prior to this happening over the last few days had months of stability without any issues with the same setup. Any help would be appreciated.
-
3 hours ago, Frank1940 said:
What is the plugin SATA card and is it in the IT-Mode? (Some Cards are actually RAID cards in a non-raid configuration and they can be somewhat problematic when trying to move drives between their ports and on-board ports.)
Yes, its an LSI card in IT mode.
-
1
-
-
25 minutes ago, Michael_P said:
This isn't accurate, you can use whatever SATA ports are available
Perfect, thank you!
-
Hi,
I need some advice on array expansion. I've got a SATA Card with 8 ports and currently have 8 drives connected to it in an array. One of the drives is smaller (4TB) than the others (ranging between 12TB to 16TB). I have a share configured to only be on the smaller drive for downloads. I've got a large case and would like to expand my array further. Physical space is not an immediate issue but I've seen that drives in an array should all be on the same SATA card and not mixed between different SATA cards or a SATA cards and onboard SATA.
I was thinking to move the 4TB drive out of the array and swap it with a 16TB drive. Then connect the 4TB drive to my mainboard's SATA. The intention would be to keep the 4TB drive for downloads and as its a scratch disk am not too fussed if it's not protected somewhat with the parity drive. Is there a way to do this in Unraid? Would I still need to add the drive to the array? And am I effectively stuck expanding my array beyond the 8 drives due to the limited ports on the SATA card?
Thanks in advance
-
I've got a strange issue with stale file handles and docker containers that seems better when monting via SMB rather than NFS. However, one of the docker containers I am using (gphotos-sync) uses symlinks and the unraid SMB share doesn't allow symlink creation. Is there a way to enable this?
-
11 minutes ago, kubed_zero said:
If you use SNMP without adjusting any of the default settings, it should work without a hitch. Those that have had issues still have not been able to tell me as the maintainer what exactly to do to reproduce their issues, so as far as I know there shouldn't be any problems with running this plugin.
At the end of the day, this plugin is just a wrapper script to install the SNMP Slackware package, so in the worst case you could just default to installing SNMP manually.
Thanks . I just installed and didn't change any settings. It's working fine. I don't often reboot but will definitely let you know if something goes awry. Thanks for putting together the plugin
-
1
-
Stuck enabling 10G NIC
in General Support
Posted
Apologies for the late reply. I've been ordering NIC's and cables to test. Yes, you're correct it was a bad cable. All good now.