[Solved] Cant boot the kernel after (--force) upgrade

broi · 2012-03-08 20:46:36

Recently I screwed up my Arch and decided to reinstall it, so I did and first thing I ran is update.

Since my Installation CD is old about 6 months, I had to upgrade 80+ pckgs, and downloading finished and in *checking for file conflict* part I get error:

error: failed to commit transaction (conflicting files)
filesystem: /etc/mtab exists in filesystem
Errors occurred, no packages were upgraded.

I had this problem once before, and, as some of ppl on forums said I should upgrade with --force, I did so and it was alright, but now... After Upgrade I get this msg at boot>

...
Decompressing Linux... Parsing LEF... done.
Booting the kernel.
ERROR: Unable to find root device */dev/sda3*.
You are being dropped to recovery shell
     Type *exit* to try and continue booting
sh: cant access tty: job control turned off
[rootfs /]$ _

And I cant type *exit*, keyboard not work...
This was my second try, so I knew what will happen and I made /etc/mtab a backup which I replaced with afterupgrade one with hope it will run /sda3, but same problem...

Last edited by broi (2012-03-09 18:30:47)

litemotiv · 2012-03-08 20:49:15

You should only --force update the "filesystem" package: http://www.archlinux.org/news/filesyste … -required/

/dev/zero · 2012-03-08 21:01:20

nm, need to ltfr

Last edited by /dev/zero (2012-03-08 21:01:57)

broi · 2012-03-08 22:12:58

litemotiv wrote:

You should only --force update the "filesystem" package: http://www.archlinux.org/news/filesyste … -required/

I just did that update seperately of other packages, then tried to update other without --force but getting this error>
initscripts: /etc/profile.d/locale.sh exists

So I get everything update with --force (but filesystem, its already update), and same shh problem.

broi · 2012-03-08 22:13:42

/dev/zero wrote:

nm, need to ltfr

What?? lol

Last edited by broi (2012-03-08 22:20:56)

Gcool · 2012-03-08 22:16:11

For an explanation of the locale issue, take a look here.

However, if you're doing a fresh install anyways; I would suggest to use the netinstall image instead. That'll save you alot of these sort of problems.

/dev/zero · 2012-03-08 22:19:39

broi wrote:

/dev/zero wrote:
nm, need to ltfr
What??

fyi, nm = "Never mind", ltfr = "learn to fucking read".

I wrote a post in haste, realised my mistake, "nm, need to ltfr" means please ignore me and get on with your life.

broi · 2012-03-08 22:23:01

Gcool wrote:

For an explanation of the locale issue, take a look here.
However, if you're doing a fresh install anyways; I would suggest to use the netinstall image instead. That'll save you alot of these sort of problems.

Thank you, ill follow ur advice.

litemotiv · 2012-03-08 22:24:36

broi wrote:

Gcool wrote:
For an explanation of the locale issue, take a look here.
However, if you're doing a fresh install anyways; I would suggest to use the netinstall image instead. That'll save you alot of these sort of problems.
Thank you, ill follow ur advice.

In this case, don't do a fresh netinstall though, removing locale.sh is the only thing you have to do to get your system back online.

broi · 2012-03-08 22:26:43

litemotiv wrote:

broi wrote:
Gcool wrote:
For an explanation of the locale issue, take a look here.
However, if you're doing a fresh install anyways; I would suggest to use the netinstall image instead. That'll save you alot of these sort of problems.
Thank you, ill follow ur advice.
In this case, don't do a fresh netinstall though, removing locale.sh is the only thing you have to do to get your system back online.

Okay, I will try it now

broi · 2012-03-09 13:27:22

Okay, this what I did after FRESH install. this is solutions thanks to u guys

-There was 80+ pckgs to upgrade, I upgraded ONLY filesystem with --force (and reboot to check if it will boot)
-After successfull boot,tried to upgrade others but problem was locale.sh
-I removed it, upgraded again and it was all ok now.

Installed X etc. etc. It just works as it should, thanks alot!!

Arch Linux

#1 2012-03-08 20:46:36

[Solved] Cant boot the kernel after (--force) upgrade

#2 2012-03-08 20:49:15

Re: [Solved] Cant boot the kernel after (--force) upgrade

#3 2012-03-08 21:01:20

Re: [Solved] Cant boot the kernel after (--force) upgrade

#4 2012-03-08 22:12:58

Re: [Solved] Cant boot the kernel after (--force) upgrade

#5 2012-03-08 22:13:42

Re: [Solved] Cant boot the kernel after (--force) upgrade

#6 2012-03-08 22:16:11

Re: [Solved] Cant boot the kernel after (--force) upgrade

#7 2012-03-08 22:19:39

Re: [Solved] Cant boot the kernel after (--force) upgrade

#8 2012-03-08 22:23:01

Re: [Solved] Cant boot the kernel after (--force) upgrade

#9 2012-03-08 22:24:36

Re: [Solved] Cant boot the kernel after (--force) upgrade

#10 2012-03-08 22:26:43

Re: [Solved] Cant boot the kernel after (--force) upgrade

#11 2012-03-09 13:27:22

Re: [Solved] Cant boot the kernel after (--force) upgrade

Board footer