On Sun, Jan 18, 2015 at 11:35 AM, Ralf Mardorf
wrote:
>
> HOOKS="base udev autodetect modconf block filesystems keyboard vboxhost"
>
> I removed fsck ;). Use mkinitcpio fsck hook and rw on the kernel
> commandline or don't use the hook and ro on the kernel
> commandline.
I think you missed the po
On Sun, 18 Jan 2015 18:35:13 +0100, Csányi Pál wrote:
> The output of `pacman -S base' command is:
> (50/50) checking keys in keyring
> (50/50) checking package integrity
> (50/50) loading package files
> (50/50) checking for file conflicts
> (50/50) checking available disk space
> ( 1/50) reinsta
On Sun, 18 Jan 2015 11:03:59 -0600, Troy Engel wrote:
> HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck"
HOOKS="base udev autodetect modconf block filesystems keyboard vboxhost"
I removed fsck ;). Use mkinitcpio fsck hook and rw on the kernel
commandline or don't use the
>
> >>Here I exit from the prompt and reboot the machine, but get the same
> >>error message: can't run init.
> >>
> >>What did I wrong?
> >
> > You missed that the base group should be reinstalled, as the error is
> not with the ramdisk,
>
there's no /init outside of the ramdisk, so his problem s
2015-01-18 17:57 GMT+01:00 Oliver Temlin :
> On January 18, 2015 5:49:37 PM CET, "Csányi Pál" wrote:
>>What I did sofar is the following:
>>
>>Boot with Arch linux live cd.
>>lsblk
>>Note: my root / partition is on /dev/sda3
>>mkdir /mnt/arch
>>mount /dev/sda3 /mnt/arch
>>systemd-nspawn -D /mnt/ar
On Sun, Jan 18, 2015 at 10:57 AM, Oliver Temlin wrote:
> On January 18, 2015 5:49:37 PM CET, "Csányi Pál" wrote:
>>mkinitcpio -p linux
>>
>
> You missed that the base group should be reinstalled, as the error is not
> with the ramdisk, but with the files of systemd.
> Just run `pacman -S base' a
On January 18, 2015 5:49:37 PM CET, "Csányi Pál" wrote:
>What I did sofar is the following:
>
>Boot with Arch linux live cd.
>lsblk
>Note: my root / partition is on /dev/sda3
>mkdir /mnt/arch
>mount /dev/sda3 /mnt/arch
>systemd-nspawn -D /mnt/arch
>mkinitcpio -p linux
>
>Here I exit from the promp
2015-01-18 17:02 GMT+01:00 Ralf Mardorf :
> On Sun, 18 Jan 2015 16:30:12 +0100, Oliver Temlin wrote:
>> Just mount your rootfs to /mnt and boot to /mnt/boot and `sudo
>> chroot /mnt', it should be available on your rescue cd.
>
> Assumed the rescue CD should come with systemd, instead of chroot yo
On Sun, 18 Jan 2015 16:30:12 +0100, Oliver Temlin wrote:
> Just mount your rootfs to /mnt and boot to /mnt/boot and `sudo
> chroot /mnt', it should be available on your rescue cd.
Assumed the rescue CD should come with systemd, instead of chroot you
could use systemd-nspawn.
Mount the rootfs and
El 18/1/2015 16:23, "Csányi Pál" escribió:
>
> 2015-01-18 16:19 GMT+01:00 Giedrius Statkevičius
> :
> > On 2015.01.18 17:12, Csányi Pál wrote:
> >> 2015-01-18 16:06 GMT+01:00 Damien Robert
> >> :
> >>> Csányi Pál wrote in message
> >>> :
> I did so but get another error:
> Failed to exe
On January 18, 2015 4:23:45 PM CET, "Csányi Pál" wrote:
>I think I must to chroot into my Arch linux system.
>How can I do that?
Just mount your rootfs to /mnt and boot to /mnt/boot and `sudo chroot /mnt',
it should be available on your rescue cd.
Or if on the arch install media, substitute arch
2015-01-18 16:19 GMT+01:00 Giedrius Statkevičius
:
> On 2015.01.18 17:12, Csányi Pál wrote:
>> 2015-01-18 16:06 GMT+01:00 Damien Robert
>> :
>>> Csányi Pál wrote in message
>>> :
I did so but get another error:
Failed to execute /init (error -2)
>>>
>>> You don't seem to have a valid /us
On 2015.01.18 17:12, Csányi Pál wrote:
> 2015-01-18 16:06 GMT+01:00 Damien Robert
> :
>> Csányi Pál wrote in message
>> :
>>> I did so but get another error:
>>> Failed to execute /init (error -2)
>>
>> You don't seem to have a valid /usr/bin/init anymore, try booting on an usb
>> key and see what
2015-01-18 16:06 GMT+01:00 Damien Robert
:
> Csányi Pál wrote in message
> :
>> I did so but get another error:
>> Failed to execute /init (error -2)
>
> You don't seem to have a valid /usr/bin/init anymore, try booting on an usb
> key and see what happened to it.
>
>> Failed to execute /usr/bin/s
Csányi Pál wrote in message
:
> I did so but get another error:
> Failed to execute /init (error -2)
You don't seem to have a valid /usr/bin/init anymore, try booting on an usb
key and see what happened to it.
> Failed to execute /usr/bin/systemd (error -2). Attempting defaults...
It should b
2015-01-18 15:39 GMT+01:00 Csányi Pál :
> 2015-01-18 15:27 GMT+01:00 Savya :
>>
>> On Sun, Jan 18, 2015, at 11:22 PM, Csányi Pál wrote:
>
>>> I upgrade today my Arch linux desktop.
>>> Later when I did a reboot, on the screen I can to read followings:
>>>
>>> Failed to execute /init )error -2)
>>>
2015-01-18 15:27 GMT+01:00 Savya :
>
> On Sun, Jan 18, 2015, at 11:22 PM, Csányi Pál wrote:
>> I upgrade today my Arch linux desktop.
>> Later when I did a reboot, on the screen I can to read followings:
>>
>> Failed to execute /init )error -2)
>> Kernel panic - not syncing: No working init found.
Hi,
I upgrade today my Arch linux desktop.
Later when I did a reboot, on the screen I can to read followings:
Failed to execute /init )error -2)
Kernel panic - not syncing: No working init found. Try passing init=
option to kernel. See Linux Documentation/init.txt for guidance.
I upgraded my sys
18 matches
Mail list logo
