MeoBoot 2.2 : Can't boot new image from HDD

vindiou

vindiou

Vu+ Newbie
Hi,

I have a Solo2 with BlackHole 2.1.4 + MeoBoot 2.2 installed on my HDD (ext4 filesystem).

A few weeks earlier, my solo2 was running VTI 8.1.
I made a full backup and VTI saved the following files:
vuplus/solo2/root_cfe_auto.bin
vuplus/solo2/reboot.update
vuplus/solo2/kernel_cfe_auto.bin

I zipped these directories/files into a single file called "vti8.1 backup jan2015.zip".
Then I :
- Moved this file into /media/hdd/MbootUpload/
- Relaunched the MeoBoot plugin
- Installed this new image
- Rebooted my solo2

At boot, I see the 2 images, "flash" which are my BlackHole2.1.4 and "vti8.1 backup jan2015.zip".
If I choose the new image, "vti8.1 backup jan2015.zip", nothing happens, the solo2 hangs and I have to switch off/on my solo2 to be able boot again with my original BlackHole image.

Any idea what's wrong?
Why can't I boot my new image?

Thanks!
 
vindiou said:
Hi,

I have a Solo2 with BlackHole 2.1.4 + MeoBoot 2.2 installed on my HDD (ext4 filesystem).

A few weeks earlier, my solo2 was running VTI 8.1.
I made a full backup and VTI saved the following files:
vuplus/solo2/root_cfe_auto.bin
vuplus/solo2/reboot.update
vuplus/solo2/kernel_cfe_auto.bin

I zipped these directories/files into a single file called "vti8.1 backup jan2015.zip".
Then I :
- Moved this file into /media/hdd/MbootUpload/
- Relaunched the MeoBoot plugin
- Installed this new image
- Rebooted my solo2

At boot, I see the 2 images, "flash" which are my BlackHole2.1.4 and "vti8.1 backup jan2015.zip".
If I choose the new image, "vti8.1 backup jan2015.zip", nothing happens, the solo2 hangs and I have to switch off/on my solo2 to be able boot again with my original BlackHole image.

Any idea what's wrong?
Why can't I boot my new image?

Thanks!
Click to expand...


Hi

Try change the name of the zip file to vti80.zip cause i think is lenght name is to long.

Have tried this and it was.

Best regards

Nunigaia
 
First delete the existing non-bootable VTI Image in Meoboot.
I understand that your three files:-
root_cfe_auto.bin
reboot.update
kernel_cfe_auto.bin
are already contained in a folder named solo2 which is
contained in a folder named vuplus.
If yes, zip the vuplus folder and name it as vuplus_usb.zip
FTP the vuplus_usb.zip in /media/hdd/MbootUpload/
Install via Meoboot as usual.
When ready you may then rename the Image as VTI 8.1 from /media/hdd/MbootM/
 
@vindiou

I stand to be corrected but I think that in your case the problem was not actually the length of the zipped Image filename.
Why?
Because if we merely have a lengthy filename, Meoboot would not even allow the Image installation process. It simply informs that the filename is too long and instantly prevents us from installing the Image until we shorten its filename.
Your problem occurred because you used a different foldername other than vuplus.
When you used a different foldername, Meoboot merely unzipped it in /media/hdd/MbootUpload/ but did not actually install anything in /media/hdd/MbootM/.
And after reboot you simply ended up on the Flash Image because the Meoboot Image which you thought you had installed was completely blank which explains why it did not boot at all.
 
Ok.

For now i don´t use meoboot, cause : I think BLACKHOLE is the best image for my VU+ Duo2, and i prefer, for me it takes about 15 minutes to mount all as i have on Vu+ Duo2.

But Few months ago, i´ve tested and the lenght name of zip file ( long kenght name ), don´t let me install the image, until i renamed to a short lenght name.

best regards

nunigaia
 
You must log in or register to reply here.
Back
Top