i switched to systemd, but i didn't have systemd-sysvcompat, and i think that i may have some extra line in my syslinux.cfg. when i boot up, i get the following error:
Root device mounted successfully, but /sbin/init does not exist.
and then all that appears is:
how should i proceed?
by the way, i don't have any installation media on me.
Last edited by anti-destin (2012-08-03 20:40:17)
Add "init=/bin/systemd" to your kernel line.
how can i edit it? i can't get into my system.
You don't have any live media or rescue CD/USB? (you don't need the install media, just something that can boot) What can you do at that "rootfs" prompt?
Last edited by 2ManyDogs (2012-08-03 20:33:03)
i have no live media on me at the moment.
i can't do anything at the rootfs prompt, or at least i'm not sure what i should be trying.
Should be able to edit the kernel line through your bootloader. I use Syslinux, so just pressing tab on the menu item allows me to edit it.
If a kernel parameter is the issue, just press Tab at the syslinux menu to modify the details of the selected entry.
Last edited by alphaniner (2012-08-03 20:39:05)
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
thank you, pres (and alphaniner)! that worked perfectly.
By the way, you are really living on the edge if you only have one computer and no boot-able media lying around .
I tried to edit the booting kernel as offered/explained above and didn't resolve my boot.
I do believe this is a hard-disks issue due to systemd. But I also believe it can be caused by VirtualBox.
I'm (was) planning to install Arch on 2 old machine. They each have 2-3 old small HDDs (10GB to 40GB each with WinXP installed on one disk respectively, and both are dual booting with CrunchBang) So, when fisrt experimenting, I tried Arch install on a setup as my old pc on a Vbox. Fsck was hanging(full stop) at reboot. Changing HDD setup to simplify it cause it to hang at shut down (with a "giving up" message) either with arch or archbang or bridgelinux. Those were on virtual-fixe vdi drives. And now, with 3 virtual-expendable clean drives with "sda1 as /, sda2 for 950mb swap, sdb1 as /usr, and sdc1 for /home", I get this "you are on your own" as a welcome ahahahah
I'm only doing this as fun. I like to get my hands dirty at something. Beside, distro-hopping got me to Arch now. I like arch and archbang. It is fast, and not that difficult to resolve when bugs/crash comes along
I have another setup in mind for vbox. If that does not, I'll setup one of my old pc with some other HDDs laying around and see what this does, or does not
Create a new topic about this, this one has been marked as solved so you probably won't get any additional support here.
Mobo: ASUS P8Z77-V PRO // Processor: Intel Core i7-3770K 3.4GHz // GFX: nVidia GeForce GTX 970 Ti // RAM: 32GB (4x 8GB) Corsair DDR3 (@ 2133MHz) // Storage: 1x 3TB Seagate SATAII 5x 1TB Samsung SATAII, 2x 120GB Corsair SSD
Making lemonade from lemons since 2015.