-
Posts
10185 -
Joined
-
Last visited
-
Days Won
196
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by limetech
-
-
On 5/21/2022 at 3:14 AM, dlaventu said:
I don’t remember, that was years ago (November 2015), I used what was recommended in doc, it’s working since then and I never touched the flash drive from day one,
I think you win the prize for the longest continuously running USB flash device!
- 1
-
Changed Status to Retest
-
6.10.1 released, please retest
-
Changed Status to Retest
-
6.10.1 released, please retest
-
Changed Status to Retest
-
6.10.1 released, please retest
-
6.10.1 has a fix for this, internal testing now.
- 1
-
6.10.1 has a fix for this, internal testing now.
-
6.10.1 has a fix for this, internal testing now.
-
As a test, please boot in 'safe mode' and see if issue still occurs. If so, there is a misbehaving plugin.
-
@dlaventu - How did you create your current bootable USB flash? Meaning what tool did you use?
-
16 minutes ago, GrimD said:
@limetech Thank you for the explanation that, makes total sense now.
I have just tried using an MBR partition as suggested by a few people and that does work. I would prefer to use GPT though. I'm sure it makes little difference but its one of those GPT is the new hotness type of things, if that makes sense .
Would defiantly be good if you can add that in the next release, I kind of thought that was the whole point of having to label it UNRAID so you could search for and find the correct volume :D.GPT for the flash device is unnecessary and yes, sometimes unintended regressions get introduced into software.
- 1
-
13 hours ago, limetech said:
Nothing has changed in the startup scripts related to this.
Actually not true... pre-6.10 the 'udev' subsystem was started very early. This let us look for which device was assigned to the flash by looking at:
/dev/disk/by-label/UNRAID
which is a symlink which points to a partition, such as 'sda1' or 'sda2'
In 6.10 we have to find the flash device before starting 'udev', so we switch to using 'blkid' to find a device with label "UNRAID". However the code only checks partition 1 label on each device because I've never seen a case where anything other than partition 1 was ever used.
We will add code to check partitions 1, 2, 3, and 4 in the 6.10.1 release. To get your flash to boot now, you will have to reformat and make sure partition 1 is the boot partition with the UNRAID label.
- 2
-
I see what's happening but not sure why yet. From your diags, "lspci.txt" we see this:
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 04)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:0123]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)
Subsystem: PC Partner Limited / Sapphire Technology RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [174b:0123]
Kernel driver in use: r8169
Kernel modules: r8169
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)
Subsystem: PC Partner Limited / Sapphire Technology RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [174b:0123]
Kernel driver in use: r8169
Kernel modules: r8169I 'bolded' the issue above. For some reason the kernel is assigning the r8169 driver to the RTL8125 device instead of the r8125 driver. 'googling' this reveals it's a known issue, eg,
-
We cannot reproduce this.
-
The problem is that the partition containing Unraid config, with label UNRAID, must be partition 1. If you use our USB Flash Creator tool this will be the case. I will provide additional explanation a little later today.
-
Nothing has changed in the startup scripts related to this. Please try this: reboot server and when it gets to the "press ENTER key reboot" prompt, type ctrl-C instead of Enter key. The server will continue boot sequence but since it can't mount the usb flash it won't be able to mount the other bz files, in particular 'bzmodules'. You will likely see a lot of error messages, such as "module bonding not found". Eventually it should present a normal Login prompt. Here you enter 'root' as the username and it should drop right into a shell. At this point, please type:
blkid
And post the output you see from that command.
-
11 minutes ago, SimonF said:
I have found that smGlue is not written to the smart-one.cfg file.
Quick look at the code shows it's being included - @bonienl will have to take a look
-
23 hours ago, knaack said:
I ran into this as well with 6.10. Unfortunately, my Unifi UDM-Pro doesn't let me use anything but RSA. You can add "-oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedAlgorithms=+ssh-rsa" without the quotes after SSH or SCP commands to go back to prior usage.
Obviously not as secure as some other algorithms, but Unifi doesn't seem to care... https://community.ui.com/questions/SSH-Weak-Key-Exchange-Algorithms-diffie-hellman-group1-sha1/7b23bfc9-1482-4b65-bdea-b34968216b29
Thanks for this solution. I want to add to release notes. Can you provide a command example? Also those settings could be put into sshd_conf file as well correct?
-
1 minute ago, BoxOfSnoo said:
After `use_ssl yes` it seems to work as it used to.
What version Unraid OS were you using before and what was he value of "Use SSL/TLS" setting before?
thx
-
1 hour ago, Lilarcor said:
I got the same situation. Maybe ssh-rsa is no longer supported?
Yes, refer to:
https://www.openssh.com/txt/release-8.7
Unraid OS 6.9.2 uses openssh version 8.4p1 and Unraid OS 6.10 uses openssh version 8.8p1
- 1
-
Changed Status to Retest
-
Please upgrade to 6.10 and retest.
Dashboard crash on 6.10.1 - GUI not working anymore
in Stable Releases
Posted
Changed Priority to Minor