Glimmerman911

I replace the power cable and rebuilt, success, thank you!

I will replace the power cable and try rebuilding again.

I replaced the SATA cable, and followed the instructions and successfully rebuilt onto the same drive, but it still shows the red x and indicates Drive is Disabled. I have attached new diagnostics, do I need to replace the drive or do something different? tower-diagnostics-20250516-0830.zip

Will do thanks!

My Disk 9 has a small x next to it and says "Device is Disabled" I have attached diagnostics, I am not sure how to proceed, if I need to replace the drive or if I can rebuild onto this same disk, or some other action please? tower-diagnostics-20250514-1204.zip

Adding pci=realloc=off worked, I am successfully on unraid 7.0.0 with all drives showing up. The LSI raid cards did not need to have the firmware updated. Thank you for the assistance!

Thank you, I will add this to the flash drive and get the firmeware on the LSI cards updated and report back.

Thank you, Diagnostics for v6.12 attached. tower-diagnostics-20250219-0839.zip

I am having trouble finding firmware and process that I should flash to my M1015 raid cards. can someone point me to a firmware that is working on unraid 7 that I can flash my firmware to?

The LSI cards I probably got ~15 years ago and haven't touched them, the mobo is probably 5 years old. I will get the LSI card firmware updated, as well as my mobo BIOS updated, then try the upgrade to 7.0 again, and report back here. Thank you for the assistance!

Thank you JorgeB. When you say BIOS update, is that for the LSI card, or my motherboard? There are 2 different cards in 2 different PCIe slots, and both stop working on unraid 7. So I don't think it has anything to do with the PCIe slots? When I go back to unraid 6.12.8 it works fine, so I have to wait for a version of Linux/Unraid that fixes this, or I can't upgrade any more? These are very common cards, I am surprised if it is a kernal issue a lot of users aren't having issues?

Thank you, I have upgrade and rebooted, same issues. Diagnostics attached. tower-diagnostics-20250218-1127.zip

I tried upgrading to Unraid 7.0, but even after rebooting and re-seating everything to make sure all was good, Unraid does not detect any of my drives on my LSI SAS9220-8i raid cards, of which I have 2. All my drives connected directly to mobo work fine. I downgraded to 6.12.8 and everything worked fine. How do I get my LSI SAS9220-8i raid cards to work with unraid 7.0?

It just took a very long time, it has mounted and the rebuild has started, all good if the rebuild is successful.

Diagnostics attached. I also see this error in the log: Feb 2 14:01:55 Tower emhttpd: reiserfs: resizing /mnt/disk15 Feb 2 14:04:42 Tower nginx: 2025/02/02 14:04:42 [error] 6947#6947: *75 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.166, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "192.168.1.93", referrer: "http://192.168.1.93/Main" tower-diagnostics-20250202-1415.zip

I had a missing drive error and its an older drive so I decided to replace it with a larger drive. After replacing it and starting the array to do the rebuild, it is stick at "Mounting Disks" and I can see in the Main tab, it is stuck on mounting disk 15 which is the new disk. What do I do next please?

After copying the vdisk1.iso, the VM started in the VM manager, which is great. I get the windows prompt for login and password which I enter, but then I just get a black screen, it does not bring up the windows OS. Any idea what the issue might be? I stopped and started the VM again, and tried using VNC to login instead of RDP, but the same issue is encountered. *update* A server reboot fixed the issue, I am marking this thread as SOLVED, thank you!

I copied the docker.img from my old 1tb cache to the new 2tb cache, and my dockers are now working, woohoo! I also found the vdisk1.iso for my VM on the old cache, not sure why it didn't move, I am copying it now and that should fix my VM as well. Will post back my results on the VM when it finishes copying.

Thank you for the reply, I am not clear what I need to do next though. Do I need to re-install my old cache drive, get the docker.img file and replace the docker.img file on my new cache drive? I checked the new cache drive, and there is a docker.img on the root. Any advice for getting my VM working? I checked the cache drive for the file it is complaining about and it is NOT there: /mnt/cache/apps/VMs/Windows10/vdisk1.img Not sure why this would not have been moved, then moved back in this process as it is not on the root? Thanks again, Rory

Diagnostics attached, thank you! tower-diagnostics-20240808-1101.zip

I upgraded my cache from 1tb to 2tb following the process below. Everything seemed to go perfectly, until I re-enabled dockers and vms. After re-enabling dockers, the docker page simply says "No Docker containers installed". This has me freaking out, this is my primary purpose for Unraid is the dockers for downloading and Plex. After re-enabling VMs, I see the VM, but when I try to start it, I get an error "Cannot access storage file '/mnt/cache/apps/VMs/Windows10/vdisk1.img': No such file or directory" Most critical, how do I get my dockers back, I see the docker images and such on the cache drive. Process I followed to upgrade the cache drive: 1. Stop all running Dockers/VMs 2. Settings -> VM Manager: disable VMs and click apply 3. Settings -> Docker: disable Docker and click apply 4. Click on all shares that are using the pool you want to empty and change them to have the pool as primary storage, array as secondary storage and mover action set to move from pool to array 5. Run move, when it finishes check that your cache is empty (any files on the cache root will not be moved as they are not part of any share) 6. Stop array, replace cache device, assign it, start array and format new cache device (if needed), check that it's using the filesystem you want 7. Click on Shares and change the mover action to move from array to pool for all shares that you want moved back to cache 8. On the Main page click "Move Now", wait for mover to finish 9. Set the shares that are cach only to just primary storage, no secondary storage 10. Re-enable Docker and VMs

I have an application that needs OpenGL, which will not work with VNC and the virtual video adapter, it generates and error on launch when I do not pass through my GPU. When I enable VNC as my first graphics adapter and pass through my GPU as the second graphics adapter, the program will launch whereas it won't with just the VNC adapter. And I verified under windows settings that applications have the 750ti as default, and it shows in device manager. This leads me to think Windows is using the 750ti, but perhaps not, but it is strange the OpenGL application works then? When I edit the VM to remove the VNC adapter and only have my 750ti, when I RDP to it, I get an RDP error - it does not connect, likely the VM is not booting. If I add the VNC adapter in, I can VNC in and RDP in. Not sure where to go from here?

I am passing through an NVIDIO 750 ti on my Windows 10 VM, I see the card in Device Manager, and I have installed the drivers. Everything looks to be working, but when I try something simple like playing a youtube video, it is terribly chunky as the video card is not keeping up. FYI, I have VNC set as the first graphics card in the VM setup, so I can use VNC instead of RDP when needed and to help diagnose issues. Is this an issue? I have I have an AMD video card that is dedicated to the physical unraid server to run a monitor, it is not passed through. In Device Manager in the Win10 VM I see Microsoft Basic Display Adapter, Microsoft Remote Display Adapter, and my NVIDIA 750 ti. Perhaps the Win10VM is not using the 750ti as the graphics adapter? Or some other reason the performance is un-useable?

Believe I have it resolved: The 3TB drive that initially went missing must be dead, it is not being picked up The 8TB drive that I tried installing is from an 8TB seagate enclosure, brand new but appears to be dead or maybe seagate drives have the 3.3v pin? The 10TB drive that I tried installing is a white label WD drive that has the 3.3v pin and my power supply is not compatible, so it powers down I installed a molex to sata power connector to bypass the 3.3v and I now have the 10TB drive visible in Unraid, and chose it for disk 8. I entered my password to start the array, and now it is "Starting..." and disk 8 shows as Mounting so hopefully that is resolved now. When I reset my mobo bios, it turned off CPU virtualization, so I turned it on, presumably that is resolved when the array starts and I can check my VMs. I still get the following error along the top of the screen, since upgrading the flash: Warning: parse_ini_file(/usr/local/emhttp/state/flashbackup.ini): failed to open stream: No such file or directory in/usr/local/emhttp/plugins/dynamix.my.servers/include/myservers2.phpon line552 *Edit* The array has now progressed to rebuilding, woohoo! Thanks for the help! VMs are working now as well, just the flashbackup error to deal with now?

No disks show up when attached to my server to replace the disk or to add a new disk to the array. I have tried with 3 different disks on known working SATA & power cables, and none of them show up unfortunately.