Everything posted by apandey
-
tips for testing new versions in isolation
I am planning to get familiar with plugin development With 6.12 coming up, and some plugins still not working, I am thinking of picking an abandoned plugin and try to fix it I have read some material in this forum, but what I am unsure of is how to best build a test sandbox during development. Keen to see how others develop I mostly develop on my macbook, but can also do so in a linux env if needed. I only have one unraid server, and I am reluctant to try 6.12 with it yet as I run my main workloads there. I have other desktop, laptop and mini PCs, but none of those have hardware like HBA etc. In most cases, I am probably not looking at specific hardware, so I am not sure it matters, but would be good to know of any approach to mock / virtualize hardware if needed. So what is the best way to try unraid 6.12 and develop plugins for it without disrupting my current install? Also, how can I do this regularly from licensing perspective? If I create a trial USB, it will eventually expire, and then that USB is blocked. How do developers use unraid? Is there a development build or some other approach?
-
M.2 NVMe drive not listed in Unraid but visible in bios
Have you tried booting with another distro - like Ubuntu live CD maybe? Will give an idea whether this is unraid specific or generally a linux issue
-
One disk getting full while others not so much
What is being written? New files or updates to existing files? If a file is already on a disk, it will remain there irrespective of free space elsewhere How is the data being written? Tools like rsync will create all dirs first, so things may all end up on first disk
-
Eth Nic interesting issue help
You should be able to change eth0 to be 10gbe interface in network rules and that should then follow the IP configuration set for eth0. If it's properly set for static IP, it should work. Can you post diagnostics from after reboot when it doesn't work? You will need to use a connected monitor for local login to unraid, then run diagnostics command and pick up the zip from boot usb
-
Notification Flooding
We can guess, or you can post diagnostics after you seen the issue
-
Blank Dashboard after updating from 6.8.X to 6.12.0-rc2
It's also a pinned recommended post in the 6.12.0-rc2 thread listing the incompatible plugins. It's GPU-stats in your case, and a fix is on the way. You can try it out from the prerelease thread too
-
with 6.12.0-rc2 how to use zfs system for the array? How to move to zfs?
What is your motivation? You want to try it as a new thing, or are you already familiar with zfs and want to start using it? "Array" in unraid speak is JBOD protected by unraid parity disks. The individual disks in JBOD can be zfs / xfs / brtfs, and can even be a mix of those filesystems, but they don't form a zfs pool. It is still an unraid Array with individual independent disks having the filesystem of your choice. This is not zfs pool by design If you are after a zfs pool, you can do that as an unraid pool
-
Add drives externally
Do you have a spare PCIe slot? You can also get an HBA with external SAS port which you can connect to a SAS connected SATA enclosure. Might still be cheaper to look for a case transplant as suggested by @Frank1940
-
Unraid never restarts properly
You never replied to this. Not sure how anyone can help without feedback
-
Notification Flooding
Post diagnostics after you have seen the notifications
-
SMART self-test Completed: read failure
Extended smart test runs completely in drive firmware without any influence from the rest of the system, so if that comes back with errors, the best course of action is to replace the drive. There is not much you can do about already failing hardware. Since this is parity, you aren't immediately losing data, but you are one step closer to that if another disk fails while you are waiting to replace
-
Fans keep starting and stopping
Does your bios has a fan curve you can customize? Perhaps post diagnostics zip after the undesired fan activity if you want someone to have a look
-
New server, migrate all cache?
I think it should work Are you using new config or planning to reuse the usb? If reusing, removing the ssd pool while those drives haven't gone missing (i.e. Before hardware change) yet might be better
-
M.2 NVMe drive not listed in Unraid but visible in bios
Never heard of it myself, and can't find anything meaningful when trying to look for it Good catch, but it does not look like a PCI switch in the block diagram. Would be curious if you could share what you find. Maybe ask manufacturer for clarification - this is new kit, so they must be helpful
-
Low transfer Speeds, what to exspect from Toshiba MG09-ACA
JorgeB was asking for diagnostics (look under tools tab, then attach the generated zip). After transfer, before a reboot
-
M.2 NVMe drive not listed in Unraid but visible in bios
Looks ok to me, sorry, I'm out of ideas. Will defer to someone else here
-
M.2 NVMe drive not listed in Unraid but visible in bios
how are the nvme drives connected? your motherboard only has 1 m.2 slot. Are you using any of the OCuLink connections? Or a PCI card? Have you looked at any shared slots in your motherboard manual, where using another connection might disable a nvme drive? Tried swapping the missing drive with another one?
-
High CPU usage for process
I see you have cache dirs plugin. Can you confirm if "scan user shares" is set to yes? That can cause higher CPU usage
-
Unraid boot looping after adding 2nd VM'ed pass through SATA SSD
what manual path are you setting? /dev/sdX can change across reboots, so if you want it to be consistent, use the /dev/disk/by-id/ path which remains same across boots
-
AsRock z690 board can't see LSI 9220-8i
Is there a newer firmware for your LSI card available? Was your old system using EFI BIOS? I am wondering if the difference is because the cards are not accepted on UEFI Bios
-
Large amount of data lost and I'm unsure why.
uh oh. glad that it was limited to the prank of just deleting files, it can go worse once someone can get to the unraid server in an unintended way
-
NVME drive stopped working and comes back only after reboot
try this
-
Parity Sync Errors
looks like interface errors, start by changing the cables. once you get rid of the interface error noise, can look at specific drive issues via smart
-
UDMA CRC errors on new UnRaid server - Advise
CRC errors can be due to anything no being stable in your data pipe. Basically data being sent from computer doesn't check out when written to drive. It can be controller, cables (SATA/power), drive itself. More often than not, its the cables / connections as they are the most fragile part in the chain. I would start by checking / reseating / swapping / replacing cables. That is most likely all you need If you want to be doubly sure, you can run an extended smart test on the drive. This test runs completely within the drive firmware and is thus immune to any external factors. If that comes out well, your drive is OK. It's an expensive test to run, so I will still just start with cables
-
Tainted Kernel and other errors
probably should discuss this in 6.12 RC thread or post a bug in prerelease forum section if not already reported Can a mod move please?