I'm in the process of installing a new box, last night before going to bed I
started installing xorg server. This morning, I found the 82nd build (out of
162) had failed with the following error:
1450K .......... .......... .......... .......... .......... 89% 44.2K
0:04
1500K .......... .......... .......... .......... .......... 92% 51.2K
0:02
1550K .......... .......... .......... .......... .......... 95% 20.0K
0:04
1600K .......... .......... .......... .......... .......... 98% 61.9K
1650K .......... .......... .......... . 100% 46.4K
00:33:24 (29.93 KB/s) - `/usr/portage/distfiles/curl-7.17.1.tar.bz2' saved
[1721551/1721551]
>>> Unpacking curl-7.17.1.tar.bz2 to
/var/tmp/portage/net-misc/curl-7.17.1/work
* Applying curl-7.16.2-strip-ldflags.patch ...
[ ok ]
* Applying curl-7.17.1-null-handler-segfault.patch ...
[ ok ]
* Running elibtoolize in: curl-7.17.1
* Applying install-sh-1.5.patch ...
* Applying portage-1.5.10.patch ...
* Applying sed-1.5.6.patch ...
>>> Source unpacked.
>>> Compiling source in
/var/tmp/portage/net-misc/curl-7.17.1/work/curl-7.17.1 ...
*
* ERROR: net-misc/curl-7.17.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2344: Called die
* The specific snippet of code:
* die 'ldap and kerberos (gssapi) not playing nicely try version
>=7.18.1';
* The die message:
* ldap and kerberos (gssapi) not playing nicely try version >=7.18.1
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located at
'/var/tmp/portage/net-misc/curl-7.17.1/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/net-misc/curl-7.17.1/temp/environment'.
*
* Regenerating GNU info directory index...
* Processed 133 info files.
Okay, looks like there's something wrong with curl, let's see what the
current and latest version I can unmask is:
[ 00:33:41 ] Wed Apr 16 /home/Cyor $ emerge -s curl
Searching... -Traceback (most recent call last):
File "/usr/bin/emerge", line 6971, in ?
retval = emerge_main()
File "/usr/bin/emerge", line 6945, in emerge_main
myopts, myfiles, spinner)
File "/usr/bin/emerge", line 5811, in action_search
searchinstance.execute(mysearch)
File "/usr/bin/emerge", line 566, in execute
if not self.portdb.xmatch("match-visible", package):
File "/usr/bin/emerge", line 494, in _xmatch
matches.update(db.xmatch(level, atom))
File "/usr/lib/portage/pym/portage.py", line 7438, in xmatch
File "/usr/lib/portage/pym/portage.py", line 7372, in xmatch
File "/usr/lib/portage/pym/portage.py", line 7481, in visible
File "/usr/lib/portage/pym/portage.py", line 7085, in aux_get
File "/usr/lib/portage/pym/cache/template.py", line 82, in __delitem__
File "/usr/lib/portage/pym/cache/flat_hash.py", line 98, in _delitem
raise cache_errors.CacheCorruption(cpv, e)
cache.cache_errors.CacheCorruption: dev-lisp/cl-curl-20050609 is corrupt:
[Errno 13] Permission denied:
'/var/cache/edb/dep/usr/portage/dev-lisp/cl-curl-20050609'
What...! the file is corrupt..? okay, maybe a --sync will fix it:
[ 06:41:58 ] Wed Apr 16 /home/Cyor $ emerge --sync
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
Permission denied: '/usr/portage/metadata/timestamp.chk'
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
"Permission denied," " Read-only file system" ... WTF..!?!
[ 06:42:52 ] Wed Apr 16 /home/Cyor $ df
bash: /bin/df: Input/output error
"I/O error" okay enough of this, time to reboot.
[ 06:43:22 ] Wed Apr 16 /home/Cyor $ shutdown -h now
bash: /sbin/shutdown: Input/output error
Uh-oh, this is starting to look bad.
[ 06:44:48 ] Wed Apr 16 /home/Cyor $ man emerge
bash: man: command not found
[ 06:45:05 ] Wed Apr 16 /home/Cyor $ cd /
[ 06:45:13 ] Wed Apr 16 / $ ls
ls: cannot access stage3-i686-2007.0.tar.bz2.DIGESTS: Permission denied
ls: cannot access portage-20080407.tar.bz2: Permission denied
total 105521
1 drwxr-xr-x 21 NormalUser Domain Admins 736 Apr 12 12:02 .
1 drwxr-xr-x 21 NormalUser Domain Admins 736 Apr 12 12:02 ..
4 drwxr-xr-x 2 NormalUser Domain Admins 3888 Apr 13 09:41 bin
0 drwxr-xr-x 2 NormalUser Domain Admins 48 Apr 7 17:23 boot
0 drwxr-xr-x 15 NormalUser Domain Admins 3120 Apr 15 21:23 dev
3 drwxr-xr-x 40 NormalUser Domain Admins 3144 Apr 16 00:32 etc
0 drwxr-xr-x 5 NormalUser Domain Admins 144 Apr 12 11:21 home
4 drwxr-xr-x 8 NormalUser Domain Admins 4048 Apr 12 14:31 lib
0 drwxr-xr-x 4 NormalUser Domain Admins 80 Apr 12 05:19 log
0 drwxr-xr-x 6 NormalUser Domain Admins 168 Apr 11 21:44 mnt
0 drwxr-xr-x 2 NormalUser Domain Admins 72 Apr 19 2007 opt
? ?????????? ? ? ? ? ?
portage-20080407.tar.bz2
4 -rw-r--r-- 1 NormalUser Domain Admins 59 Apr 9 07:42
portage-20080407.tar.bz2.md5sum
0 dr-xr-xr-x 67 NormalUser Domain Admins 0 Apr 15 14:21 proc
0 drwx------ 3 NormalUser Domain Admins 216 Apr 12 14:12 root
4 drwxr-xr-x 2 NormalUser Domain Admins 3856 Apr 12 15:18 sbin
105491 -rw-r--r-- 1 NormalUser Domain Admins 107915722 Apr 8 22:35
stage3-i686-2007.0.tar.bz2
? ?????????? ? ? ? ? ?
stage3-i686-2007.0.tar.bz2.DIGESTS
0 drwxr-xr-x 12 NormalUser Domain Admins 0 Apr 15 14:21 sys
0 drwxrwxrwt 4 NormalUser Domain Admins 112 Apr 16 00:32 tmp
0 drwxr-xr-x 13 NormalUser Domain Admins 368 Apr 10 09:52 usr
0 drwxr-xr-x 15 NormalUser Domain Admins 408 Apr 16 00:14 var
[ 06:45:14 ] Wed Apr 16 / $ reboot
bash: /sbin/reboot: Input/output error
[ 06:45:32 ] Wed Apr 16 / $ cd sbin/
[ 06:46:04 ] Wed Apr 16 /sbin $ ls
ls: cannot access grub: Permission denied
ls: cannot access grub-md5-crypt: Permission denied
ls: cannot access grub-terminfo: Permission denied
ls: cannot access reiserfstune: Permission denied
ls: cannot access grub-install: Permission denied
ls: cannot access debugreiserfs: Permission denied
ls: cannot access grub-set-default: Permission denied
ls: cannot access resize_reiserfs: Permission denied
total 5314
4 drwxr-xr-x 2 NormalUser Domain Admins 3856 Apr 12 15:18 .
1 drwxr-xr-x 21 NormalUser Domain Admins 736 Apr 12 12:02 ..
52 -rwxr-xr-x 1 NormalUser Domain Admins 51168 Apr 19 2007 MAKEDEV
16 -rwxr-xr-x 1 NormalUser Domain Admins 14748 Apr 19 2007 agetty
4 -rwxr-xr-x 1 NormalUser Domain Admins 3928 Apr 19 2007 ctrlaltdel
.
.
.
68 -rwxr-xr-x 1 NormalUser Domain Admins 66096 Apr 19 2007 debugfs
? ?????????? ? ? ? ? ? debugreiserfs
36 -rwxr-xr-x 1 NormalUser Domain Admins 35232 Apr 19 2007 depmod
.
.
.
12 -rwxr-xr-x 1 NormalUser Domain Admins 9493 Apr 19 2007
generate-modprobe.conf
36 -rwxr-xr-x 1 NormalUser Domain Admins 36364 Apr 19 2007 genksyms
? ?????????? ? ? ? ? ? grub
? ?????????? ? ? ? ? ? grub-install
? ?????????? ? ? ? ? ?
grub-md5-crypt
? ?????????? ? ? ? ? ?
grub-set-default
? ?????????? ? ? ? ? ? grub-terminfo
12 -rwxr-xr-x 1 NormalUser Domain Admins 10376 Apr 19 2007 halt
56 -rwxr-xr-x 1 NormalUser Domain Admins 56212 Apr 19 2007 hdparm
8 -rwxr-xr-x 1 NormalUser Domain Admins 5546 Apr 19 2007 rc-update
0 lrwxrwxrwx 1 NormalUser Domain Admins 4 Apr 9 07:45 reboot ->
halt
288 -rwxr-xr-x 1 NormalUser Domain Admins 293800 Apr 11 22:25 reiserfsck
? ?????????? ? ? ? ? ? reiserfstune
28 -rwxr-xr-x 1 NormalUser Domain Admins 28484 Apr 19 2007 resize2fs
? ?????????? ? ? ? ? ?
resize_reiserfs
12 -rwxr-xr-x 1 NormalUser Domain Admins 9556 Apr 19 2007 rmmod
0 lrwxrwxrwx 1 NormalUser Domain Admins 10 Apr 9 07:45 rmmod.old ->
insmod.old
20 -rwxr-xr-x 1 NormalUser Domain Admins 18580 Apr 19 2007 udevtrigger
0 lrwxrwxrwx 1 NormalUser Domain Admins 14 Apr 9 07:45
update-modules -> modules-update
[ 06:46:07 ] Wed Apr 16 /sbin $ ./halt -r now
bash: ./halt: Input/output error
[ 06:48:33 ] Wed Apr 16 /sbin $ ./reboot
bash: ./reboot: Input/output error
BTW, the user:group "NormalUser : Domain Admins" in normal and correct that
is 0:0, it comes from the W2K3 domain controller that is the NIS server, and
NIS is listed first in nsswitch.conf.
Also worthy of note is the reason for installing this new box, the previous
install developed severe hard disk corruption. Because of that, this install
is located on a brand new 250G Seagate with a five year warranty, so while
not impossible, I tend to doubt that the hard disk it self is the true root
cause.
Okay, so my question is how bad is it?
Is there anyway to shutdown cleanly?
I do have a second brand new 250G Seagate, is another clean install, with a
*second* brand new drive the best alternative, or is some even lower level
hardware (i.e. disk controller) the more likely culprit at this point?
Thanks for listening
Bob Young
San Jose, CA.
--
[email protected] mailing list
