unRAID OS version 6.4.0-rc8q available


384 posts in this topic Last Reply

Recommended Posts

1 hour ago, peter_sm said:

I Also have issue to start my VM:s , have created some diagnostics and roll back to previous version and Ishall take a look at my diagnostics files .....


Skickat från min iPhone med Tapatalk

All my UEFI based VM will not start. The Seabios VM is OK.

I'm back on rc7a

//Peter

Link to post
  • Replies 383
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Upgrading: We have changed the way one checks for new unRAID OS releases.  Please refer to Update OS below. Bugs: If you want to report an issue, please start a new topic in this board. New

"rc" means "really close".

Wow......  Didn't see that coming......   Nice one guys!  

Posted Images

1 hour ago, DZMM said:

Not sure what's causing the boot problems, but I can see in my syslog.txt what's slowing my overall boot times which I think I can fix:

 


Sep  3 08:53:04 Highlander emhttpd: shcmd (82): /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php

This locks the machine for about 9 mins, so I guess it's looking for docker updates when there's no internet connection so it's failing - will see if disabling helps


Sep  3 09:12:02 Highlander crond[2837]: failed parsing crontab for user root: ? * FRI * /usr/local/emhttp/plugins/user.scripts/startCustom.php /boot/config/plugins/user.scripts/scripts/Backup Buzz/script > /dev/null 2>&1
Sep  3 09:12:02 Highlander crond[2837]: failed parsing crontab for user root: ? * WED * /usr/local/emhttp/plugins/user.scripts/startCustom.php /boot/config/plugins/user.scripts/scripts/Backup Disney and Lego/script > /dev/null 2>&1

There are a couple of attempts in the logs that cost me about 7 mins each time, for have custom userscripts jobs based on days of week to backup some of my VMs - these keep failing I think because the server isn't sure what day it is - other backup jobs not based on days of the week aren't mentioned, so I'll change these to non-day-of-the week backups.  

 

1 hour ago, DZMM said:

Not sure what's causing the boot problems, but I can see in my syslog.txt what's slowing my overall boot times which I think I can fix:

 


Sep  3 08:53:04 Highlander emhttpd: shcmd (82): /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php

This locks the machine for about 9 mins, so I guess it's looking for docker updates when there's no internet connection so it's failing - will see if disabling helps


Sep  3 09:12:02 Highlander crond[2837]: failed parsing crontab for user root: ? * FRI * /usr/local/emhttp/plugins/user.scripts/startCustom.php /boot/config/plugins/user.scripts/scripts/Backup Buzz/script > /dev/null 2>&1
Sep  3 09:12:02 Highlander crond[2837]: failed parsing crontab for user root: ? * WED * /usr/local/emhttp/plugins/user.scripts/startCustom.php /boot/config/plugins/user.scripts/scripts/Backup Disney and Lego/script > /dev/null 2>&1

There are a couple of attempts in the logs that cost me about 7 mins each time, for have custom userscripts jobs based on days of week to backup some of my VMs - these keep failing I think because the server isn't sure what day it is - other backup jobs not based on days of the week aren't mentioned, so I'll change these to non-day-of-the week backups.  

 

Ok, I've worked out what my 'problem' was with RC7 and now RC8 - it's because of a fix to a RC5 problem that was either not mentioned in the RC7 changelog, or is is the small print.  Or, is in the small print but I didn't realise what the entry meant (more likely!)

 

I just had to change my VM settings back to the friendly name for my nvme drive e.g. /mnt/disks/sm961/domains/  and not /mnt/disks/SAMSUNG_MZVPW256HEGL_00000_S346NY0HC35392/domains/ etc etc, and also in my VM XML files and all was ok.

 

Bonus from this problem though was spotting the problems that were slowing my boot time without a live network - changing the cron job to not reference days and using the inbuilt weekly/monthly schedules and removing the docker auto-update plugin, meant my boot time was normal for the first time in ages and I only had to wait for my pfSense VM to start to get a network - brilliant going from a 30-40mins boot time to under 5 mins!

Link to post
2 hours ago, bonienl said:

 

Any logs?

No logs, but a question, is OVMF firmware updated in this release (OVMF_CODE-pure-efi.fd file) ?

 

We hade this issue in earlier 6.3 for a year ago when we couldn't start VM in UEFI mode and not able to do changes in bios.

Edited by peter_sm
Link to post
2 hours ago, starbix said:

I don't have a backup of that disk, I discovered that even when the drive is emulated by parity it's still unmountable.

It wasn't much data yet, but now I wasted a lot of freeleech tokens :(

If you want help with possibly recovering this data then you should start another thread in General Support since your issue was self-inflicted and unrelated to this release.

 

Link to post
27 minutes ago, Aerowinder said:

All of my share entries are missing in rc8q. Shares still physically present on the drives, and VMs still working. If I click compute all, nothing happens. If I click Add Share, I get a blank white screen. Any ideas?

Untitled.png

 

Whitelist the GUI, if you are using an ad-blocker, and/or exclude the GUI from firewall / anti-virus processing.

 

Link to post
8 minutes ago, eschultz said:

 

It has not been updated.

Thanks for info, I found a syslog for the new rc8q, but I can't found anything why UEFI VM won't run ?

 

It's boots, but stops after some seconds.

//Peter 

syslog.zip

Edited by peter_sm
Link to post

so...  how does one start on a custom port (or is this no longer supported)?  in the past i altered my go file to do the following:

 

/usr/local/sbin/emhttp -p 90 &

but that no longer seems to work (lol, caused me a tiny bit of consternation since i originally thought it was related to all the certificate and/or DNS changes).  I am only able to get to the GUI using the default port (80).

Link to post
5 minutes ago, ajax3712 said:

so...  how does one start on a custom port (or is this no longer supported)?  in the past i altered my go file to do the following:

 


/usr/local/sbin/emhttp -p 90 &

but that no longer seems to work (lol, caused me a tiny bit of consternation since i originally thought it was related to all the certificate and/or DNS changes).  I am only able to get to the GUI using the default port (80).

Have you tried changing the port under Settings->Identification?   This replaces doing it via the ‘go’ file.   If that is not working then you should raise a defect report giving the details.

Link to post
38 minutes ago, trurl said:

If you want help with possibly recovering this data then you should start another thread in General Support since your issue was self-inflicted and unrelated to this release.

 

It is somehow related to this release, as the drive was recognised correctly in rc7a, but yes formatting was my mistake. I have accepted it now :| there was nothing too critical on that drive

Link to post
3 minutes ago, starbix said:

It is somehow related to this release, as the drive was recognised correctly in rc7a, but yes formatting was my mistake. I have accepted it now :| there was nothing too critical on that drive

Post up your diagnostics file.

Link to post
12 minutes ago, starbix said:

I have downgraded to rc7a, so I'm not sure if that would help now. If it still does where do I find it?

The diagnostic file is generated by a script that is run by going to    'Tools'   >>>   'Diagnostics'    The file will be downloaded to the Downloads folders/directory of your web browser. 

Link to post
40 minutes ago, itimpi said:

Have you tried changing the port under Settings->Identification?   This replaces doing it via the ‘go’ file.   If that is not working then you should raise a defect report giving the details.

 

@itimpi, thank you!  Configuring Settings > Identification works for me.  looked under network settings & didn't think to check under identification.

Link to post
5 hours ago, bonienl said:

 

Yes, if you want to make use of the DNS service from Limetech. It is still possible to work the "old way" or make an entry in the hosts file to bypass online DNS service.

 

 

Just to clarify before I update:

 

If I use pfSense as a VM (which obviously runs after UnRAID has booted + array started + VMs started) I will still be able to access the UnRAID UI the way I've always done? I.e. via the IP?

 

I dont want to upgrade and then find it wont boot because there is no internet connection!

 

Thanks :)

Link to post

ok, I'm steering well clear of the new ssl provision page until someone else smarter than me figures it out!  Just had a nightmare couple of hours after figuring out what went wrong with my RC6-->RC8 upgrade.

 

  1. went to settings/identification and thought I'd change the https port to 444 as my letsencrypt docker already using 443.  When I clicked 'done'  (not Apply) in the GUI via my W10 VM, all my VMs stopped immediately
  2. I rebooted ok and went back to the page and thought I'd brave hitting 'Provision' - same again all my VMs stopped
  3. After rebooting, I couldn't access unraid on the usual address and the xxxxxxxx.unraid.net address appeared, but it wouldn't load the dashboard.  I went to the terminal and entered the lines in the OP to reset and rebooted
  4. After rebooting, my pfSense VM now wouldn't start and was stuck in a bootloop.  Luckily I had a recent config backup from yesterday that I restored by building a new pfSense VM and then restoring the config - (I'm glad I've now tested this restore method as it was relatively painless except for waiting for the packages to download)
  5. All is good now

Not sure what happened with 1,2 and 4 but I'm going to leave it now as I've been at this too long now and I think I've got the end goal of being able to access my server from anywhere at the moment via VPN already, although a bookmark would be even nicer.

Link to post
Guest
This topic is now closed to further replies.