JBanner

Here is the situation. unRaid has been working on this hardware extremely well for some time, however, a couple of weeks ago i added some drives to a controller that was in the system and unused. Those drives were throwing up a lot of errors, so as I was going on vacation. I simply disconnected them. (There were in caddies on a PowerEdge server, so I removed the caddies and put blank ones in place. While on vacation, I looked at the errors and it indicated that the cables were probably at fault, and as I had never used this controller and cables, I ordered up some new cables for my return from vacation. Fast forward to today, I retuned home. I shut down unraid, and swapped the cables over. - I had also has a new riser card arrive, so i swapped the controller into a different slot. I tried to boot up and it hung at some point - I didn't notice at what point. I decided I'll mess with this another time, so removed the unused controller, and reverted everything else back to how it was. unraid will still not boot. It is starting to boot, but then after it goes to Loading /bzroot..ok" it goes no further. I downloaded a backup of the flashdrive from unraid connect, put all of the old files into a folder called "OLD" and put all of the files from the backup onto the root part of the flash drive. However I am still getting the same problem, It goes as far as the "loading/bzroot...ok" I did a quick search on hear and it mentioned renaming the efi- to efi, i tried that but no change. - The Bios is set to boot in uefi mode. - I don't believe any bios settings have changed Any ideas on how to progress? I cannot add diagnostics... but if there are any files that would help please let me know.

Thanks for the reply. I'll go ahead and give it a go.....

Currently I have an Nvidia RTX3070 up and running, passed through to a Windows VM - All working well. Available to me is an AMD Radeon 5700xt that I would like to install alongside the Nvidia card, and use for transcoding & other work. Would this work? or is it not possible to mix types like this? Would I install both sets of drivers from community apps?

Ok, Edited out and restarted the server. Thank you

Interesting.... I learn something every day. I assumed that because it was set that way in the setting that was how it is, and I've not edited that file certainly not since swapping to the new hardware. Ok I've changed that line in the file "smb-extra.conf" to "server multi channel support = no" - I'm assuming this will be ok? Lets see how it goes...

SMB Extras is turned off, and Enable SMB Multichannel is also turned off within the SMB setting on the Settings Page. "testparm -s" returns this....

This is a new machine to me, I did post earlier in the week about not being able to get the Monitor to work with the Unraid GUI. That I can live with, but I am having some crashes, and trying to establish if there is a fault on the hardware or if it is config related. Machine is running generally very nicely, but I am getting the occasional random crash (Maybe once per day?) This morning it shutdown gracefully with a message in the log saying the ups had reported a power fail, but we've not had a power cut, so not sure what happened there, however at lunchtime it crashed. Log attached. (I am mirroring to Boot Flash at the moment) Diagnostics attached. syslog syslog-previous tower-diagnostics-20250320-1400.zip

Ok, I'll live with it.... Not the end of the world.

It completely matches what happens on the physical monitor, I get the initial booting into gui, and the scrolling text thereafter, followed by going blank when the gui loads.

Not sure entirely what you mean here, I think that means to use the built in iDRAC? Using iDRAC, I can see the state of the machine, and force restarts etc, but I cannot get any video output from the iDRAC console from unraid.

Just tried this and still the same, no video on the attached monitor, but server is up and running, and I can connect via Web Browser. I realise that I can mostly manage the server via Browser, but there are occasions that I could do with accessing the physical monitor...

I have just swapped out my server hardware from a regular PC with an HBA card to a Dell Poweredge R740 Server. I have swapped the HBA card over and the Boot Flash USB and the server starts up and runs - So Far So Good. The Problem is that on starting up the server hardware, I initially get video on the attached monitor, and I choose the Start with GUI option. The Server starts up but the video goes blank when the GUI starts. The Video is live, so the monitor is receiving something. Remote access works and all services are running fine, just the GUI local to the server not working. It is specific to unraid as If I boot the server into another OS the monitor is working there... (I'm considering possibly using Proxmox in the future to virtualise unraid, but for now running unraid on the bare metal, proxmox boots and gives me the usual login screen available.) I have seen there is a couple of threads here about similar issues, but I'm not certain they are the same - they mention turning opff fast boot, but I do not seem to see that as an option on this Dell BIOS. Any ideas? Diagnostics Attached tower-diagnostics-20250317-1155.zip

OK Removed Mover Tuning. Will see how it goes, thank you.

Explored the mnt/none/ directory as I didn't understand it... I have copied everything out of it, into the correct places on the array. And I've deleted it.... Invoked Mover manually, and the same sorts of errors again, and again there is now a /mnt/none/ directry been created. Now I've run out of ideas...

Restarted, and changed mover to a monthly schedule. I have left the server running for a bit and it seems stable, so it MAY be the mover issues causing the crash. Invoked mover manually, and I am getting lots of this..... - I have stopped mover from running again for now.... I have scrubbed both Cache SSD's and there is plenty of space on the array and cache drives. Jan 15 13:50:34 Tower move: rsync: [receiver] rsync_xal_set: lsetxattr("/mnt/none/data/usenet","user.DOSATTRIB") failed: Operation not supported (95) Jan 15 13:50:34 Tower move: rsync: [receiver] rsync_xal_set: lsetxattr("/mnt/none/data/usenet/incomplete","user.DOSATTRIB") failed: Operation not supported (95) Jan 15 13:50:34 Tower move: rsync: [receiver] write failed on "/mnt/none/data/usenet/incomplete/Abdul.2017.1080p.BluRay.Remux.AVC.DTS-HD MA5.1-HDmux/bda9fef688364080a0e0d1d029a4a3e6.part010.rar": No space left on device (28) Jan 15 13:50:34 Tower move: rsync error: error in file IO (code 11) at receiver.c(380) [receiver=3.2.7] Jan 15 13:50:34 Tower move: rsync: [sender] write error: Broken pipe (32) Jan 15 13:50:34 Tower move: Not deleting dir containing 143 files: /mnt/disk11/data/usenet/incomplete/Abdul.2017.1080p.BluRay.Remux.AVC.DTS-HD MA5.1-HDmux Jan 15 13:50:34 Tower move: numfmt: invalid option -- '1' Jan 15 13:50:34 Tower move: Try 'numfmt --help' for more information. Jan 15 13:50:34 Tower move: -365 files remaining from array to caches B Jan 15 13:50:34 Tower move: Moving "/mnt/disk11/./data/usenet/incomplete/Abdul.2017.1080p.BluRay.Remux.AVC.DTS-HD MA5.1-HDmux/bda9fef688364080a0e0d1d029a4a3e6.part012.rar" to /mnt/none/ Jan 15 13:50:34 Tower move: rsync: [receiver] rsync_xal_set: lsetxattr("/mnt/none/data/usenet","user.DOSATTRIB") failed: Operation not supported (95) Jan 15 13:50:34 Tower move: rsync: [receiver] rsync_xal_set: lsetxattr("/mnt/none/data/usenet/incomplete","user.DOSATTRIB") failed: Operation not supported (95) Jan 15 13:50:34 Tower move: rsync: [receiver] write failed on "/mnt/none/data/usenet/incomplete/Abdul.2017.1080p.BluRay.Remux.AVC.DTS-HD MA5.1-HDmux/bda9fef688364080a0e0d1d029a4a3e6.part012.rar": No space left on device (28) Jan 15 13:50:34 Tower move: rsync error: error in file IO (code 11) at receiver.c(380) [receiver=3.2.7] Jan 15 13:50:34 Tower move: rsync: [sender] write error: Broken pipe (32) Jan 15 13:50:34 Tower move: Not deleting dir containing 143 files: /mnt/disk11/data/usenet/incomplete/Abdul.2017.1080p.BluRay.Remux.AVC.DTS-HD MA5.1-HDmux Jan 15 13:50:34 Tower move: numfmt: invalid option -- '1' Jan 15 13:50:34 Tower move: Try 'numfmt --help' for more information. Jan 15 13:50:34 Tower move: -366 files remaining from array to caches B Jan 15 13:50:34 Tower move: Moving "/mnt/disk11/./data/usenet/incomplete/Abdul.2017.1080p.BluRay.Remux.AVC.DTS-HD MA5.1-HDmux/bda9fef688364080a0e0d1d029a4a3e6.part011.rar" to /mnt/none/ Jan 15 13:50:34 Tower move: rsync: [receiver] rsync_xal_set: lsetxattr("/mnt/none/data/usenet","user.DOSATTRIB") failed: Operation not supported (95) Jan 15 13:50:34 Tower move: rsync: [receiver] rsync_xal_set: lsetxattr("/mnt/none/data/usenet/incomplete","user.DOSATTRIB") failed: Operation not supported (95) Jan 15 13:50:34 Tower move: rsync: [receiver] write failed on "/mnt/none/data/usenet/incomplete/Abdul.2017.1080p.BluRay.Remux.AVC.DTS-HD MA5.1-HDmux/bda9fef688364080a0e0d1d029a4a3e6.part011.rar": No space left on device (28) Jan 15 13:50:34 Tower move: rsync error: error in file IO (code 11) at receiver.c(380) [receiver=3.2.7] Jan 15 13:50:34 Tower move: rsync: [sender] write error: Broken pipe (32) Jan 15 13:50:34 Tower move: Not deleting dir containing 143 files: /mnt/disk11/data/usenet/incomplete/Abdul.2017.1080p.BluRay.Remux.AVC.DTS-HD MA5.1-HDmux Jan 15 13:50:34 Tower move: numfmt: invalid option -- '1' Jan 15 13:50:34 Tower move: Try 'numfmt --help' for more information.

ok didn't take long for it to go down.... here is the syslog..... I just read a bit of it and there are a load of No Space errors, but all drives have plenty of free space.... syslog

Thanks for the reply I have had it running a memory test it did 2 passes showed no faults. I have now enabled the syslog server, and set it to copy to flash. Could it be a faulty flash drive as this is a brand new one, only been using it since the power cut?

HI, earlier this week I had a power cut that took my power out for over 4 hours. Unraid would not start up afterwards, and the Boot Flash drive was corrupted - It is a fairly old flash drive, and I had another prepared to go, so just a case of updating the files on it from the backup from in the night, and transfer the licence and it booted up. Docker.img was corrupted. So rebuilt it and reinstalled all of my dockers. Some files used by the dockers were corrupted also, but they could of all been in use when the power cut happened, so nothing too alarming. However, I am now in a position where the server is acting strange. - it ran for a couple of days relatively ok, but i did see some more corruption, but unable to say if it was related to the power cut or not. So, today, I was unable to log into the homepage, I used usual password and root username, but it would not accept it. (I copied and pasted the password so I know it was correct.) and after a couple of tries, it stopped responding completely - as in the web page was no longer loading. The dockers were still running, and SOME of the shares were working. I went to the physical gui mode on the server, and it was there and accepted my root and password. I shut down the server, and started it back up. It ran for a few hours, dockers were all working fine. - Then the same thing - no response on the home page. I have done another shutdown and restart and grabbed diagnostics. Please can someone give me some ideas on what to look for? - I want to get the server stable before upgrading to 7.00 Diagnostics attached. tower-diagnostics-20250114-2136.zip

My bad. Removed.

I currently cannot stop the server as it says parity operation in progress. Should I let it complete and then do the check filesystem?

I have recently had some power issues and a failed drive. I have sorted the power and replaced 2 drives and rebuilt the parity. Array has ran for a few days with no issues, and then I did a reboot and one drive came up as "Unmountable Unsupported or no filesystem" Array is currently started, with a orange icon next to the drive saying its emulated. and it is saying its rebuilding. Drive is showing with an option to format it. How do i best move forward? Format drive or check filesystem in maintenance mode? Diagnostics attached tower-diagnostics-20241219-0805.zip

Thank you again. I did a new config without drive 13 and server is building the parity onto one of the 12TB drives. Next step is to replace drive 2 with a 12TB drive as it's having some read errors. Then I'll reassess what other drives may need replacement.

Thanks again for your answer. Ok just to get this clear before I proceed, Luckily I did move all the data off drive 13. So do a new config and exclude drive 13 from the array, and put the new 12TB drive as parity, and let it build. And then add the second 12 Tb drive after as a new drive no, or to replace one of the smaller drives, probably drive 2 as that may fail too. Or, you say use a new spare disc… Does that mean to do a new config and place a new parity drive and a new drive 13 both as 12TB drives? - Can I do this in 1 step or would I have to do 2 steps? Also, I have never done a new config before so what would I loose out of the configuration that I currently have? Would it just accept the change in drives, rebuild parity and everything else would be the same? Sorry to ask questions, I just want to get out of this mess as quickly as possible.

Yes that is correct. And i only had a 12tb drive to replace it with.

Thank you for your reply, Diagnostics attached. I have 2 x 12Tb drives available and want to proceed with caution, so any advice is appreciated. I realise that Drive 2 is also needs replacement, and probably drive 11 as well..... So I was going to move the data off drive 2 once the parity is up and sorted. tower-diagnostics-20241207-1438.zip