failed to boot after pacman -Syu

This forum is for all other ARMv5 devices

failed to boot after pacman -Syu

Postby pogoman » Tue Jul 17, 2012 6:02 am

my current system failed to boot after update.
Then I tried to download the latest rootfs, and was able to boot up, and again after a full update, the system would fail to boot.
pogoman
 
Posts: 8
Joined: Fri Feb 03, 2012 3:13 am

Re: failed to boot after pacman -Syu

Postby pogoman » Tue Jul 17, 2012 6:28 am

it ends up blinking with a different color, and network is not up.
I have repeated a few times, and it is reproducible.
pogoman
 
Posts: 8
Joined: Fri Feb 03, 2012 3:13 am

Re: failed to boot after pacman -Syu

Postby MrSmith » Tue Jul 17, 2012 8:27 am

I have the same problem. Yesterday i have done "pacman -Syu". After reboot network connection was lost. Haven't tried to new rootfs yet.
My Setup is:
PogoPlugPro Boot from SATA, latest rootfs and kernel
I am updating the system almost daily, usually it always works, but yesterday it didnt survive reboot.
MrSmith
 
Posts: 4
Joined: Tue Sep 27, 2011 8:29 am

Re: failed to boot after pacman -Syu

Postby WarheadsSE » Tue Jul 17, 2012 12:19 pm

This is a kmod change issue.

mv /lib/modules /usr/lib/modules
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: failed to boot after pacman -Syu

Postby pogoman » Tue Jul 17, 2012 9:10 pm

this fixed the issue now.
but still some applications won't work properly.
and might be due to the permission of /dev/
such as random, urandom, null, zero, the permission is 600, other users won't be able to read/write to them.
pogoman
 
Posts: 8
Joined: Fri Feb 03, 2012 3:13 am

Re: failed to boot after pacman -Syu

Postby Philoo » Tue Jul 17, 2012 9:19 pm

yup the problem apparently comes from upstream. broke 3 configs over the week end including a 686 system.
http://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/

it is a not TOO bad to fix but a pain deal with. worst case you transfer the storage to a working system and manually do the copies and symlinks before you put it back to your arm device.
Philoo
 
Posts: 102
Joined: Wed Aug 10, 2011 9:20 pm

Re: failed to boot after pacman -Syu

Postby WarheadsSE » Wed Jul 18, 2012 1:25 am

Annoying: yes

Bad Timing: Yes

Simple Fix: Thank the gods
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: failed to boot after pacman -Syu

Postby steets » Wed Jul 18, 2012 6:05 am

$this->bbcode_second_pass_quote('pogoman', 's')ome applications won't work properly.
and might be due to the permission of /dev/
such as random, urandom, null, zero, the permission is 600, other users won't be able to read/write to them.

I have the same issue. This fix didn't work for me (couldn't ssh after reboot).

Also, "pacman-key --init" never finishes. The cause seems to be insufficient entropy. However, the proposed fix (repeatedly run "updatedb" or "ls -R /" in parallel terminal to increase entropy, did't work for me. I guess it may be related to the /dev/random permessions issue.
Last edited by steets on Wed Jul 18, 2012 6:38 am, edited 1 time in total.
steets
 
Posts: 6
Joined: Tue Jul 17, 2012 7:15 pm

Re: failed to boot after pacman -Syu

Postby steets » Wed Jul 18, 2012 6:37 am

$this->bbcode_second_pass_quote('WarheadsSE', 'T')his is a kmod change issue.

mv /lib/modules /usr/lib/modules

I am sorry to report that this didn't work for me: green/amber fast-blinking LED and not able to ssh after reboot.

Although it is a bit of cross-posting, maybe the following helps.

I installed ArchLinuxARM-oxnas-latest.tar.gz on my PogoPlug Pro, which worked fine. But after "pacman -Syu" and reboot I would get a green/amber fast-blinking LED and not be able to ssh. After a long search, installing packages individually and rebooting after every single one, I figured out that the problem was in kmod, and "pacman -Syu --ignore kmod" allowed me to ssh after reboot.

Trying the fix in the above thread I found that "depmod -a" did not work for me:
$this->bbcode_second_pass_code('', '
ERROR: could not open directory /usr/lib/modules/2.6.31.6_SMP_820: No such file or directory
FATAL: could not search modules: No such file or directory
')
However "pacman -S linux" now worked fine, where before it would say (from pacman.log):
$this->bbcode_second_pass_code('', '
[2012-07-17 16:48] Running 'pacman -S linux'
[2012-07-17 16:48] >>> Updating module dependencies. Please wait ...
[2012-07-17 16:48] ERROR: could not open directory /lib/modules/3.1.10-12-ARCH: No such file or directory
[2012-07-17 16:48] FATAL: could not search modules: No such file or directory
[2012-07-17 16:48] upgraded linux (3.1.10-11 -> 3.1.10-12)
')
WarheadsSE replied in the above thread:
$this->bbcode_second_pass_quote('WarheadsSE', 'N')o, the oxnas DOES NOT RUN "linux" package @ 3.1.10-12

I am going to attempt to make a "clean" package for the oxnas.. it's not going to be fun.

If I can do anything to help fix this issue, please let me know.
steets
 
Posts: 6
Joined: Tue Jul 17, 2012 7:15 pm
Top


Return to Community Supported

Who is online

Users browsing this forum: No registered users and 2 guests

cron