-
Posts
19355 -
Joined
-
Last visited
-
Days Won
53
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by itimpi
-
-
3 minutes ago, GrimD said:
it shows as one partition in every windows tool I have so quite sure it is only one.
Interesting! I only get 1 partition showing with the blkid command on my Unraid system so somehow a difference has crept in. Be interested to see what any others experiencing this issue show as the output of the blkid on their systems or if the apparent difference is a red herring.
I would guess we must be getting around the time that Limetech folk come online (being US based) so maybe they will have something useful to say
- 1
-
4 minutes ago, GrimD said:
@JorgeB One of the few things I haven't tried but but the same drive with no changes (other then coping the install files across) works fine with 6.9.2 so why would\should it be an issue for 6.10?
No idea, but it is something different to what I normally expect to see. Limetech may have an idea when they see the screenshot.
It could be worth trying to see of you can get the drive formatted with a single partition to see if it then boots?
if it does turn out to be related to having 2 partitions in some way it might explain why only some people are encountering this issue.
-
That screenshot shows there are two partitions on the drive sda1 and sda2. Normally there would be only one partition (sda1) and that would be the one labelled UNRAID. Not quite sure what caused you to end up with 2 partitions, but it could well be what is causing the booting problem.
-
3 hours ago, dumurluk said:
"waiting up to 30 sec for device with label UNRAID to come online"?
I mean, it is booting off of the usb drive up to that point. And the usb drive is clearly labeled "UNRAID".
This message has always occurred in all Unraid versions if the USB cannot be found at step 4 of the boot process (described here) but what is not clear is what has suddenly stopped the flash drive being found for some people.
As far as I know this was not an issue for the many rc releases that preceded the ‘stable’ one. Not clear if this is a specific hardware combination causing this that nobody running an rc release happened to have, or if there is some last minute change since the last rc triggering it.
-
14 minutes ago, Bouxer said:
Btw, will the iGPU and/or driver behave differently in Unraid with a display dummy plug?
Not sure, but is is unlikely to cause a problem and may just help depending on how the GPU reacts if it does not detect a display.
-
23 minutes ago, Bouxer said:
The only change I’ve made is apply an XMP profile.
Technically this is an over lock of the RAM so can always cause unexpected side-effects.
-
1 minute ago, casperse said:
So IGFX always worked before? - I am not using it for anything like transcoding
Any idea why IGFX doesn't work anymore?
No idea I am afraid - maybe somebody else will have an idea.- 1
-
1 minute ago, casperse said:
But I can se that no plugin in safe mode also stops the GUI?
So how to boot with GUI and not load any plugin to verify if a plugin is causing this error?
Safe mode does not stop the GUI running unless your system NEEDS a particular plugin to get GUI mode to work.
You can also stop plugins running by renaming the .plg files on the flash drive to have a different file extension. This can allow you to experiment with different combinations of plugins being loaded.
-
5 hours ago, casperse said:
would safe boot do that
Safe Boot stops any plugins from being installed.
-
2 minutes ago, hawihoney said:
So please expect my feature request in a day about how to start/stop/pause/resume/query parity checks from within user scripts via UR
Are you trying to do something that is not already supported by the Parity Check Tuning plugin? If so please describe exactly what it is so I can decide if it is a feature that is worth adding.
-
Just a small point you can still spin down individual disks by clicking on the spindown option there even though the global option is not enabled.
I assume that what you are seeing is because an assumption was made that it does not normally make sense to spin down the disks in the middle of a parity check
- 1
-
That seems a not uncommon problem. It is as though on some systems the bz* type files are not written out correctly.
-
I also notice a lot of items appear to be loaded via Nerdpack and it is possible one of them is not compatible with this release. It might be worth running in Safe Mode for a while as this would suppress any plugins runningand if that works it will give you a starting point for further troubleshooting.
-
3 hours ago, sjaak said:
unraid detected an unclean shutdown and doing a parity sync... its wasn't unclean, it was just a normal reboot
A normal reboot will be considered unclean if the array did not get stopped before the shutdown timers activated.
it might be worth reading this section of the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.
- 1
-
3 hours ago, blaine07 said:
When sever came back online it kicked off a parity check on its own. Is that normal behavior for RC4? I don’t think I’ve ever seen it initiate parity check on a clean reboot before?
That means Unraid thinks the reboot was not actually clean
You might find this section of the online documentation that can be accessed via the Manual link at the bottom of the GUI to be of use?
-
7 minutes ago, Gingko_2001 said:
managed to revert back to RC2, but can't boot into normal server Mode, only safe mode.
Every time boot up, about 3 seconds, it shuts down by it self.
please help!!! and tell me what is wrong with my configurations, attached my diagnostics file.
The screenshots shows that the normal shutdown script has been triggered. This will either be something you are running that calls the script or something obscure that makes Unraid think you have made a short press on the power switch.
If it boots OK into Safe Mode then it will almost certainly be one of your plugins.
-
I have found that sometimes simply downloading the .zIp file for a release and then extracting all the bz* type files and overwriting the ones on the flash fixes such issues. It is as if the upgrade process does not always write these out error free. If you want to try this then the zip file can be downloaded via this link
-
3 hours ago, Squid said:
Yup. My bad. I had to edit the URL slightly (add the -) after posting it. Let the spanking begin.
Do you we should recommend that Limetech provide the download link for the zip file as part of the announcement for beta/rc releases? Would avoid this sort of issue.
-
1 hour ago, ChatNoir said:
and I don't see a difference
There is difference! The link posted is slightly different to the displayed value (the underlying link has missing - character).
- 1
-
11 hours ago, eatoff said:
Any word on what Kernel version is going to be in stable? Looks like 5.15 adds support for quite a few CPUs/GPUs, and some compatibility improvements for Ryzen 5000 series.
No idea on final version, but there has already been comments that rc3 will have the 5.15 kernel (or later I guess).
- 1
-
You should provide a copy of your diagnostics so we can get a better idea of what happened. It would also be a good idea to provide a copy of /etc/cron.d/root so we can see how the schedule has been set.
BTW: It is normally recommended that scheduled checks are set to be non-correcting.
-
4 hours ago, Squid said:
You need to include your diagnostics for this.
There's a few containers out there that seem to have issues when their data files / appdata is set to /mnt/user/... but work perfectly with /mnt/user/...,
Should the second /mnt/user/... actually be /mnt/cache/... ? Does not seem to make sense otherwise
- 1
-
1 hour ago, bonienl said:
Next Unraid version will have the correct values when parity check is paused and resumed.
Just for interest will this be for the whole run or just the last increment? Just asking to see if I might need to revisit the code in the Parity Check Tuning plugin that tries to give the correct values for the run as a whole.
-
5 hours ago, MyKroFt said:
have the latest version of extraputty, what else can i do, my keys no longer work after this upgrade
Did you see the post from Limetech that said:
QuoteNote: recent update to openssh may cause certain clients, eg, PuTTY to not connect using public/private keys.
You may see this in the system log:userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]
You might get hit by this if using an older version of PuTTY.
Maybe this is your issue because as far as I can see extraPutty has not been updated for some time.
[6.10.0] Unraid boot device not found
in Stable Releases
Posted
That indicates there is actually no specific partition on the drive (as that would be sda1).