Everything posted by Veah
-
Cannot access webgui, dockers, SSH from specific computer
Its acting like it's on a different subnet than the server. That gets assigned either by your router/ap or on the workstation itself. Possibly port isolation ... Can you plug it into a different port on the switch/router?
-
Cannot access webgui, dockers, SSH from specific computer
The windows machine. Don't mess with unraid at this point cause it's working for everything else I believe
-
Cannot access webgui, dockers, SSH from specific computer
Try a different random IP, preferably DHCP assigned. If that works then it's a networking issue. If not, probably (not definitely) a windows/PC side issue. I've no reason to think there is anything on Unraid side.
-
Cannot access webgui, dockers, SSH from specific computer
Be sure your computer is not connected as Guest network.
-
Unraid not getting IP after a reboot
In storytelling, this is called foreshadowing.
-
Cannot validate Unraid Trial key
Verify internet connectivity. Can you ping google.com? Ip addresses either by router DHCP or manually. (IP address, gateway, subnet, and dns IP) DNS IP: 1.1.1.1 or 208.67.220.220 are good ones. Set time in bios to UTC time. Post diagnostics to give us more info to work with.
-
Replacing HDD with SSD except parity disk
Trim is for SSDs. If they are in the array, trim wont work and the SDDs will start having problems. An alternative would be to get your SSDs and set them up in a pool. ZFS is a fairly new shiny in Unraid and should get you where you want to go. I believe if you are running the Unraid 7 beta that you don't even need any array drives.
-
Replacing HDD with SSD except parity disk
No trim function for array drives.
-
Docker won't start / Drive mounted read-only or nearly full when its not
If you have or can get a Plex backup, then blow it away and start over after doing what JorgeB suggest. Restore Plex backup and call it a day. If unable to get a backup, you may be configuring Plex manually. Shouldn't be too tough as your libraries should be just fine. Krusader don't need anything but a fresh install.
-
Expand storage server - suggestions
I am testing with what looks like that exact device (here) on an ASrock 780 It seems to add 1-2W of energy consumption if installed but not hosting drives. So that's nice. Using 4 Exos HDDs, I am not noticing any bottleneck so far. I do recommend you verify the firmware on it as they have been known to ship very out of date. Here is the tool and an with an older update link. Attached is the most current ASM1166 firmware I could find, Nov2022. Also, when plugging in SATA cables, either do that before installing the card on MB, or be sure you are supporting it when plugging it in. The backplane wants to bend a lot when pushing on it. 11180000.rom
-
Unable to Rest Password
The default login is root with no password. Did that not work?
-
Unraid Won't Boot on new PC
Try formatting thumb drive with Rufus and then copy the Unraid files to it. Rufus settings: Boot Selection = FreeDOS Volume Label = UNRAID File System = Large FAT32
-
Unraid 6.12.8 - Drives won’t stay spun down.
That's a rough go of things. Hope quiet stability is your future now.
-
Removing a data drive.. what happens to disk numbers?
-
Unraid 6.12.8 - Drives won’t stay spun down.
Looks like I learned something.
-
Unraid 6.12.8 - Drives won’t stay spun down.
Maybe try recreating a new share for them for backup. New share, ONLY used for bu... It's a stretch but I'm quickly running out of ideas.
-
Unraid 6.12.8 - Drives won’t stay spun down.
Have you tried skipping one of those win backups? Curious if those drives do or don't spin up at half past the hour if no backup taking place
-
Unraid 6.12.8 - Drives won’t stay spun down.
I'm more of an adaptec guy for my hba so I can't suggest where or how to check there
-
Unraid 6.12.8 - Drives won’t stay spun down.
Maybe something with the lsi card starting them all up when the backup starts it's thing.
-
Unraid 6.12.8 - Drives won’t stay spun down.
Those spin up entries and spin downs in the earlier diagnostic were sandwiched by some sort of plugin error, I cannot recall it exactly now. There were also the Fixcommonproblems errors in vicinity. I would try removing all the plugins you can and see if it makes a difference. Like you, I'm having a hard time seeing how windows backups on a single drive can be causing this.
-
Unraid 6.12.8 - Drives won’t stay spun down.
In your Fix Common Problems plugin... check if 'Avoid spinning up disks for tests?' is set to skip tests on spun down disks. Also even try removing the plugin for a day.
-
ASM1166 brakes ASPM
This was hard to find so sharing. ASM1166 firmware 221118 (Nov2022) 11180000.rom
-
Change disk pool from 2 to 1?
Had this box open for hours while doing life and crafting the above. Now I see the process put up a while ago. Still leaving this here since I did it specifically for the thread. Should be a cinch if still needed for btrs anyway. Punching out now. GL
-
Change disk pool from 2 to 1?
I went back and did this process twice. Needed to get it right after putting out bum info so I made this. Here is how I got there: 1. With array started, go to the Main tab and scroll down and find the Balance button. Next to that, there is a drop down selection. Select the Convert to raid1 mode' option. 2. Click the Balance button. (If you are already in Raid1 then it will be instant). 3. Stop the array. 4. Unassign both cache drives by selecting the drop-down 'no device' choice. 5. Then change slots drop-down to none. 6. Start array. 7. Stop array. 8. Click Add Pool button and click Add. (just a single device in the pop-up) 9. Select the drive you want to keep as a single cache drive. 10. Start array. 11. Go near bottom of main tab and find Format button. To the left you should see your drive s/n that you wish to keep as your cache. Be sure this is the ONLY drive listed. Other drives will also be formatted and lose their data. 12. Check the 'Yes, I want to do this' box to the right. 13. Click Format. 14. Wait a bit for it to complete. Took mine about 2 minutes for an old Sandisk 120GB SATA drive. 15. Verify your data is intact. If it is not, then mount the removed drive with Unassigned devices and copy the files over with MC (or something you prefer) Bonus: Possibly not necessary. *Verify your shares are all mapped correctly. 16. Replace your outgoing cache drive with your new drive and assign as required.
-
Help understanding log
Ah. Thank you for that.