You are not logged in.
This is the second time I tried upgrading linux to 3.13 and both times it gets stuck
[inxsible ~ ]$ pacin linux
[sudo] password for inxsible:
warning: linux-3.13.5-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): linux-3.13.5-1
Total Installed Size: 67.12 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [###################################################################] 100%
(1/1) checking package integrity [###################################################################] 100%
(1/1) loading package files [###################################################################] 100%
(1/1) checking for file conflicts [###################################################################] 100%
(1/1) checking available disk space [###################################################################] 100%
(1/1) reinstalling linux
It stays there for hours. Finally I had to Ctrl+C and then manually run
sudo mkinitcpio -P
Even this gets stuck at the [ autodetect ] module and I have to Ctrl+C it. Then it successfully builds the fallback image. Then I have to relogin via the fallback and re-install linux at which point the installation and generation of the initramfs image goes without a hitch.
I looked at the basic logs and nothing there was the obvious problem. Anyone else seen this ?
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
try with --debug maybe? That will give much more details about where things are failing.
Offline
ok. I might have to downgrade linux first though.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Keep in mind that booting to a live disk/usb might be easier and less permanent than downgrading linux. Using this method, you can simply chroot into your existing system to test and fix everything.
Offline
So this happened to me again when updating the linux package tonight.
As it happens, I have a NFS share that I access from this machine and that machine (a laptop) had been switched off. I saw this in the dmesg
[175434.699141] nfs: server toshiba not responding, timed out
[175630.539122] nfs: server toshiba not responding, timed out
[175811.019135] nfs: server toshiba not responding, timed out
[175874.165762] nfs: server toshiba not responding, timed out
[176054.645744] nfs: server toshiba not responding, timed out
[176174.539067] nfs: server toshiba not responding, timed out
[176355.019045] nfs: server toshiba not responding, timed out
[176415.179042] nfs: server toshiba not responding, timed out
[176598.645693] nfs: server toshiba not responding, timed out
[176658.805684] nfs: server toshiba not responding, timed out
[176899.018994] nfs: server toshiba not responding, timed out
[176959.178987] nfs: server toshiba not responding, timed out
[177142.645635] nfs: server toshiba not responding, timed out
[177202.805628] nfs: server toshiba not responding, timed out
[177446.432271] nfs: server toshiba not responding, timed out
[177506.592266] nfs: server toshiba not responding, timed out
[177750.218905] nfs: server toshiba not responding, timed out
[177810.378902] nfs: server toshiba not responding, timed out
[178054.005540] nfs: server toshiba not responding, timed out
[178114.165538] nfs: server toshiba not responding, timed out
[178357.792199] nfs: server toshiba not responding, timed out
[178417.952174] nfs: server toshiba not responding, timed out
[178661.578812] nfs: server toshiba not responding, timed out
[178721.738811] nfs: server toshiba not responding, timed out
[178965.365450] nfs: server toshiba not responding, timed out
[179025.525446] nfs: server toshiba not responding, timed out
[179269.152089] nfs: server toshiba not responding, timed out
[179329.312083] nfs: server toshiba not responding, timed out
[179572.938726] nfs: server toshiba not responding, timed out
[179633.098718] nfs: server toshiba not responding, timed out
So I switched on the laptop and after a while tried to install the package again and this time it worked. I still don't know why it would need a remote NFS server to be up while installing/upgrading linux locally
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Probably the free space check.
Offline
its definitely pacman configuration because if I manually run
sudo mkinitcpio -P
it runs fine
[inxsible ~ ]$ sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.14.0-5-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.14.0-5-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
[inxsible ~ ]$
I will downgrade again and switch off the free space check and try again.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Ok. I tried upgrading linux and if my NFS server was down, it just doesn't complete regardless of the CheckSpace in pacman.conf. Gets stuck here
$ pacin linux
warning: linux-3.14-5 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): linux-3.14-5
Total Installed Size: 69.47 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [###################################################################] 100%
(1/1) checking package integrity [###################################################################] 100%
(1/1) loading package files [###################################################################] 100%
(1/1) checking for file conflicts [###################################################################] 100%
(1/1) reinstalling linux [###################################################################] 100%
But if I turn on my NFS server and then try, it works with or without the CheckSpace turned on. How do I tell pacman to stop worrying about the remote servers ?
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Where is the NFS share mounted? Please post the relevant part of the fstab.
Offline
You could try using --noscriptlet; I think this is caused by the `depmod` call in https://projects.archlinux.org/svntogit … ages/linux. To debug this; try executing `depmod 3.14-5-ARCH` after running with --noscriptlet. If depmod hangs too; you could strace it to see which nfs-path it attempts to access
Offline
Running it with --noscriptlet finishes it instantly
[inxsible ~ ]$ pacin linux --noscriptlet
[sudo] password for inxsible:
warning: linux-3.14.1-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): linux-3.14.1-1
Total Installed Size: 69.47 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [###################################################################] 100%
(1/1) checking package integrity [###################################################################] 100%
(1/1) loading package files [###################################################################] 100%
(1/1) checking for file conflicts [###################################################################] 100%
(1/1) reinstalling linux [###################################################################] 100%
[inxsible ~ ]$
and running depmod gives nothing really
[inxsible ~ ]$ sudo depmod 3.14.1-1-ARCH
[inxsible ~ ]$
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Okay, this also runs from the scriptlet, could you see how long this takes?
findmnt --fstab -uno SOURCE /boot ; mountpoint -q /boot
Last edited by Spider.007 (2014-04-16 16:44:31)
Offline
it immediately spits out the UUID whether the NFS server is up or not.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline