SliTaz Forum

Guest

Guest

Impossible restart after upgrade

[This is a english (or something like that) translation of a thread I opened without success in the french part of the forum.]

I upgraded my cooking slitaz (a cooking base from march 2011 installed in virtualbox) and I cannot reboot since this upgrade. I have a infinite loop of "Can't open /dev/tty[1 to 6] No such file or directory" on the screen. The first error displayed before that seems to be "Could not open /dev/null read-only filesystem".

I tried to boot in single user mode but the mounting is done also in read-only mode.

I tried to add rw after the kernel in grub at start; no success.

I chrooted from the livecd, but I didn't see what to do next: the nodes are present in dev, as they are built by the livecd boot. I tried to reinstall udev. No change at reboot.

Has got anyone an idea?

For me, this is the principal problem of delaying 4.0; if you use cooking, you can have this kind of problem with an upgrade. You cannot avoid to upgrade for security reasons, then what to do? Is the rolling release of slitaz less problematic with upgrade?

Trixar_za

Administrator

Registered: 2011-03-29

Posts: 1,506

Re: Impossible restart after upgrade

It may be because your version of cooking is old. There has been major changes, including a more modern use of udev and the inclusion of tazpanel and tazweb.

And why it's not booting correctly tells me that it's not further than  the e2fsck stage in your /etc/init.d/rcS file, which may have been caused by a faulty upgrade which overwrite - or should I say half wrote - that file.

The rolling release is more current, but it doesn't mean it will work with all machines, just that it complies. Is it better than that OLD cooking you're using? Most definately.

Also FYI, I've seen a few distro's upgrade function break it. It's not just a SliTaz problem...