stor44
-
Posts
136 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by stor44
-
-
Thanks for this template! Usually these apps require a separate database docker etc, so it's nice having this all setup automatically.
-
On 7/12/2023 at 5:37 PM, Squid said:
Switch to advanced view in the docker tab. There's probably another container (orphaned?) at the bottom that's using the same image. Delete that one first.
Thanks for this. A few of my docker containers were failing with the same error as in the first post. Turns out I had several orphaned docker images. I've deleted those, and did "Force Update" on each docker app that still wouldn't start, and now they're up and running again.
-
Thanks for the reply, will do.
-
Hello. Noticed this morning that I couldn't mount any unRAID shares. Had a look at the unRAID screen and turns out it had a kernel panic. Diagnostics are attached. I'm just wondering if something obvious (and bad?) had happened?
I had to do a hard shutdown and restart, now it's running a parity check (which is a drag because I just did one on Thursday, plus it's gonna be 30 Celsius today, but oh well).
Thanks for your time.
-
Seeing the same error here.
-
Bah, missed the survey by one day. Hope you folks made good decisions!
-
On 6/3/2020 at 2:16 PM, Milldor said:
Setting MakeMKV to run as root user fixed the drive not being detected for me.
Use PGID and PUID as 0.
Thanks for this. I haven't used MakeMKV for a long time, and had removed the container. Today I realized my optical drive had a bad SATA cable, so I replaced it but still couldn't see the drive even though I could see it in unRAID and my BIOS menu.
Setting those two values to 0 worked! Cheers.
-
15 hours ago, ljm42 said:
To the next person who finds this thread - if you have the UD Preclear plugin installed, please reboot BEFORE running any extra commands. I need to know if that reboot is enough to solve the problem
thanks!
Hi @ljm42, I can confirm that solution. I have the UD Preclear plugin, and had the same issue as Koenig (the MyServers window was telling me to update the plugin, after I had already updated it). A reboot this morning has solved it. I didn't need to run any commands. Cheers!
-
1
-
-
Just to note, it is documented correctly here:
https://wiki.unraid.net/Manual/Security#Https_with_Unraid.net_certificate_-_with_no_fallback_URL
"Set Use SSL/TLS to Strict (this was previously called "Auto", but "Strict" is more descriptive)".
-
Not sure where to post this. On this wiki page for MyServers plugin:
https://wiki.unraid.net/My_Servers#Optional_step_for_Unraid_6.10
It says: "In the CA-signed certificate area, if there are no warnings about DNS Rebinding then go ahead and set Use SSL/TLS to Auto."
On my server, that option is called "Strict", there is no Auto. But it does the same thing. So just a small error.
Thanks.
-
7 minutes ago, itimpi said:
You might want to check that the SMB security setting under Settings->Unassigned Devices is not now set to No when you probably want the (new) Public option.
That's exactly what it was, excellent! Set to Public, now the shares instantly show again.
23 minutes ago, JorgeB said:Please use the existing plugin support thread:
Will do, didn't realize it was UD causing the issue.
21 minutes ago, trurl said:You can go directly to the correct support thread for any of your plugins by clicking its Support link on your Plugins page.
Good to know, will keep in mind for next time.
Thanks for all the help, very appreciated.
-
Hello. I have two drives in Unassigned Devices (not part of the array) that are supposed to be shared over the network. If I go to the Main page in the unRAID GUI, click on Edit Settings on each drive, AUTOMOUNT and SHARE are both checked on each drive, always have been.
I can also click on the share name of each drive and see the data is still there in the unRAID GUI.
I'm not sure when this changed, but it's only in the past week. But I also upgraded to 6.10.3 in that time.
One drive is a 4TB I use to backup my Windows PCs with. None of the PCs can see that drive listed on the network now, so the backups fail.
The other is a 10TB drive I store my older security camera footage from Blue Iris in a Windows 10 VM, and record TV from the Channels DVR docker app. The Channels apps on iOS and Apple TV still play all my recordings and is working normally.
So I know the drives are still there and working, they just aren't shared liked they were before? Is this a bug or did I do something wrong?
I've shut down unRAID a couple times (unrelated) and rebooted, no difference.
Thanks for your time. Diagnostics attached.
-
Update. I'm up and running with the new power supply and have completed a parity-sync rebuilding Drive 3 to itself, and things seem back to normal.
I found a solution in ASUS's help pages here, in Step 1 C. Turns out my motherboard has 3 power connections. The 24 pin, an 8 pin and an extra 4 pin. I didn't have the 4 pin connected! Fortunately the new PSU came with a two cables that have 8 pin connectors which split into 2 x 4 pins on one end. The AX860i does not seem to have those, but maybe I lost them at some point.
The parity sync completed without errors, and hopefully I've seen my last Red X for a while.
Thanks as always for your patience and advice, I really appreciate it.
-
43 minutes ago, trurl said:
Will anything boot with it?
No, the CPU cooler fans spin for a split second then switch off, and the PC stays off, it’s not even POSTing. I might have to contact Corsair, make sure this PSU isn’t a dud.
-
So I bought and installed a Corsair RM850X power supply. I removed all the existing power cables and used only the new ones that came with it to connect the motherboard and peripherals and drives.
Unfortunately, unRAID won't boot with this new power supply, so far anyway. I connected the power plug to my UPS, flipped the power switch on the PSU to the On position, and the lights on my motherboard come on. Then I press the power button my PC. My CPU cooler fans spin for a moment but then stop and the PC doesn't boot.
I tried it a few times, unplugging things and re-plugging, no luck. I then removed everything and did the paper clip test, the PSU comes on, its fan spins, no problem. So I don't think it's faulty? It has a 2021 date on the box.
For now, I've removed it and put the AX860i PSU back in and now unRAID is up and running. Still have a Red X on Disk 3, but I'd like to sort out this power issue before running another parity sync.
Thanks for any help.
-
Thanks, I agree. Might just have to try a new power supply.
-
5 hours ago, JonathanM said:
It seems you got EXTREMELY lucky. Most of the time when someone posts with a similar situation, it's to figure out why all of their drives aren't recognized any more, because they didn't realize modular cables are seldom interchangeable, Many times it will attempt to power up and blow the circuit boards out on all the attached drives.
Yikes. Well that's good to know, I'd never even heard of that.
4 hours left on my current rebuild, but Drive 3 has a Red X again now, and Disk 4 has some errors.
Thanks for any further ideas.
-
Thank you, I've now double-checked all my power connectors. I have a Corsair AX860i power supply from Jan 2014. I don't have any splitters.
This power supply has a self-test switch, so I unplugged everything and tested it, green light says it's good.
FWIW, I'm using 3 x 6pin cables into the "PERIPHERAL & SATA" ports, and 3 x 8pin cables into the "6+2 PCI-E & 4+4 CPU" ports. I've always used the bottom row, ports 4 5 6 on each kind, leaving room on top for more cables later.
As an experiment, I moved them into the top ports, 1 2 3 on each. But the power supply showed a red light when I pressed the power button on my case and the computer didn't boot.
I've now moved them back into the bottom row, and unRAID is booted and I'm running a parity sync to rebuild Drive 5 which is now good again.
Also, it seems I was using some generic SATA power cables. I've now swapped in the original power cables that came with this PSU. They have text on them that says "TXM/HX/AXi Only". Maybe that will help if there is some difference in the cables.
-
Bah. Thought it was solved, but now Drive 5 has a Red X. Here are my diagnostics, thanks for any help. Drives 3 & 5 were also the ones that had Red X's back in March, for what it's worth.
-
OK we're good. The rebuild finished with no errors. Then I bought new cables for all the array drives, two of these.
Thanks again for the help!
-
Thanks so much MrGrey and JorgeB. Yes, I have a backup of my important data on another system.
I also clearly have the memory of a goldfish, because Jorge you helped me with a similar (same?) issue with the same drive in March here:
So I have now swapped a new SATA cable for that drive, and followed the wiki instructions "Rebuilding a drive onto itself", so the rebuild is now running.
Should be fine now, thanks again! I'll mark this as solved once the parity-sync/rebuild is completed.
-
Hi there. Got an alert from my unraid server today, one of the drive has a red X. I've attached the diagnostics.
Found this in the SMART report for the failed drive:
SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FISMost of my unRAID problems have been bad cables or connections, so I guess it could be another one? At what point is it a bad controller?
Thanks for any help.
-
Thanks for that Jorge. I was able to shutdown unRAID, re-check the cables and swap the one to Disk 3 with a new cable. I booted back up and followed the wiki here to rebuild a failed drive to itself. A few minutes in, Disk 5 got a Red X as well. I let the rebuild finish so Disk 3 would be fixed, and then swapped a new cable in for Drive 5 and rebuilt to that drive as well. A couple long days, but I'm back to good now. Cheers.
-
1
-
-
Hi there. I started a parity check today, and a couple minutes in Disk 3 of my array drives suffered the Red X. I cancelled the parity check. Diagnostics attached.
I could use help reading the SMART reports for the drive, and if there's anything else that looks like trouble.
Thanks for any advice.
thanks!
Welcome to our new Technical Program Manager hire
in Announcements
Posted
Welcome Nick!