Hello Everybody. I'm using slitaz cooking ISO Rc 3 from a sandisk 2gb pendrive. I'm a newbie to linux so kindly go easy on me.
what happened was I was using this system fine. I downloaded a package and after that I did writefs.gzip from right click at desktop tazusb live menu. After that as I had read on tazusb docu, I used the clean command to clean old rootfs.gzip files. after that when I started again today, It did start fine, language menu appeared. after that when I chose Slitaz Live to start the system, it didn't boot and there was a "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" error.
the pendrive is in ext3 format so it can't be read on my windows. I guess I'll have to format it and start again. What I want to know is what I did wrong to cause that error? I wanted to have a persistent usb installation. so if somebody can give me some pointers on what I did wrong and what is the right way to do it.
one more question I have is is I chose to use the new rolling build, will I be able to upgrade to new weeks build without losing all the packages I installed?
Thank you very much for you help.
Boot error after cleaning old Rootfs files
(7 posts) (4 voices)- Started 9 years ago by Bhavesh17894
- Latest reply from Bhavesh17894
- This topic is resolved
-
Bhavesh17894
offlineMemberPosted 9 years ago # -
Use writefs(lzma) or writefs(none), it's bug of gzip.
You can also try solution from tazlito to fix rootfs.gzip:
boot rolling iso, enter directory with failed-to-boot rootfs.gz and run two commands
tazpkg get-install advancecomp
advdef -z4 /rootfs.gzIf this will not fix "Kernel panic" on boot, I'm afraid it's impossible to upgrade without losing all the packages installed.
Posted 9 years ago # -
Bhavesh17894
offlineMemberAs I didn't had any more pendrives to boot slitaz into and try those commands you said, I fornatted my usb and again installed 5.0 rc3.
After that i tried that again. Made some changes in packages- Writefs.gzip and rebooted. It was persistent. Then I made few more changes again did writefs.gzip and rebooted. After I made sure that all the changes were there. I cleaned up old rootfs.gzip by tazusb clean, and then rebooted. It worked fine.
So maybe the problem was either a) Last time I didn't rebooted before cleaning up the old rootfs.gzip files, or b) I did something else wrong. Anyways thanks for your help.
One more question, I downloaded the latest rolling iso when I was reinstalling slitaz. I tried uui, tazusb windows, tazusb slitaz but I couldn't boot into the new rolling version. It was always Not a COM32R image error. Do you have any idea about this?
and thanks again for help.Posted 9 years ago # -
llev
offlineMemberHi,
Bellard is an expert on syslinux so he'll probably be able to help on the boot error.
As for your other question about weekly: except in some corner cases, by running
tazpkg upor updating your packages through Tazpanel you get an up-to-date system that's identical to the weekly build.Posted 9 years ago # -
Bellard
offlineKey Master@Bhavesh17894:
1. Syslinux & isolinux can load lzma'd c32 file since http://hg.slitaz.org/wok/rev/ef4ed701a27f
2. You are installing a 2016 slitaz with a pre 2016 tazusbYou can
- unlzma the c32 file : lzma d c32box.c32 c32boot.c32.new ; mv c32boot.c32.new c32boot.c32 (idem with vesamenu.c32)
- or copy the new {sys|ext}linux.bin to your hard diskPosted 9 years ago # -
Bhavesh17894
offlineMemberUMM bellard I really new to linux so I couldn't understand what you said. I have a lot to learn. But thanks for taking the time to reply bro.
I am using the last cooking ISO with all upgraded packages so for now my query is solved.
Thanks all for help.
Posted 9 years ago #
Reply
You must log in to post.
