[Solved] latest filesystem upgrade failed

Question

During last system upgrade ( pacman -Syu )，when upgrading filesystem-2011.08-1,
the system hang for a while,  then pacman exit with some segfault error
I tried to fix it by typing ` pacman -Syu ` again, then got another error when upgrading linux-3.0.2-1
ERROR: file not found: `/etc/modprobe.d/usb-load-ehci-first.conf'
and filesystem is not in the upgrade package list, so I tried
sudo pacman -S filesystem
but I got some file confilct error
warning: filesystem-2011.08-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/desc: No such file or directory
Targets (1): filesystem-2011.08-1
Total Download Size: 0.00 MB
Total Installed Size: 0.06 MB
checking package integrity...
checking for file conflicts...
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
error: could not open file /var/lib/pacman/local/filesystem-2011.08-1/files: No such file or directory
filesystem: /etc/crypttab exists in filesystem
filesystem: /etc/fstab exists in filesystem
filesystem: /etc/group exists in filesystem
filesystem: /etc/gshadow exists in filesystem
filesystem: /etc/host.conf exists in filesystem
filesystem: /etc/hosts exists in filesystem
filesystem: /etc/issue exists in filesystem
filesystem: /etc/ld.so.conf exists in filesystem
filesystem: /etc/motd exists in filesystem
filesystem: /etc/nsswitch.conf exists in filesystem
filesystem: /etc/passwd exists in filesystem
filesystem: /etc/profile exists in filesystem
filesystem: /etc/resolv.conf exists in filesystem
filesystem: /etc/securetty exists in filesystem
filesystem: /etc/shadow exists in filesystem
filesystem: /etc/shells exists in filesystem
Errors occurred, no packages were upgraded.
after search the forum, I found a post last year
https://bbs.archlinux.org/viewtopic.php?pid=833711
I only have the file " install " in /var/lib/pacman/local/filesystem-2011.08-1/
ls -l /var/lib/pacman/local/filesystem-2011.08-1/
total 4.0K
-rw-r--r-- 1 root root 1.6K Aug 10 07:41 install
I checked another machine which also installed Arch Linux,
it's package number is filesystem-2011.04-1
ls -l /var/lib/pacman/local/filesystem-2011.04-1/
total 12
-rw-r--r-- 1 root root 287 Jul 23 12:49 desc
-rw-r--r-- 1 root root 1804 Jul 23 12:23 files
-rw-r--r-- 1 root root 1623 Apr 8 18:08 install
Should I just copy the " desc " and " files " to my computer, then run `pacman -Syu` again
or
Upgrade that machine's filesystem to 2011.08-1, then copy the files to my computer to fix it ?
( I am afraid of upgrade error again)
Thank you
Last edited by lefthaha (2011-08-20 16:38:24)

Answer 1

I just upgraded filesystem to 2011.08-1 on my VM
then copyed the " desc, files " under /var/lib/pacman/local/filesystem-2011.08-1/
to my computer, and reinstall filesystem and kernel
$ sudo pacman -S filesystem --dbonly
$ sudo pacman -S filesystem
Running 'pacman -S filesystem'
warning: /etc/fstab installed as /etc/fstab.pacnew
warning: /etc/group installed as /etc/group.pacnew
warning: /etc/hosts installed as /etc/hosts.pacnew
warning: /etc/passwd installed as /etc/passwd.pacnew
warning: /etc/resolv.conf installed as /etc/resolv.conf.pacnew
warning: /etc/shells installed as /etc/shells.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
warning: /etc/shadow installed as /etc/shadow.pacnew
upgraded filesystem (2011.08-1 -> 2011.08-1)
$ sudo pacman -S linux
after edited /etc/fstab,  reboot the computer
During booting I got some filesystem error warning
system automaticlly checked and fixed those errors on root partition and reboot again
Then I can boot into X now
in  /var/log/error.log  I found something similar to previous booting error
Aug 19 20:39:42 MyHost kernel: [473315.923933] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:39:42 MyHost kernel: [473315.923939] ata1.00: BMDMA stat 0x65
Aug 19 20:39:42 MyHost kernel: [473315.923944] ata1.00: failed command: READ DMA EXT
Aug 19 20:39:42 MyHost kernel: [473315.923954] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:39:42 MyHost kernel: [473315.923955] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:39:42 MyHost kernel: [473315.923960] ata1.00: status: { DRDY ERR }
Aug 19 20:39:42 MyHost kernel: [473315.923963] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473321.025032] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473321.025038] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473321.025044] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473321.025053] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473321.025055] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473321.025059] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473321.025062] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473328.558325] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473328.558331] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473328.558337] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473328.558346] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473328.558348] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473328.558352] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473328.558355] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473333.355772] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473333.355779] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473333.355784] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473333.355794] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473333.355796] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473333.355800] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473333.355802] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473338.984884] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473338.984891] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473338.984896] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473338.984905] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473338.984907] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473338.984911] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473338.984914] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473345.947035] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Aug 19 20:40:13 MyHost kernel: [473345.947042] ata1.00: BMDMA stat 0x65
Aug 19 20:40:13 MyHost kernel: [473345.947047] ata1.00: failed command: READ DMA EXT
Aug 19 20:40:13 MyHost kernel: [473345.947056] ata1.00: cmd 25/00:00:6f:20:bd/00:04:00:00:00/e0 tag 0 dma 524288 in
Aug 19 20:40:13 MyHost kernel: [473345.947058] res 51/40:00:d2:23:bd/40:00:00:00:00/e0 Emask 0x9 (media error)
Aug 19 20:40:13 MyHost kernel: [473345.947062] ata1.00: status: { DRDY ERR }
Aug 19 20:40:13 MyHost kernel: [473345.947065] ata1.00: error: { UNC }
Aug 19 20:40:13 MyHost kernel: [473345.980986] end_request: I/O error, dev sda, sector 12395474
after searching on the web, I found that maybe an old harmless problem related to kernel ?
https://bbs.archlinux.org/viewtopic.php?pid=293179
also found an error in  /var/log/daemon.log
Failed to activate service 'org.freedesktop.Avahi': timed out
there is already a post about it, but not having a conclusion yet
https://bbs.archlinux.org/viewtopic.php?id=124485
Every things seen to work fine now
After few more test and reboot, I would mark this post [solved]
Thanks to everyone for replying m(_ _)m
P.S.
There is still a problem when using virtualbox 4.1.2-1 after reboot, but I think that may not related to this post
If I try to upgrade kernel of the VM to 3.0.2-1  ( currently 3.0.1-1 ), will cause VirtualBox and my computer crash
generating some assert error, produce segfault when I tried to type any command in shell
unable to launch any program in X, but if I switch to tty*, I only got
INIT:Id "x" respawning too fast: disabled for 5 minutes
So I have to push the reset button to force reboot
after restore VM to previous snapshot, not having any problem so far