NFS mount on boot failing after systemd upgrade

Hello,
after upgrading systemd (208-2 --> 208-3), nfs mount on boot will fail. Tested multiple times. After downgrading back to 208-2, all worked fine.
Output of journalctl --reverse:
Dependency failed for Remote File Systems.
Dependency failed for /mnt/demeter.
Dependency failed for File System Check on /192.168.20.70:/data.
Timed out waiting for device 192.168.20.70:-data.device.
/etc/fstab, the nfs line:
192.168.20.70:/data/ /mnt/demeter nfs4 defaults 0 5
uname -a:
Linux eros 3.12.5-1-ARCH #1 SMP PREEMPT Thu Dec 12 12:57:31 CET 2013 x86_64 GNU/Linux
I'm using the latest packages (expect grub, it's the version before the current, because of huge ugrade problems, too).
Greetings,
Sebastian

Ah, big thanks. I thought the last column is the mount order, because it's called "pass". I changed it to zero, and now it works.
Greetings,
Sebastian

Similar Messages

Are nfs mounts allowed in vfstab after a flash archive restore?

I am restoring a server using a flash archive. The vfstab on the original server contains an entry for an nfs mount. It looks like during the push of the archive to the new server, the vfstab gets saved to vfstab.orig and the nfs mount is removed from vfstab. So I added a finish script to add the nfs mount back to vfstab and now the server gets hung during S73nfs.client during reboot.
Are nfs mounts not allowed in vfstab after a flash archive restore?

One option is to secure the OBP with a password.
At the OK prompt, set the security-mode to "command" and then set a password. Careful not to loose this password. With this set the only option is to "boot" without supplying the firmware password.
Commands:
# halt
ok setenv security-mode = command
ok setent security-password <enterpasswd>
ok reset-all

"/usr/lib/cups/backend/usb failed" After Kernel Upgrade

When I upgraded my kernel to 2.6.31.5-1 from 2.6.31.4-1 and tried printing a file, I got this error from cups:
"/usr/lib/cups/backend/usb failed"
The printer was working perfectly fine yesterday.
Upgrade I did today before rebooting my pc to use the new kernel:
[2009-10-27 09:49] upgraded compositeproto (0.4-2 -> 0.4.1-1)
[2009-10-27 09:49] upgraded consolekit (0.3.1-1 -> 0.4.1-1)
[2009-10-27 09:49] upgraded dbus-glib (0.80-1 -> 0.82-1)
[2009-10-27 09:49] upgraded dmxproto (2.2.99.1-1 -> 2.3-1)
[2009-10-27 09:49] upgraded fontcacheproto (0.1.2-2 -> 0.1.3-1)
[2009-10-27 09:49] upgraded pango (1.26.0-1 -> 1.26.0-2)
[2009-10-27 09:49] upgraded shared-mime-info (0.60-1 -> 0.70-1)
[2009-10-27 09:49] upgraded gtk2 (2.18.2-1 -> 2.18.3-1)
[2009-10-27 09:49] upgraded hicolor-icon-theme (0.10-2 -> 0.11-1)
[2009-10-27 09:49] upgraded kbproto (1.0.3-2 -> 1.0.4-1)
[2009-10-27 09:49] upgraded module-init-tools (3.10-2 -> 3.11.1-1)
[2009-10-27 09:50] >>> Updating module dependencies. Please wait ...
[2009-10-27 09:50] >>> MKINITCPIO SETUP
[2009-10-27 09:50] >>> ----------------
[2009-10-27 09:50] >>> If you use LVM2, Encrypted root or software RAID,
[2009-10-27 09:50] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2009-10-27 09:50] >>> More information about mkinitcpio setup can be found here:
[2009-10-27 09:50] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2009-10-27 09:50]
[2009-10-27 09:50] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2009-10-27 09:50] ==> Building image "default"
[2009-10-27 09:50] ==> Running command: /sbin/mkinitcpio -k 2.6.31-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2009-10-27 09:50] :: Begin build
[2009-10-27 09:50] :: Parsing hook [base]
[2009-10-27 09:50] :: Parsing hook [udev]
[2009-10-27 09:50] :: Parsing hook [autodetect]
[2009-10-27 09:50] :: Parsing hook [pata]
[2009-10-27 09:50] :: Parsing hook [scsi]
[2009-10-27 09:50] :: Parsing hook [sata]
[2009-10-27 09:50] :: Parsing hook [usb]
[2009-10-27 09:50] :: Parsing hook [pcmcia]
[2009-10-27 09:50] :: Parsing hook [usbinput]
[2009-10-27 09:50] :: Parsing hook [keymap]
[2009-10-27 09:50] :: Parsing hook [filesystems]
[2009-10-27 09:50] :: Generating module dependencies
[2009-10-27 09:50] :: Generating image '/boot/kernel26.img'...SUCCESS
[2009-10-27 09:50] ==> SUCCESS
[2009-10-27 09:50] ==> Building image "fallback"
[2009-10-27 09:50] ==> Running command: /sbin/mkinitcpio -k 2.6.31-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2009-10-27 09:50] :: Begin build
[2009-10-27 09:50] :: Parsing hook [base]
[2009-10-27 09:50] :: Parsing hook [udev]
[2009-10-27 09:50] :: Parsing hook [pata]
[2009-10-27 09:50] :: Parsing hook [scsi]
[2009-10-27 09:51] :: Parsing hook [sata]
[2009-10-27 09:51] :: Parsing hook [usb]
[2009-10-27 09:51] :: Parsing hook [pcmcia]
[2009-10-27 09:51] :: Parsing hook [usbinput]
[2009-10-27 09:51] :: Parsing hook [keymap]
[2009-10-27 09:51] :: Parsing hook [filesystems]
[2009-10-27 09:51] :: Generating module dependencies
[2009-10-27 09:51] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2009-10-27 09:51] ==> SUCCESS
[2009-10-27 09:51] upgraded kernel26 (2.6.31.4-1 -> 2.6.31.5-1)
[2009-10-27 09:51] upgraded libfetch (2.25-1 -> 2.26-1)
[2009-10-27 09:51] upgraded libgpg-error (1.6-1 -> 1.7-2)
[2009-10-27 09:51] upgraded libpciaccess (0.10.8-1 -> 0.10.9-1)
[2009-10-27 09:51] upgraded libspectre (0.2.2-2 -> 0.2.3-1)
[2009-10-27 09:51] upgraded xf86dgaproto (2.0.99.1-1 -> 2.1-1)
[2009-10-27 09:51] upgraded libxxf86dga (1.0.99.1-1 -> 1.1.1-0.1)
[2009-10-27 09:51] upgraded mlocate (0.22.2-1 -> 0.22.2-2)
[2009-10-27 09:51] upgraded sqlite3 (3.6.18-1 -> 3.6.19-1)
[2009-10-27 09:51] upgraded nss (3.12.4-1 -> 3.12.4-2)
[2009-10-27 09:51] upgraded pcmanfm (0.5.1-2 -> 0.5.2-1)
[2009-10-27 09:51] upgraded perl (5.10.1-3 -> 5.10.1-5)
[2009-10-27 09:51] upgraded pixman (0.16.0-1 -> 0.16.2-1)
[2009-10-27 09:51] upgraded popt (1.14-1 -> 1.15-1)
[2009-10-27 09:51] upgraded pygtk (2.16.0-1 -> 2.16.0-2)
[2009-10-27 09:51] upgraded python (2.6.3-2 -> 2.6.4-1)
[2009-10-27 09:51] upgraded qtcurve-gtk2 (0.69.0-1 -> 0.69.2-1)
[2009-10-27 09:51] upgraded randrproto (1.3.0-1 -> 1.3.1-1)
[2009-10-27 09:51] upgraded recordproto (1.13.2-2 -> 1.14-1)
[2009-10-27 09:51] upgraded tzdata (2009n-1 -> 2009o-1)
[2009-10-27 09:51] upgraded xbitmaps (1.0.1-2 -> 1.1.0-1)
[2009-10-27 09:51] upgraded xcursor-themes (1.0.1-2 -> 1.0.2-1)
[2009-10-27 09:51] upgraded xf86miscproto (0.9.2-2 -> 0.9.3-1)
[2009-10-27 09:51] upgraded xf86vidmodeproto (2.2.99.1-1 -> 2.3-1)
[2009-10-27 09:51] upgraded xineramaproto (1.1.99.1-1 -> 1.2-1)
[2009-10-27 09:51] upgraded xorg-apps (7.4-2 -> 7.5-1.1)
[2009-10-27 09:51] upgraded xproto (7.0.15-1 -> 7.0.16-1)
[2009-10-27 09:51] upgraded xulrunner (1.9.1.3-1 -> 1.9.1.3-2)
Last edited by ShadowKyogre (2009-10-28 01:32:52)

I downgraded the kernel and the printer works again and I forgot to mention I had usblp blacklisted both before and after I upgraded.

A different slow boot scenario after systemd conversion

converted to full systemd a few days ago...my boot times increased instead of going down...the machine still boots, and (mostly) works like before, but so many people are reporting a speed-up without really doing much to earn it that i figured it was worth posting about just to see if someone knows how to help.
details: machine is a 2008 lenovo t61 laptop. i run gdm + openbox, and the graphics are nvidia Quadro NVS 140M.
i list the systemd-analyze output below, but before you look at those i want to stress that the real clock time it takes before i can log in is about 90 seconds, and that MOST of this occurs AFTER what is shown below, when X and gdm are getting themselves revved up to provide the login screen. i am not posting the journalctl output here, but i have looked at it many times and have scoured the forums trying to find some clues. there is nothing in my log files that does not appear in other people's posted logs -- people whose reported boot times are much shorter than mine. i think the solution lies with X and/or gdm, but since nothing is actually broken and there is nothing novel in the log i am at a loss.
systemd-analyze ------> Startup finished in 4531ms (kernel) + 37505ms (userspace) = 42036ms
systemd-analyze blame ------->
15735ms openntpd.service
9623ms systemd-vconsole-setup.service
4872ms colord.service
4039ms accounts-daemon.service
4016ms polkit.service
3891ms dev-mqueue.mount
3584ms gdm.service
3325ms systemd-remount-fs.service
2956ms dev-hugepages.mount
2791ms sys-kernel-debug.mount
2678ms systemd-modules-load.service
2046ms systemd-udev-trigger.service
1881ms systemd-logind.service
1685ms systemd-udevd.service
1590ms home.mount
987ms systemd-sysctl.service
664ms systemd-readahead-collect.service
655ms systemd-readahead-replay.service
494ms dev-sda2.swap
430ms tmp.mount
367ms boot.mount
151ms udisks2.service
96ms rtkit-daemon.service
41ms systemd-tmpfiles-setup.service
4ms upower.service
2ms systemd-user-sessions.service
1ms sys-fs-fuse-connections.mount
any ideas?

You did not share what the kernel panic says, but I guess it has to do with your root file systems not mounted correctly. If it happens like 75% of the time, sounds like you are using /dev/sdax and it gets enumarated differently? Use UUID's instead.
Your "slow boot" is a seperate problem, see the thread you linked too for how to fix that.
Its a fresh install but i alredy have DE and programs, i used Helmuth script to install all the stuff, just so i didnt forget to install stuff.
No idea what this means, but if it is some third party script downloaded off the internet - use them only if you understand exactly what it does, else the chances are you will run into some problems with no idea how you got there. For simply keeping a list of packages to install, put them in a text file and pipe them into pacman (see also here.

Udisks inhibiting fails after system upgrade

Hi,
To keep my cdrom silent I have in rc.local this line:
udisks --inhibit-all-polling &
It worked fine, but stopped working after yesterdays upgrade
Now it (in console) returns:
Inhibit all polling failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
And in kernel.log I found this:
May 29 20:58:27 Mypc2 kernel: [ 2160.206487] INFO: task udisks-daemon:2105 blocked for more than 120 seconds.
May 29 20:58:27 Mypc2 kernel: [ 2160.206491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 29 20:58:27 Mypc2 kernel: [ 2160.206494] udisks-daemon D c109b5e5 0 2105 1 0x00000000
May 29 20:58:27 Mypc2 kernel: [ 2160.206500] f4b29d8c 00000086 f4b29d04 c109b5e5 00000001 00000000 f4a9f980 f533de00
May 29 20:58:27 Mypc2 kernel: [ 2160.206507] f2748400 f533de00 f4b29d14 c127164f 000000c3 f6006380 c14c4380 f4a9f8c0
May 29 20:58:27 Mypc2 kernel: [ 2160.206514] f4a9fa84 f533de48 f533dfd4 c14c4380 f6006380 f4a9f8c0 c142df60 00000000
May 29 20:58:27 Mypc2 kernel: [ 2160.206521] Call Trace:
May 29 20:58:27 Mypc2 kernel: [ 2160.206531] [<c109b5e5>] ? __rcu_read_unlock+0x185/0x190
May 29 20:58:27 Mypc2 kernel: [ 2160.206536] [<c127164f>] ? sock_def_readable+0x5f/0x70
May 29 20:58:27 Mypc2 kernel: [ 2160.206541] [<c11a3a42>] ? kobject_get+0x12/0x20
May 29 20:58:27 Mypc2 kernel: [ 2160.206546] [<c1195a8f>] ? get_disk+0x6f/0x120
May 29 20:58:27 Mypc2 kernel: [ 2160.206552] [<c131ad9d>] __mutex_lock_slowpath+0x10d/0x2b0
May 29 20:58:27 Mypc2 kernel: [ 2160.206556] [<c131af4b>] mutex_lock+0xb/0x20
May 29 20:58:27 Mypc2 kernel: [ 2160.206560] [<c1131447>] __blkdev_get+0x47/0x320
May 29 20:58:27 Mypc2 kernel: [ 2160.206564] [<c1131762>] blkdev_get+0x42/0x290
May 29 20:58:27 Mypc2 kernel: [ 2160.206567] [<c11319fe>] blkdev_open+0x4e/0x70
May 29 20:58:27 Mypc2 kernel: [ 2160.206572] [<c1102e36>] __dentry_open+0xe6/0x300
May 29 20:58:27 Mypc2 kernel: [ 2160.206576] [<c1104186>] nameidata_to_filp+0x66/0x80
May 29 20:58:27 Mypc2 kernel: [ 2160.206579] [<c11319b0>] ? blkdev_open+0x0/0x70
May 29 20:58:27 Mypc2 kernel: [ 2160.206584] [<c111124f>] finish_open+0xaf/0x1a0
May 29 20:58:27 Mypc2 kernel: [ 2160.206587] [<c1110043>] ? do_path_lookup+0x53/0xe0
May 29 20:58:27 Mypc2 kernel: [ 2160.206591] [<c1111838>] do_filp_open+0x1d8/0x6a0
May 29 20:58:27 Mypc2 kernel: [ 2160.206595] [<c11affff>] ? kstrtoll+0xf/0x80
May 29 20:58:27 Mypc2 kernel: [ 2160.206600] [<c115ac27>] ? sysfs_release+0x77/0x90
May 29 20:58:27 Mypc2 kernel: [ 2160.206604] [<c11041f5>] do_sys_open+0x55/0xf0
May 29 20:58:27 Mypc2 kernel: [ 2160.206608] [<c1103569>] ? filp_close+0x49/0x70
May 29 20:58:27 Mypc2 kernel: [ 2160.206611] [<c11042b9>] sys_open+0x29/0x40
May 29 20:58:27 Mypc2 kernel: [ 2160.206615] [<c10037df>] sysenter_do_call+0x12/0x28
I looked at packages that were upgraded yesterday, and here are few that can be relevant to this issue:
[2011-05-28 22:48] upgraded udev (167-2 -> 171-1)
[2011-05-28 22:49] upgraded udisks (1.0.3-2 -> 1.0.3-3)
[2011-05-28 22:51] upgraded kernel26 (2.6.38.6-1 -> 2.6.38.7-1)
[2011-05-28 22:51] upgraded kernel26-headers (2.6.38.6-1 -> 2.6.38.7-1)
[2011-05-28 22:52] upgraded udev-compat (167-2 -> 171-1)
So what might be wrong? Any ideas?
Thanks

What if you disable polling of a specific device with " udisks --inhibit-polling /dev/the_devicename & " ? So without 'all', and using the_devicename that "ps aux | grep udisks-daemon" shows?
And have you tried using and udev rule instead of a line in rc.local? For example I use this to disable polling a card reader:
# /etc/udev/rules.d/02-udev-disable-cardreader-polling.rules
SUBSYSTEM=="block", ENV{ID_VENDOR}=="APPLE*", ENV{ID_MODEL}=="SD Card Reader*", ENV{UDISKS_DISABLE_POLLING}="1"

3gs iOS 6.1.2 call failed - after software upgrade

After the upgrade, i can receive calls, connect to wireless, send texts and play sounds, but cannot make calls.
"Call Failed" is the msg i get wthin a second of dialling.
The signal strength is excellent and since i have tried calling several phones (land and mobiles, with different providers/carriers) within my home, I know they are not busy and it cannot be a network problem.
Any suggestions?
thanks

Basic troubleshooting from the User's Guide is reset, restart, restore (first from backup then as new). Try each of these in order until the issue is resolved.

Yosemite booting fails after erasing and merging bootcamp

I have a MBP 15' retina. I had dual system: mac and windows, but windows failed after upgrading to to Yosemite for obvious reasons so I left it there. Yesterday, I decided to erase my bootcamp and merge it to my mac partition. Everything worked out smoothly as long as I did not reboot. After reboot, Yosemite failed. Here are the symptoms:
Please assist. Thanks

Click on Utilities -> Terminal and post the output of the following Terminal commands. In Recovery console you have to switch between Terminal and Safari.
diskutil list
diskutil cs list
gpt -vv -r show /dev/disk0
fdisk /dev/disk0

PC-Suite sync fails after Firmware upgrade of E65

After firmware upgrade of E65 PC-Suite stops syncing Calendar & Contacts from outlook. No error messages, just "0 entries has been updated".
- PC-Suite updated to 7.0.9.2
- Outlook 2003
- XP Prof.
Any ideas?
Solved!
Go to Solution.

The funny thing is - the notes are synced???? If I restore some old contacts they'll double up in outlook, so I think the problem is, that the sync app doesn't see the outlook contact & calendar folder.
Does somebody has an idea?

Forms and Reports 6i connections fail after db upgraded 10gr2

After database upgraded to 10gr2 on 64bit Windows 2008 server, connections from forms and reports 6i hang while sqlplus connections work. After database is restarted, connections to forms and reports work again but only for a few days?
Also if authenication is changed from NTS to NONE, we do not experience any connection problems from forms or reports.
Any suggestions would be appreciated.
Thanks

Hi!
Is there maybe a database package that gets invalid form some reason?
And if forms/reports tries to connect, the package should get compiled cause of a call
to it and this ends in a endless lock?
Regards

[Solved by itself] Loading module aha152x failed after kernel upgrade

Hi all,
I have a ten-year old Epson GT5500 scanner plugged onto an ISA card.
This was quite hard to get it working under linux but it worked well untill yesterday last update.
I have the following error output when trying to load aha152x module:
# modprobe aha152x
FATAL: Error inserting aha152x (/lib/modules/2.6.27-ARCH/kernel/drivers/scsi/aha152x.ko): No such device
I have the following line in /etc/modules.conf:
alias scsi_hostadapter aha152x options aha152x aha152x=0x140,9
How can I get the scanner back to work?
Thanks.
Last edited by Jeddo (2008-11-15 11:54:12)

fwojciec wrote:Did you build the module yourself? If so you might have to rebuild it for the new kernel version.
No. The configuration to get the scanner working under linux comes from a how-to and remains valid after kernel upgrades -- until yesterday. It does not need any module building, only loading.

Boot fails after pacman -Syu [SOLVED]

Hello forums,
I did a full system upgrade two days ago. Getting this on boot
early console in decompress_kernel
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: running early hook [udev]
:: running early hook [lvm2]
:: running hook [udev]
:: Triggering uevents...
:: running hook [v86d]
:: running hook [xfs]
:: performing fsck on '/dev/mapper/vg_phobos-lv_root'
/sbin/fsck.xfs: XFS file system.
filesystem '' cannot be mounted, unable to open the datases
:: running cleanup hook [lvm2]
:: running cleanup hook [udev]
ERROR: Failed to mount the real root device
Bailing out, you are on your own. Good luck.
sh: can't access tty: job control turned off
[rootfs /]#
LVM is fine and root partition is fine. I can mount it manually from initramfs console.
Running "./init" or exit at the console results in kernel panic, root mounted in /new_root or not.
pacman -Syu went without problems.
Thanks in advance.
Last edited by zb10948 (2013-11-10 18:00:52)

The issue was initcpio ZFS hook. Evidently, if root partition isn't on ZFS the boot breaks.
In this case, ZFS should be handled by systemd service which will mount ZFS partitions from userland.
Procedure :
inside initcpio console, manually mount the root filesystem, chroot to it and run init
mount /dev/path/to/root /new_root
switch_root /new_root /sbin/init
System boots. Afterwards, remove zfs hook from /etc/mkinitcpio.conf and rerun mkinitcpio. Also check that zfs.service system unit is active and enabled.
Last edited by zb10948 (2013-11-10 18:00:37)

Boot fails after pacman -Syu

Hi, I did pacman -Syu and after this the system did not boot anymore.
I noticed 2.6.18 kernel files
First I got problem with master boot block
then I got: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
- As proposed in another topics I tried already:
in /etc/fstab
/dev/discs/disc1/part3 / ext3 defaults 0 1
/dev/discs/disc1/part1 /boot ext2 defaults 0 1
/dev/discs/disc1/part2 swap swap defaults 0 0
changed to
/dev/hdd3 / ext3 defaults 0 1
/dev/hdd1 /boot ext2 defaults 0 1
/dev/hdd2 swap swap defaults 0 0
in /boot/grub/menu.lst
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd1,0)
kernel /vmlinuz26 root=/dev/discs/disc1/part3 ro
changed to
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd1,0)
kernel /vmlinuz26 root=/dev/hdd3 ro
initrd /boot/kernel26.img
and now I got:
Booting 'Arch Linux [/boot/vmlinuz26]'
root (hd1,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz26 root=/dev/hdd3 ro
[Linux-bzImage, setup=0x1400, size=0x2917b71]
initrd /boot/kernel26.img
Error 15: File not found
=============================
- I tried first to change disks/disk1/part3 to change to hdb3 but this failed. then I noticed that a Live boot disk mounted hdd1 hdd2 and hdd3
My bios configuration:
primary IDE controller CD-1
CD-2
secondary IDE controller hd-0 Win
hd-1 Arch
and now I get lost....thanks
fdiks -l tells:
Disk /dev/hdd: 10.2 GB, 10262568960 bytes
16 heads, 63 sectors/track, 19885 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hdd1 * 1 66 33263+ 83 Linux
/dev/hdd2 67 587 262584 82 Linux swap
/dev/hdd3 588 19885 9726192 83 Linux

# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd1,0)
kernel /vmlinuz26 root=/dev/hdb3 ro
initrd /boot/kernel26.img
changed to
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd1,0)
kernel /vmlinuz26 root=/dev/hdd3 ro
initrd /boot/kernel26.img
and now I got:
::Initramfs completed - control passing to kinit
md: Autodetecting RAID arrays
md: autorun ...
md: .. autorun DONE.
this error is gone
Kernel panic - not syncing: Attempted to kill init !
and continues with:
EXT3-fs: mounted filesystem with ordered data mode.
> Archlinux v0.7.2 (Gimmick)
:: Starting UDev Daemon
:: Loading Modules
FATAL: Could not load /lib/modules/2.6.10-ARCH/modules.dep: No such file or directory
shouldn't it be 2.6.18 ?
So it seems that CD on the primary IDE and disks on the Secondary IDE
seems to be a problem for upgrading from v0.7.0 to v0.7.2
Shouldn't I swap the IDE flatcables ?
If I should do this is the kernel26.img right for this new hw configuration ?

Boot Fail after latest BIOS Update on Flex 2-15D

Hi everyone,
I have a severe problem (I guess) after the latest BIOS Update. Windows 7 freezes during startup.
I own a 64-bit Lenovo FLex 2 15D with AMD A6-6310 and R4, 4GB RAM and a SSHD (8GBSSH). I purchased it without OS and installed Windows 7 - which worked fine so far.
I yesterday updated the BIOS with version 9FCN23WW (for Win7 and Win8), the latest BIOS update. A mistake, it seems.
After Reboot, I first had to disable Secure Boot in the BIOS, because it would not let me boot at all. I figured out how to get into the BIOS-Setup to disable this (press Enter 2x, press Tab when in the Boot Menu to access the "Apps Menu", then "SETUP" - just in case this helps someone).
Now Win7 begins to start up, but freezes during the startup process (the splash screen with the win flag freezes and looks a bit strange. I used the "protected mode" Windows Startup and saw that the process always hangs when loading "amdkmpfd.sys".
That is basically it.I guess I have to find a way to re-install the previous version of the BIOS, but I have no idea how!
Any idea?!
Now about what I did to fix this (poor, but I tried):
If I try to start from a Win7 installation CD-ROM (actually it is one for Dell PCs, but I guess that is not the problem) and press a key to boot from CD, Windows loads files, shows "Starting Windows" and at a certain point again just freezes. When I -do not- press a key, WIndows Boot Manager shows up and mentions that "Windows failed to start (etc.)" "File: \EFI\Microsoft\Boot\BCD" "An Error occurred while attempting to read the boot configuration data."
I can't even boot into Linux on a USB stick, because the Windows "Error Recovery" (translated from German, sorry - my guess) won't let me when I try (just offers to boot to Win7 in protected mode - it could be that it fails immediately and jumps back to Win Startup).
Thank you for every bit of help!
Tristam
Solved!
Go to Solution.

I found our the solution to my problem with the help of SebastianLenovo ...
In the BIOS / Boot Mode, I switched back from "UEFI" to "Legacy". That's it. That simple. The BIOS Upgrade routine just did not transfer that setting from the old BIOS to the new.
Given the fact that 1. I did not change that setting, so it is default and 2. it would have been easy to avoid, if the BIOS update routine would be well programmed to transfer the current BIOS settings to the new, upgraded BIOS ...
Anyway a strange situation that a 64-bit system has a 32-bit BIOS. Actually no Linux distribution (except FatDog and rescue systems) are able to deal with it - Linux only running as a Virtual Machine under Windows. I think this is inappropriate and really taking away a part of the fun if you can not run this laptop as a dual boot system.
Thanks to Sebastian and I hope this solution helps someone in the future...
Regards, Tristam.

Boot fails after pacman -Suy

Today I tried to refresh my system using pacman -Suy
After reboot I get the following message:
:: Checking Filesystems [BUSY]
/dev/hda4:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
********* FILESYSTEM CHECK FAILED ********************
* please repair manually and reboot. Note that the root
* file system is currently mounted read-only. To remount
* it read-write type: mount -n -o remount,rw /
* When you exit the maintenance shell the system will
* reboot automatically.
give root password for maintencance
(or type Control-D to continue):
Running e2fsck -b 8193 /dev/hda4
gives the same error message (except the part within asterixes)
Curiously, "fdisk -l" does not give any output at all!
cat /proc/partitions
major minor #blocks name
3 0 58605120 hda
3 1 15727603 hda1
3 2 1 hda2
3 3 104391 hda3
3 4 5245222 hda4
3 5 618471 hda5
3 6 16418398 hda6
3 7 20490876 hda7
cfdisk gives the following error: "FATAL ERROR: Cannot open disk drive"
cat /etc/mtab:
/dev/hda4 / ext3 rw 0 0
/udev /dev tmpfs rw,nosuid 0 0
none /proc proc rw 0 0
none /sys sysfs rw 0 0
cat /etc/fstab
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
sys /sys sysfs defaults 0 0
/dev/hda5 swap swap defaults 0 0
/dev/hda4 / ext3 defaults 0 1
/dev/hda3 /boot ext defaults 0 1
/dev/hda6 /home ext3 defaults 0 1
blkid doesnt give any output either, so I cannot find UUIDs to use in my fstab
the /boot folder is empty, probably hasn't mounted,
but through windows I could locate /boot/grub/menu.lst:
timeout 0
default 0
color light-blue/black light-cyan/blue
title Arch Linux
root (hd0,2)
kernel /vmlinuz26beyond root=/dev/hda4 ro
initrd /kernel26beyond.img
Are there perhaps any irregularities in my setup files, I havent been able to spot any
I have tried anything I know!
Can anyone please help me get my system up and running again?
~Quinten

Did you
mount -n -o remount,rw /
When was your last update? What has been updated?
Can you mount your devices with an arch install cd?
Last edited by ZaQ (2010-03-13 16:42:03)

Boot fails after security update

Greetings,
In installed the most recent security update this morning, and after restarting, my machine won't boot up.
I've followed the existing threads (in case you've also had this problem, the most informative was here:
http://discussions.apple.com/thread.jspa?threadID=1545171 )
Here's my machine's current state; I'd appreciate any input!
I booted to single user mode, and checked the disks using /sbin/fsck -fy . there were no errors reported.
I booted from my Install Disk 1, repaired the disk (again, no errors), and verified the disk.
Now, it still does not boot independently; it stalls at the apple logo. Safe boot does not work. It doesn't appear to be a PRAM or SMC issue.
What should my next move be? Thanks again!

There are no guarantees, but following this procedure when installing updates and upgrades on your Mac, or even re-installing them, will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO or security update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.10 to 10.4.11. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed an OS update and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 used Safari 3.0.4 which was not a beta. If Safari 3.1.1 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 3.0.4 (or worse still, version 2) when running 10.4.11 or 10.5 can have repercussions, as Safari 3.1.1 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely, and may entail you having to reinstall an earlier operating system.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692
To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
• /Library/InputManagers
• ~/Library/InputManagers
especially prior to system updates (they can always be added back one-by-one later).

NFS mount on boot failing after systemd upgrade

Similar Messages

Maybe you are looking for