In my laptop there is a SSD which I decided to finally use. So I made
one big partition out of it, and copied my root file system onto it (cp
-ax, while / was mounted read-only). My root filesystem includes /var
but not /home or /boot. I'm using the actual debian testing.
I made all necessary changes to fstab and grub.
The bootloader still resides on the HDD since for whatever reason my
system doesn't support to boot from the SSD card.
But now when I boot my system it boots correctly, but in the middle of
the boot progress it shows me
...
Setting up x sockets ...
init: entering runlevel 0
...
and it starts stopping all services and at the end switches off the
laptop.
If I choose in the grub menu to boot into recovery mode (runlevel 1),
and just press ctrl+D instead of entering the root password when being
asked for it. It correctly boots to runlevel 2 and starts up the xserver
and everything is working perfectly. It's also using the correct
partitions and everything.
I guessed it could be some kind of timing issue, so I passed the
delayroot parameter to the kernel, but that didn't change anything. Also
telling the kernel explicitly it should boot to runlevel 2 doesn't
change anything. I guess there must be some service or something which
forces the system (or kernel) to shutdown directly.
In syslog I couldn't find anything helpful since it seems like it
doesn't manage to write anything there before shutting down the laptop.
So right now I've got no idea what the problem could be.
I already changed root partitions/disks on a lot of systems. And never
run into this problem.
If anybody could give me a hint into the right direction would be great.
thanks in advance :-)
meier
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/963adc3756931458dea10e69c8772...@rmm.li
