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)

Similar Messages

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 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)

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

Boot-up fails after pacman update

Recent update of many pkgs failed to load after downloading.
The boot stops at :
Archlinux 0.7 (wombat) [(none)] (vc/1)
(none) login:
Attempts to login fail (probably because I don't know what should go for login)
The hdd can be addressed from another hdd boot-up and all partitions accessed.
It just won't finish boot. :cry:

As posted previously, a recent upgrade was followed by a failure to load the downloaded packages. None of these packages were kernel upgrades and lilo run would not be necessary thereafter.
My fstab and rc.conf follow:#
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
#/dev/#EXT2FS_BOOT# /boot ext2 defaults 0 1
#/dev/#REISERFS_ROOT# / reiserfs defaults 0 0
#/dev/#EXT2FS_ROOT# / ext2 defaults 0 1
#/dev/#SWAP# swap swap defaults 0 0
#/dev/#REISERFS_HOME# /home reiserfs defaults 0 0
#/dev/#EXT2FS_HOME# /home ext2 defaults 0 2
/dev/cdroms/cdrom0 /mnt/cd iso9660 ro,user,noauto,unhide 0 0
/dev/cdroms/cdrom0 /mnt/dvd iso9660 rw,user,noauto,unhide 0 0
/dev/floppy/0 /mnt/fl vfat user,noauto,unhide 0 0
none /dev/pts devpts defaults 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs size=2G,nr_inodes=10k 0 0
/dev/discs/disc0/part3 / ext3 rw,users,exec 0 0
/dev/discs/disc0/part1 /boot ext2 defaults 0 1
/dev/discs/disc0/part2 swap swap defaults 0 0
/dev/discs/disc1/part3 /mnt/drive ext3 rw,users,exec 0 0
/dev/discs/disc1/part1 /mnt/fat1 vfat defaults 0 0
/dev/sdb1 /mnt/fat3 vfat defaults 0 0
/dev/sda1 /mnt/fat2 vfat defaults 0 0
/dev/sda3 /mnt/drive ext3 defaults 0 0
# /etc/rc.conf - Main Configuration for Arch Linux
# Localization
# Note: HARDWARECLOCK is either "UTC" or "localtime"
KEYMAP=us
TIMEZONE=Canada/Pacific
HARDWARECLOCK="localtime"
# Networking
HOSTNAME="n6re"
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
MODULES=(!usbserial !ide-scsi ne2k-pci snd-cmipci
usb-storage sd_mod sr_mod)
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="eth0 216.86.214.121 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 216.86.214.1"
ROUTES=(gateway)
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
DAEMONS=(!pcmcia network crond syslogd klogd kdm)
# End of file
The above files are from the affected HDD.
I note that (none)login: appears with an ID name in place of (none) in this clone HDD when opting for console login from the kde window options, so that element is missing in the other hard drive.
How to replace (none) with the right ID is the problem solution.

"FILESYSTEM CHECK FAILED" after pacman -Syu

Hi all,
After a sucessfull 'pacman -Syu' (in which i didnt see any 'todo' messages but it did have a kernel upgrade) archlinux cannot start and i just get to a message similar talking about my root partition (ext3):
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 *
* filesystem is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the mantenance shel the system will *
* reboot automatically. *
I restarted with a livecd and 'e2fscked' the partition (which btw found many errors that were corrected by it) but archlinux still gives me the same message. I have checked the partition again and again a thousand times but it always comes up clean, im even able to mount it from the different livecds i have tried and can read and create files on it so im pretty sure it is fine.
And so my question is, does anyone know why this is happening? How comes archlinux keeps seeing a problem in this partition when others dont? What am i doing wrong?
An y answer appreciated.
Last edited by feralert (2009-06-03 20:15:23)

Hi again,
I have done some testing, maybe it will help.
After the failure message i put roots password and i got dropped to a shell, if i try to find the root partition (eg. ls /dev/sda) gives an error cause it sda doesnt exists.
If i edit rc.sysinit with a livecd and remove the fsck part i get a few diferent errors, some about partitions not being found and similar stuff. In my little knowledge of linux it ooks to me like it doesnt load the sata module or somethig...
I copy here the pacman.log file, i remember that the update was a huge one, around 400 Mbytes if i remember correctly:
[2009-05-30 22:20] synchronizing package lists
[2009-05-30 22:21] starting full system upgrade
[2009-05-30 22:23] synchronizing package lists
[2009-05-30 22:23] starting full system upgrade
[2009-05-30 23:29] upgraded alacarte (0.11.10-1 -> 0.12.1-1)
[2009-05-30 23:29] upgraded kernel-headers (2.6.27.6-2 -> 2.6.29.3-1)
[2009-05-30 23:29] upgraded tzdata (2009f-1 -> 2009g-1)
[2009-05-30 23:29] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
[2009-05-30 23:29] Generating locales...
[2009-05-30 23:29] es_ES.UTF-8... done
[2009-05-30 23:29] es_ES.ISO-8859-1... done
[2009-05-30 23:29] es_ES.ISO-8859-15@euro... done
[2009-05-30 23:29] Generation complete.
[2009-05-30 23:29] upgraded glibc (2.9-4 -> 2.10.1-2)
[2009-05-30 23:29] upgraded alsa-lib (1.0.19-1 -> 1.0.20-1)
[2009-05-30 23:29] upgraded alsa-utils (1.0.19-1 -> 1.0.20-1)
[2009-05-30 23:29] upgraded binutils (2.19.1-1 -> 2.19.1-3)
[2009-05-30 23:29] upgraded geoip (1.4.5-1 -> 1.4.6-1)
[2009-05-30 23:29] upgraded gcc-libs (4.3.3-1 -> 4.4.0-2)
[2009-05-30 23:29] upgraded libdrm (2.4.9-1 -> 2.4.11-2)
[2009-05-30 23:29] upgraded libgl (7.4.1-1 -> 7.4.2-2)
[2009-05-30 23:29] upgraded mesa (7.4.1-1 -> 7.4.2-1)
[2009-05-30 23:29] upgraded wxgtk (2.8.9.2-1 -> 2.8.10-1)
[2009-05-30 23:29] upgraded amule (2.2.4-1 -> 2.2.5-2)
[2009-05-30 23:29] upgraded x264 (20090216-1 -> 20090416-1)
[2009-05-30 23:29] upgraded avidemux (2.4.4-2 -> 2.4.4-3)
[2009-05-30 23:29] upgraded bin86 (0.16.17-3 -> 0.16.17-4)
[2009-05-30 23:29] upgraded gmp (4.2.4-1.1 -> 4.3.1-2)
[2009-05-30 23:29] upgraded coreutils (7.2-1 -> 7.4-1)
[2009-05-30 23:29] upgraded dbus-core (1.2.4.4permissive-1 -> 1.2.14-1)
[2009-05-30 23:29] upgraded glib2 (2.20.1-1 -> 2.20.2-1)
[2009-05-30 23:29] upgraded bluez (4.37-1 -> 4.39-1)
[2009-05-30 23:29] upgraded gstreamer0.10 (0.10.22-1 -> 0.10.23-1)
[2009-05-30 23:29] upgraded gstreamer0.10-base (0.10.22-1 -> 0.10.23-1)
[2009-05-30 23:29] upgraded gstreamer0.10-base-plugins (0.10.22-1 -> 0.10.23-1)
[2009-05-30 23:29] upgraded brasero (2.26.1-2 -> 2.26.2-1)
[2009-05-30 23:29] upgraded policykit (0.9-7 -> 0.9-9)
[2009-05-30 23:29] upgraded consolekit (0.3.0-3 -> 0.3.0-5)
[2009-05-30 23:29] upgraded cpio (2.9-3 -> 2.9-5)
[2009-05-30 23:29] upgraded curl (7.19.4-1 -> 7.19.5-2)
[2009-05-30 23:29] upgraded dbus (1.2.4.4permissive-1 -> 1.2.14-1)
[2009-05-30 23:29] upgraded dcron (3.2-3 -> 3.2-4)
[2009-05-30 23:29] upgraded dhcpcd (4.0.12-1 -> 5.0.4-1)
[2009-05-30 23:29] upgraded dmapi (2.2.9-1 -> 2.2.10-1)
[2009-05-30 23:29] upgraded docbook-xml (4.5-1 -> 4.5-2)
[2009-05-30 23:29] upgraded gconf (2.26.0-3 -> 2.26.2-1)
[2009-05-30 23:29] upgraded gnome-desktop (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:29] upgraded gdbm (1.8.3-5 -> 1.8.3-6)
[2009-05-30 23:29] upgraded sqlite3 (3.6.13-1 -> 3.6.14.1-1)
[2009-05-30 23:29] upgraded python (2.6.1-1 -> 2.6.2-1)
[2009-05-30 23:29] upgraded eog (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded epiphany (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded poppler (0.10.6-1 -> 0.10.7-1)
[2009-05-30 23:30] upgraded poppler-glib (0.10.6-1 -> 0.10.7-1)
[2009-05-30 23:30] upgraded evince (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded libsoup (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded evolution-data-server (2.26.1.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded ffmpeg (20090217-1 -> 0.5-1)
[2009-05-30 23:30] upgraded file (5.00-1 -> 5.03-2)
[2009-05-30 23:30] upgraded file-roller (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded findutils (4.4.0-1 -> 4.4.1-2)
[2009-05-30 23:30] upgraded gcalctool (5.26.1-1 -> 5.26.2-1)
[2009-05-30 23:30] installed ppl (0.10.2-2)
[2009-05-30 23:30] installed cloog-ppl (0.15.3-1)
[2009-05-30 23:30] upgraded gcc (4.3.3-1 -> 4.4.0-2)
[2009-05-30 23:30] upgraded gtksourceview2 (2.6.1-1 -> 2.6.2-1)
[2009-05-30 23:30] upgraded gedit (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded glproto (1.4.9-1 -> 1.4.10-1)
[2009-05-30 23:30] upgraded gnome-games (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded whois (4.7.33-1 -> 4.7.33-2)
[2009-05-30 23:30] upgraded gnome-nettool (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:30] upgraded policykit-gnome (0.9.2-3 -> 0.9.2-4)
[2009-05-30 23:30] upgraded gnome-panel (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:31] upgraded gnome-power-manager (2.26.1-1 -> 2.26.1-2)
[2009-05-30 23:31] upgraded vte (0.20.1-1 -> 0.20.2-1)
[2009-05-30 23:31] upgraded gnome-terminal (2.26.1-1 -> 2.26.2-2)
[2009-05-30 23:31] upgraded gtk-engines (2.18.1-1 -> 2.18.2-1)
[2009-05-30 23:31] upgraded gnome-themes (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:31] upgraded gnome2-user-docs (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:31] upgraded gparted (0.4.4-2 -> 0.4.5-1)
[2009-05-30 23:31] upgraded gstreamer0.10-bad (0.10.11-1 -> 0.10.12-1)
[2009-05-30 23:31] upgraded libraw1394 (1.3.0-2 -> 2.0.2-1)
[2009-05-30 23:31] installed libusb1 (1.0.0-1)
[2009-05-30 23:31] upgraded libdc1394 (2.0.3-1 -> 2.1.0-1)
[2009-05-30 23:31] upgraded libdvdread (0.9.7-2 -> 4.1.3-1)
[2009-05-30 23:31] upgraded libdvdnav (0.1.10-3 -> 4.1.3-1)
[2009-05-30 23:31] upgraded neon (0.28.3-2 -> 0.28.4-1)
[2009-05-30 23:31] installed liblrdf (0.4.0-6)
[2009-05-30 23:31] upgraded gstreamer0.10-bad-plugins (0.10.11-3 -> 0.10.12-1)
[2009-05-30 23:31] upgraded gstreamer0.10-good (0.10.14-1 -> 0.10.15-1)
[2009-05-30 23:31] upgraded libavc1394 (0.5.3-2 -> 0.5.3-3)
[2009-05-30 23:31] upgraded libiec61883 (1.1.0-1 -> 1.2.0-1)
[2009-05-30 23:31] installed libcaca (0.99.beta16-1)
[2009-05-30 23:31] upgraded gstreamer0.10-good-plugins (0.10.14-1 -> 0.10.15-1)
[2009-05-30 23:31] upgraded gstreamer0.10-ugly-plugins (0.10.11-1 -> 0.10.11-2)
[2009-05-30 23:31] upgraded gtkhtml (3.26.1.1-1 -> 3.26.2-1)
[2009-05-30 23:31] upgraded gucharmap (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:31] upgraded libarchive (2.6.2-1 -> 2.7.0-1)
[2009-05-30 23:31] NOTE
[2009-05-30 23:31] ----
[2009-05-30 23:31] Add your user to group 'camera' to use camera devices.
[2009-05-30 23:31] upgraded libgphoto2 (2.4.4-1 -> 2.4.6-1)
[2009-05-30 23:31] upgraded gvfs (1.2.2-1 -> 1.2.3-1)
[2009-05-30 23:31] upgraded gzip (1.3.12-4 -> 1.3.12-6)
[2009-05-30 23:31] upgraded jfsutils (1.1.13-1 -> 1.1.14-1)
[2009-05-30 23:31] upgraded libsndfile (1.0.19-1 -> 1.0.20-1)
[2009-05-30 23:31] upgraded sox (14.2.0-2 -> 14.2.0-3)
[2009-05-30 23:31] installed ilmbase (1.0.1-1)
[2009-05-30 23:31] installed openexr (1.6.1-1)
[2009-05-30 23:31] upgraded libpng (1.2.35-1 -> 1.2.36-1)
[2009-05-30 23:31] upgraded qt (4.5.0-5 -> 4.5.1-3)
[2009-05-30 23:31] installed xine-lib (1.1.16.3-3)
[2009-05-30 23:31] installed phonon (4.3.1-2)
[2009-05-30 23:31] installed clucene (0.9.21b-1)
[2009-05-30 23:31] installed exiv2 (0.18-1)
[2009-05-30 23:31] installed strigi (0.6.4-2)
[2009-05-30 23:31] installed soprano (2.2.3-1)
[2009-05-30 23:31] installed xdg-utils (1.0.2-1)
[2009-05-30 23:31] installed kdelibs (4.2.3-1)
[2009-05-30 23:31] installed kdebase-runtime (4.2.3-1)
[2009-05-30 23:31] installed fftw (3.2.1-1)
[2009-05-30 23:31] installed libofa (0.9.3-2)
[2009-05-30 23:31] installed tunepimp (0.5.3-6)
[2009-05-30 23:31] installed kdemultimedia (4.2.3-1)
[2009-05-30 23:31] installed polkit-qt (0.9.2-1)
[2009-05-30 23:31] upgraded k3b (1.0.5-2 -> 1.66.0alpha2-1)
[2009-05-30 23:32] upgraded qt3 (3.3.8-10 -> 3.3.8-11)
[2009-05-30 23:32] upgraded kdelibs3 (3.5.10-2 -> 3.5.10-3)
[2009-05-30 23:32] >>> Updating module dependencies. Please wait ...
[2009-05-30 23:32] >>> MKINITCPIO SETUP
[2009-05-30 23:32] >>> ----------------
[2009-05-30 23:32] >>> If you use LVM2, Encrypted root or software RAID,
[2009-05-30 23:32] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2009-05-30 23:32] >>> More information about mkinitcpio setup can be found here:
[2009-05-30 23:32] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2009-05-30 23:32]
[2009-05-30 23:32] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2009-05-30 23:32] ==> Building image "default"
[2009-05-30 23:32] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2009-05-30 23:32] :: Begin dry run
[2009-05-30 23:32] :: Parsing hook [base]
[2009-05-30 23:32] :: Parsing hook [udev]
[2009-05-30 23:32] :: Parsing hook [autodetect]
[2009-05-30 23:32] :: Parsing hook [sata]
[2009-05-30 23:32] :: Parsing hook [keymap]
[2009-05-30 23:32] :: Parsing hook [filesystems]
[2009-05-30 23:32] :: Generating module dependencies
[2009-05-30 23:32] :: Generating image '/boot/kernel26.img'...SUCCESS
[2009-05-30 23:32] ==> SUCCESS
[2009-05-30 23:32] ==> Building image "fallback"
[2009-05-30 23:32] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2009-05-30 23:32] :: Begin dry run
[2009-05-30 23:32] :: Parsing hook [base]
[2009-05-30 23:32] :: Parsing hook [udev]
[2009-05-30 23:32] :: Parsing hook [sata]
[2009-05-30 23:32] :: Parsing hook [keymap]
[2009-05-30 23:32] :: Parsing hook [filesystems]
[2009-05-30 23:33] :: Generating module dependencies
[2009-05-30 23:33] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2009-05-30 23:33] ==> SUCCESS
[2009-05-30 23:33] upgraded kernel26 (2.6.29.2-1 -> 2.6.29.4-1)
[2009-05-30 23:33] upgraded klibc (1.5.15-1 -> 1.5.15-2)
[2009-05-30 23:33] upgraded klibc-extras (2.5-2 -> 2.5-3)
[2009-05-30 23:33] upgraded klibc-kbd (1.15.20080312-8 -> 1.15.20080312-9)
[2009-05-30 23:33] upgraded klibc-module-init-tools (3.5-1 -> 3.5-2)
[2009-05-30 23:33] upgraded klibc-udev (141-1 -> 141-2)
[2009-05-30 23:33] upgraded libdownload (1.3-1 -> 1.3-3)
[2009-05-30 23:33] upgraded libgsf (1.14.12-1 -> 1.14.13-1)
[2009-05-30 23:33] upgraded libsasl (2.1.22-7 -> 2.1.22-8)
[2009-05-30 23:33] upgraded lsof (4.81-1 -> 4.82-1)
[2009-05-30 23:33] upgraded lzo2 (2.02-3 -> 2.03-1)
[2009-05-30 23:33] upgraded man-pages (3.20-2 -> 3.21-1)
[2009-05-30 23:33] upgraded metacity (2.26.0-1 -> 2.26.0-2)
[2009-05-30 23:33] upgraded mlocate (0.21.1-1 -> 0.22-1)
[2009-05-30 23:33] upgraded mplayer (28347-4 -> 29318-1)
[2009-05-30 23:33] upgraded mtools (4.0.10-1 -> 4.0.10-2)
[2009-05-30 23:33] upgraded nautilus (2.26.2-1 -> 2.26.3-1)
[2009-05-30 23:33] upgraded net-tools (1.60-13 -> 1.60-14)
[2009-05-30 23:33] * relogin or source /etc/profile.d/openoffice.sh
[2009-05-30 23:33] * see http://wiki.archlinux.org/index.php/Openoffice
[2009-05-30 23:33] how to use extensions, e.g. for spell checking
[2009-05-30 23:33] see /opt/openoffice/share/extension/install what
[2009-05-30 23:33] is shipped with this package
[2009-05-30 23:33] upgraded openoffice-base (3.0.1-1 -> 3.1.0-1)
[2009-05-30 23:33] upgraded openoffice-es (3.0.1-1 -> 3.1.0-1)
[2009-05-30 23:33] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2009-05-30 23:33] upgraded pacman-mirrorlist (20090405-1 -> 20090509-1)
[2009-05-30 23:33] upgraded pango (1.24.1-1 -> 1.24.2-1)
[2009-05-30 23:33] upgraded pidgin (2.5.5-2 -> 2.5.6-1)
[2009-05-30 23:33] upgraded tcp_wrappers (7.6-8 -> 7.6-9)
[2009-05-30 23:33] upgraded portmap (6.0-2 -> 6.0-3)
[2009-05-30 23:33] upgraded ppp (2.4.4-7 -> 2.4.4-8)
[2009-05-30 23:33] upgraded procps (3.2.7-5 -> 3.2.8-1)
[2009-05-30 23:33] upgraded psmisc (22.6-2 -> 22.7-1)
[2009-05-30 23:33] upgraded pycairo (1.8.2-1 -> 1.8.4-1)
[2009-05-30 23:33] upgraded pygobject (2.16.1-1 -> 2.18.0-1)
[2009-05-30 23:33] upgraded python-gdata (1.3.0-1 -> 1.3.1-1)
[2009-05-30 23:33] upgraded python-nose (0.10.4-3 -> 0.11.0-1)
[2009-05-30 23:33] upgraded python-numpy (1.3.0-1 -> 1.3.0-2)
[2009-05-30 23:33] upgraded rsync (3.0.5-1 -> 3.0.6-1)
[2009-05-30 23:34] upgraded seahorse (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:34] upgraded seahorse-plugins (2.26.1-1 -> 2.26.2-1)
[2009-05-30 23:34] upgraded sysfsutils (2.1.0-4 -> 2.1.0-5)
[2009-05-30 23:34] upgraded syslinux (3.75-4 -> 3.80-1)
[2009-05-30 23:34] upgraded sysvinit (2.86-4 -> 2.86-5)
[2009-05-30 23:34] upgraded tomboy (0.14.1-1 -> 0.14.2-1)
[2009-05-30 23:34] upgraded transmission-gtk (1.42-1 -> 1.60-1)
[2009-05-30 23:34] upgraded unrar (3.9.1-1 -> 3.9.3-1)
[2009-05-30 23:34] upgraded usbutils (0.81-1 -> 0.82-1)
[2009-05-30 23:35] upgraded vlc (0.9.9a-1 -> 0.9.9a-4)
[2009-05-30 23:35] upgraded wireless_tools (29-2 -> 29-3)
[2009-05-30 23:35] upgraded xfsprogs (3.0.0-1 -> 3.0.1-1)
[2009-05-30 23:35] upgraded xkeyboard-config (1.5-1 -> 1.6-1)
[2009-05-30 23:35] upgraded xorg-server-utils (7.4-5 -> 7.4-6)
[2009-05-30 23:35] upgraded xorg-server (1.6.1-1 -> 1.6.1.901-1)

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.

[SOLVED] X fails after pacman -Syu

After a year or so without upgrading (not recommended) I did a pacman -Syu; it took like ages 'cause I was on kernel 2.26, and now my arch is a complete mess: user modules don't load at boot, dhcpcd is not working so I don't have internet access and the X server is erratic too. Now I have to repair it step by step, and I think I should start with X.
Here is the startx/ xinit output:
[root@HAL-9000 ~]# startx
xauth: (argv):1: bad display name "HAL-9000:0" in "list" command
xauth: (stdin):1: bad display name "HAL-9000:0" in "add" command
X.Org X Server 1.11.2
Release Date: 2011-11-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.1.1-1-ARCH i686
Current Operating System: Linux HAL-9000 3.1.1-1-ARCH #1 SMP PREEMPT Fri Nov 11 22:05:37 UTC 2011 i686
Kernel command line: root=/dev/disk/by-uuid/67fb73d6-b981-47d1-a07c-223b5b730551 ro vga=0x0318
Build Date: 16 November 2011 11:26:40AM
Current version of pixman: 0.24.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov 20 19:02:40 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(EE) synaptics: Touchpad: Synaptics driver unable to detect protocol
(EE) PreInit returned 11 for "Touchpad"
gnome-session: error while loading shared libraries: libdevkit-power-gobject.so.1: cannot open shared object file: No such file
or directory
xinit: connection to X server lost
waiting for X server to shut down Server terminated successfully (0). Closing log file.
I guess the gnome-session error with libdevkit-powe-gobject.so.1 is what causes the x server to close. And this is the complete X log:
http://pastebin.com/UBficJVi
*note: I have a Nvdia card which already worked perfectly with the privative driver, and supposedly I still have gnome 2 (that was the only packages group I didn't upgrade)
Last edited by isacdaavid (2011-11-21 06:27:07)

isacdaavid wrote:
knopwob wrote:
isacdaavid wrote:*note: I have a Nvdia card which already worked perfectly with the privative driver, and supposedly I still have gnome 2 (that was the only packages group I didn't upgrade)
So you updated everything except gnome-stuff? Update the gnome-stuff.
But I'm all for gnome 2 , and X should work despite of the gnome version or the desktop environment. Shouldn't it?
No, not if you're using gdm or autoboot into gnome or something similar.
gnome-session: error while loading shared libraries: libdevkit-power-gobject.so.1: cannot open shared object file: No such file
or directory
This sounds like one of gnome-sessions dependencies have been updated and isn't compatible with gnome-session anymore.
Before you continue trying to repair your system, you should read this

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).

[solved] boot fails after recent update

After updating a load of packages today my system fails to boot with the following message:
Checking Filesystems [Fail]
********************Reboot Required*********************
* The System will be rebooted automatically in 15 seconds *
Then it just reboots. I can't get past this message.
I did not upgrade the kernel26-firmware package since I run kernel26-ice 2.6.29.
I can't find any logfiles for hints. What could be wrong?
[Edit 2009-07-06]
I checked the filesystems from a rescue system to no avail.
Last edited by mykey (2009-07-07 09:54:15)

Oh well - took me a while to figure things out this time maybe the solution helps somebody else.
Since I use reiser4 as a filesystem I had to recompile reiser4progs against the new libreadline in order to allow a proper fsck during boot

Boot fails after improper shutdown

A few months ago, my Powerbook G4 Titanium began failing to boot into 10.4 after any improper shutdown---power failure, force restart, etc.
It would begin booting, the little circle would start to spin, and then the thing would just shut off. No error, no message.
The only solution was to pull out my Norton Systemworks CD, use it to boot into OS9, and then restart into 10.4.
Any help in figuring out what's up would be greatly appriciated.

Norton Systemworks was actually probably the cause at one point. It is not compatible with Mac OS X in its Disk Doctor or Speed Disk module.
You should only use these utilites:
1. A backup utility before any other as my backup FAQ says:
http://www.macmaps.com/backup.html
2. And if your data is backed up and won't boot after an improper shut down, try repairing your directory with utilities known to work as my FAQ explains:
http://www.macmaps.com/directoryfaq.html
The only elements of Systemworks that are even remotely safe for use with Mac OS X are Retrospect for backup, and Anti-virus for locating Windows viruses on your Mac that you may transfer to Windows users. Everything else, you should throw away from the Systemworks bundle.

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

[SOLVED] Boot fails after setting bios time to future

I set my pc clock to wrong year(future) in bios, it worked first time but after a reboot I am getting this error message:
Starting File System Check on /dev/disk/by-uuid/xxxxxxxxxxxxxxxxxxx...
systemd-fsck[299]: storage: Superblock last mount time (Sat Oct 30 17:11:14 2038,
systemd-fsck[299]: now = Wed Oct 30 18:12:01 2013) is in the future.
systemd-fsck[299]: storage: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
systemd-fsck[299]: (i.e., without -a or -p options)
Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): _
In emergency shell, running "systemctl default" and same error shows up again. Running "fsck /dev/sda1" says "/dev/sda1 is mounted\ne2fsck: Cannot continue, aborting.". Umount'ing /dev/sda1 and fsck still says it's mounted. Google doesn't help much with this error.
Last edited by axper (2013-10-30 17:06:56)

That's what I tried:
(emergency shell)
# fsck /dev/sda1
fsck from util-linux 2.24
e2fsck 1.42.8 (20-Jun-2013)
/dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.
# umount /dev/sda1
# fsck /dev/sda1
fsck from util-linux 2.24
e2fsck 1.42.8 (20-Jun-2013)
/dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.
Also ran "fsck /dev/sda1" from live cd, rebooted - still the same.

Boot problems after pacman -Syu

Hi,
I have been using Archlinux happily for the last couple of months, updating weekly and generally having no problems.
Last friday i did an update (which included a kernel update), shut down and left it for the weekend and found that it doesn't boot today.
the last 4 lines of the boot sequence are:
:: Running Hook [filesystems]
:: Loading root filesystem module... ext3
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
i use GRUB as the boot loader and these are the lines you can edit from there
root (hd0,0)
kernel /vmlinuz26 root=/dev/hda3 ro
initrd /kernel26.img
i have also tried booting with the live cd and the command
arch root=/dev/hda3 noinitrd ro
and it locks up here:
using ipi shortcut mode
kjournald starting. commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly
So i am guessing that i am having trouble mounting the root filesystem. I think i remember seeing a message about checking the EXT3 filesystem flash by on one of my boot attempts but i don't know how i would do this without being able to boot arch linux!
thanks for any advice you can offer.
dicki
Last edited by dicki (2007-02-26 12:15:47)

while i feel like i am talking to myself...
i have come to the conclusion that it wasn't a pacman issue. i think the system is broken in the wrong way for that to be the cause.
i have now managed to mount and read *parts* of the filesystem. i am resigned to the idea that i'm going to have to trash this install and start again but i would like to try and get my recent e-mail messages off of it if i can.
When the disk is mounted i can see all of the top level directories however all of the useful ones (./boot, ./root, ./home etc) say that there is an Input Output Error when i try to access them. does anyone have any thoughts on recovering this data. i believe it should be in ~/.opera/mail but i currently cannot read this directory.

Wireless fails after pacman update

I had my wireless functional but after the latest set of updates it somehow broke.
It's a Broadcom wireless that uses the b43 driver.
I wrote myself a little cheater list when I first set up the wireless. The commands appear okay but when I attempt to get to the net I get a network unreachable error when I attempt to ping anything.
sudo ip link set wlan0 up
sudo iwlist wlan0 scan | grep ESSID
I see the available wireless. 2WIRE824 is my router.
ESSID:"2WIRE824"
ESSID:"Enforcer24GHz"
ESSID:"2WIRE409"
ESSID:"2WIRE907"
ESSID:"BAMFs"
I submit my key and attempt to connect to my router
sudo iwconfig wlan0 essid "2WIRE824" key **mykey**
sudo dhcpcd wlan0
returns --> dhcpcd[797]: sending commands to master dhcpcd process
now when I try to ping anything I get network unreachable.
What has changed (or what am I missing) that broke the wireless?
I have all my wireless profiles that haven't changed and they are still listed in /etc/rc.conf
I've even tried
sudo iwconfig wlan0 channel auto
despite my cheatsheet stating to use that only if the dhcpcd times out.
snippet from dmesg
[ 10.204558] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[ 12.331304] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 12.333498] e100 0000:02:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
[ 12.480083] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
[ 12.547890] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 12.548137] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 23.096727] eth0: no IPv6 routers present
[arch-nicky@arch-nicky ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:ff:ff:ff:8b:78 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.82/24 brd 192.168.1.255 scope global eth0
inet6 fe80::fff:ffff:fe1e:8b78/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:14:a5:0d:64:e5 brd ff:ff:ff:ff:ff:ff
[arch-nicky@arch-nicky ~]$ ip link set wlan0 up
RTNETLINK answers: Operation not permitted
I feel like the above output has something to do with it. Is wlan0 still down? Why didn't it go up? And why no error message that it didn't successfully go up?
from
sudo less /var/log/messages.log
Aug 7 18:52:59 localhost kernel: [ 6.942500] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
Aug 7 18:52:59 localhost kernel: [ 6.957385] e100 0000:02:08.0: eth0: addr 0xdfdfd000, irq 20, MAC addr 00:12:3f:1e:8b:78
Aug 7 18:52:59 localhost kernel: [ 6.996832] Broadcom 43xx driver loaded [ Features: PMNLS ]
Aug 7 18:52:59 localhost kernel: [ 7.310498] [drm] initialized overlay support
Aug 7 18:52:59 localhost kernel: [ 12.437978] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 7 18:52:59 localhost kernel: [ 12.440172] e100 0000:02:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
Aug 7 18:52:59 localhost kernel: [ 12.586739] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
Aug 7 18:52:59 localhost kernel: [ 12.659863] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug 7 18:52:59 localhost kernel: [ 12.660131] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 7 18:52:59 localhost dhcpcd[281]: eth0: sending IPv6 Router Solicitation
Aug 7 18:52:59 localhost dhcpcd[281]: eth0: rebinding lease of 192.168.0.6
Aug 7 18:52:59 localhost dhcpcd[281]: wlan0: sending IPv6 Router Solicitation
Aug 7 18:52:59 localhost dhcpcd[281]: wlan0: broadcasting for a lease
Aug 7 18:52:59 localhost kernel: [ 6.957385] e100 0000:02:08.0: eth0: addr 0xdfdfd000, irq 20, MAC addr 00:12:3f:1e:8b:78
Aug 7 18:52:59 localhost kernel: [ 6.996832] Broadcom 43xx driver loaded [ Features: PMNLS ]
Aug 7 18:52:59 localhost kernel: [ 7.310498] [drm] initialized overlay support
Aug 7 18:52:59 localhost kernel: [ 12.437978] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 7 18:52:59 localhost kernel: [ 12.440172] e100 0000:02:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
Aug 7 18:52:59 localhost kernel: [ 12.586739] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
Aug 7 18:52:59 localhost kernel: [ 12.659863] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug 7 18:52:59 localhost kernel: [ 12.660131] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 7 18:52:59 localhost dhcpcd[281]: eth0: sending IPv6 Router Solicitation
Aug 7 18:52:59 localhost dhcpcd[281]: eth0: rebinding lease of 192.168.0.6
Aug 7 18:52:59 localhost dhcpcd[281]: wlan0: sending IPv6 Router Solicitation
Aug 7 18:52:59 localhost dhcpcd[281]: wlan0: broadcasting for a lease
Aug 7 18:52:59 localhost dhcpcd[281]: eth0: NAK: from 192.168.1.254
Aug 7 18:53:00 localhost dhcpcd[281]: wlan0: carrier lost
Aug 7 18:53:00 localhost dhcpcd[281]: eth0: sending IPv6 Router Solicitation
Aug 7 18:53:00 localhost dhcpcd[281]: eth0: broadcasting for a lease
Aug 7 18:53:01 localhost dhcpcd[281]: eth0: offered 192.168.1.82 from 192.168.1.254
Aug 7 18:53:01 localhost dhcpcd[281]: eth0: acknowledged 192.168.1.82 from 192.168.1.254
Aug 7 18:53:01 localhost dhcpcd[281]: eth0: checking for 192.168.1.82
Aug 7 18:53:03 localhost dhcpcd[281]: wlan0: sending IPv6 Router Solicitation
Aug 7 18:53:04 localhost dhcpcd[281]: eth0: sending IPv6 Router Solicitation
Aug 7 18:53:06 localhost dhcpcd[281]: eth0: leased 192.168.1.82 for 86400 seconds
Aug 7 18:53:06 localhost dhcpcd[281]: forked to background, child pid 339
Aug 7 18:53:07 localhost dhcpcd[339]: wlan0: sending IPv6 Router Solicitation
Aug 7 18:53:08 localhost dhcpcd[339]: eth0: sending IPv6 Router Solicitation
Aug 7 18:53:11 localhost dhcpcd[339]: wlan0: sending IPv6 Router Solicitation
Aug 7 18:53:11 localhost dhcpcd[339]: wlan0: no IPv6 Routers available
Aug 7 18:53:12 localhost dhcpcd[339]: eth0: sending IPv6 Router Solicitation
Aug 7 18:53:12 localhost dhcpcd[339]: eth0: no IPv6 Routers available
Any thoughts/ideas/ or add'l info to help debug?
Thanks!

I had asked about systemd because I have noticed it sometimes starts things that have been installed and are lying around dormant if they were not in the DAEMONS array. I have been bitten...
So, you said...
inkdinky wrote:
I submit my key and attempt to connect to my router
sudo iwconfig wlan0 essid "2WIRE824" key **mykey**
sudo dhcpcd wlan0
I would like to see the output of a second iwconfig without any switches or parameters performed a few seconds after that first one, just as you wrote it. I want to establish if you are actually associating with the AP. You should see the MAC of the AP in that output.
Then, you said
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:ff:ff:ff:8b:78 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.82/24 brd 192.168.1.255 scope global eth0
inet6 fe80::fff:ffff:fe1e:8b78/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:14:a5:0d:64:e5 brd ff:ff:ff:ff:ff:ff
Okay, the wlan has no address, as expected. The carrier, however should be up.
[arch-nicky@arch-nicky ~]$ ip link set wlan0 up
RTNETLINK answers: Operation not permitted
But you have to run that as root
So, put the interface up as root.
Try to associate with sudo iwconfig wlan0 essid "2WIRE824" key **mykey**
Pause. Run iwconfig
If it associates, then run dhcpcd wlan0 . Don't waste your time if it does not associate.
If you are still having trouble, look at the output of rfkill list
One last thought. Are you trying to connect to the same router as you are wired to? You should be able to associate, but you may have routing issues later.
Last edited by ewaller (2012-08-09 03:12:10)

Boot fails after pacman -Suy

Similar Messages

Maybe you are looking for