View Full Version : [VU+ Ultimo4K] Image manager
Hi
Ultimo 4K on the latest image won't do an image backup. I do backups fairly regularly but since the latest upgrade, the backup hangs whilst "Backing up root file system" It generally takes around 5 mins but after about 20 mins I get a timeout error, which I 'ok' but the process keeps running (going by high cpu usage) until I reboot. I have tried doing an image backup several times but it always ends this way.
Backup manager still works ok.
Thanks :)
Hi
Ultimo 4K on the latest image won't do an image backup. I do backups fairly regularly but since the latest upgrade, the backup hangs whilst "Backing up root file system" It generally takes around 5 mins but after about 20 mins I get a timeout error, which I 'ok' but the process keeps running (going by high cpu usage) until I reboot. I have tried doing an image backup several times but it always ends this way.
Backup manager still works ok.
Thanks :)
Can you turn on debug logs menu/setup/system/Logs/settings -> enable debug logs and also save logs to HDD or usb
Run the image backup and then post the log here? (Use e.g. filezilla to transfer the log from /media/hdd/logs or /media/usb/logs )
I have done as you suggested. I rebooted, ran image manager up to when it timed out, quit it and rebooted again.
Log here:
Are you recording or time shifting at the same time of the backup?
Are you recording or time shifting at the same time of the backup?
Yes he is !
I have done as you suggested. I rebooted, ran image manager up to when it timed out, quit it and rebooted again.
Log here:
So have a look in this directory /media/hdd/imagebackups/openvix-vuultimo4k-release-temp and let me know the size of the files.
ImageManager has backed up the main elements (kernel & root) and is trying to compress the root.
So what is attached as /media/HDD? is it internal or external?
How much space is left on the device? If it is external is it powered?
Do you have a lot of plugins etc installed?
Basically ImageManager appears to have run out of time (900 seconds), so either the root is really big, or there is an HDD issue (space, disk activity or its not self powered)
Yes he is !
Haha thought so didn't know if that was timing it out
Are you recording or time shifting at the same time of the backup?
Not to my knowledge? There were no recordings taking place and I had just rebooted so wasn't in timeshift. When I rebooted after it had timed out I didn't get any warnings about recordings in progress or anything else.
After it has finished I am left with 3 folders in the directory. If I try to delete the folder 'openvix-vuultimo4k-release-mount', it crashes and does a gui restart and will keep doing that every time I try to delete the folder until it gets a full reboot. After a reboot, I can delete the folder without a problem.
I have tried saving to hdd and usb, same with both. 2 Tb (internal) hdd has 78% free, not many plugins installed at all, if any.
Do you have permanent timeshift switched on?
Do you have permanent timeshift switched on?
Yes, enabled after 5 secs, saved to usb
Not to my knowledge? There were no recordings taking place and I had just rebooted so wasn't in timeshift. When I rebooted after it had timed out I didn't get any warnings about recordings in progress or anything else.
After it has finished I am left with 3 folders in the directory. If I try to delete the folder 'openvix-vuultimo4k-release-mount', it crashes and does a gui restart and will keep doing that every time I try to delete the folder until it gets a full reboot. After a reboot, I can delete the folder without a problem.
I have tried saving to hdd and usb, same with both. 2 Tb (internal) hdd has 78% free, not many plugins installed at all, if any.
You certainly had timeshift running at the time .... how responsive is the box to remote commands at this point - the box seems to be having some resource issues.
I have never had an issue deleting the temporary folder after this sort of issue (and I have had this many times when setting up a new receiver prior to releasing a new version to ViX) - you say it crashes in which case you should have crash logs??? Can you post them here? The fact that you cannot delete indicates some disk error which is cleared by the reboot.
In between times - although perhaps illogical (?!), can you remove the usb stick , transfer the timeshift to the hdd and try imagemanager again (if you have picons on the usb either run without (preferable) or copy to the hdd for the time being)
Also whats in flash memory (you might check menu/infomation/memory to see what is available to use)
I had timeshift running but I can't see how I was in timeshift because I went straight into the menu and ran image manager as soon as the box had booted up. I didn't change channel or pause it at all.
Crash log: 58698
Edit: removed the usb stick and changed timeshift to hdd, same result.
One thing I noticed was that whilst image manager was running I had a very brief spinner every minute or so which doesn't usually happen.
I had timeshift running but I can't see how I was in timeshift because I went straight into the menu and ran image manager as soon as the box had booted up. I didn't change channel or pause it at all.
Crash log: 58698
Edit: removed the usb stick and changed timeshift to hdd, same result.
One thing I noticed was that whilst image manager was running I had a very brief spinner every minute or so which doesn't usually happen.
So I am assuming you have a hardware issue on the HDD. The crash log shows that the device is busy and stays that way until the reboot resets the channel connection between the receiver and HDD - so I guess its in some error recovery.
The code is common to all receivers and has been the same for a long while ......but also the logs all suggest some hardware issue.
You could try entering via telnet
init 4
umount -a
e2fsck -f -C 0 -v /dev/sdx1
but I guess you are going to have to try to re-initialse (menu/setup/storage/Initialise devices )
looking again at the crash log I am seeing :
<3>[14533.515536] Buffer I/O error on device sdb1, logical block 557056
<4>[14533.521643] lost page write due to I/O error on sdb1
<3>[14533.526640] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
but Iam guessing this is the usb? what dev is your hdd actually on?
It was exactly the same saving to hdd and usb. If the hdd is the issue, then why would it fail when saving to usb? The hdd is only 3 months old and it has never given me a problem.
It was exactly the same saving to hdd and usb. If the hdd is the issue, then why would it fail when saving to usb? The hdd is only 3 months old and it has never given me a problem.
I realise that but can you answer Q‘s on post #13? Whether it has never given an issue or not the log is showing issues
It may or may not be HDD. In theory I wouldn't expect your 3 month old HDD to do this but that doesn't mean it's not that. Could be a new faulty HDD. It's a process of elimination. I have seen HDDs fail that are relatively new before albeit it's rare. This would be covered under warranty if it is a faulty HDD.
If you could do: df -mh
That will tell us whether USB or HDD is mounted as sdb1
You can check for errors with the e2fsck command twol mentioned.
Re-initialising it would confirm it too but be aware you would lose everything on the drive you re-initialise.
I have just usb flashed back to 033, used my settings and image manager worked fine. I tried usb flashing to 034 again and it's still fine! Something must have got corrupted and the reflash cured it. Apologies I didn't try this in the first place :o
Thanks to everyone who tried to help :)
abu baniaz
06-04-19, 00:49
No need to apologise. Thanks for reporting back.
As Abu has said “thanks for responding“ ... makes life easier when you know the outcome!
Update. Same thing happened again after updating from 035 to 036. Image manager hung whilst 'backing up root file system'. I usb flashed 036 and it was fine again.
Thinking about it, the last time it happened was when I upgraded from 033 to 034 and I had to usb re-flash 034
I upgraded from 036 to 037 yesterday and it's ok.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.