search

maxnet / berryboot

Berryboot -- Boot menu / OS installer
http://www.berryboot.com/
Other
799 stars 135 forks source link

cant boot into image that added over cifs share #732

Open chrome511 opened 2 years ago

chrome511 commented 2 years ago

when i add an image over a cifs share i cant boot into it. Error: unable to locate or execute /sbin/init /usr/lib/systemd/systemd /init inside NAME_OF_IMAGE.img

when i add the same image with an USB stick, then i can boot into it

symbios24 commented 2 years ago

Then do the second

chrome511 commented 2 years ago

The Image is a self created image based on the bullseye image. This is the image I can't boot after I copied it from the local network repo.

A buster image works fine with the local network repo

symbios24 commented 2 years ago

The image creation method is not correct for bullseye images

chrome511 commented 2 years ago

What is the correct creation method for a bullseye Image?

symbios24 commented 2 years ago

I dont know yet im waiting like you

chrome511 commented 2 years ago

the creation method is the first problem. with an other creation method ist works with the cifs share, but after i create an backup with the berryboot backup option you cant boot anymore if you copy the backuped image over the cifs share back. the berryboot backup option create the image wrong too.

chrome511 commented 2 years ago

the problem is not the creation method and not the backup creation option in berryboot. i have created my own image withe the creation mehod with the official tutorial. i converted successfully the images with this Release date: January 28th 2022. the problem is the filename of the image. if you copy the image to berryboot with the filename bullseye-lite.img for example, then you can boot. if you change the filename from bullseye-lite.img to 1. bullseye-lite.img in the windows explorer for example, the berryboot can´t boot this image anymore.

don´t change the filename of the backuped image.