After upgrading from udev-058 to udev-070 (actually any version>58) my external firewire hard disk locks up when plugged. Visually the activity led will light up steadily, as it would being accessed, the sd* device is created but I'm not able to use it. After some troubleshooting I found out that removing line 284 in file /etc/udev/rules.d/50-udev.rules will solve the problem. That line says: KERNEL=="*[0-9]", IMPORT="/sbin/vol_id --export $tempnode" It seems that vol_id actually locks up the drive. Maybe it's a drive fault, but I think it could be ok to report the problem Reproducible: Always Steps to Reproduce: 1. Plug firewire external HDD to PC 2. Switch on the unit Actual Results: Unit doesn't work - Activity LED steady on Expected Results: Be able to mount drive/partitions Portage 2.0.51.22-r3 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r2, 2.6.13-ck8 i686) ================================================================= System uname: 2.6.13-ck8 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe -ffast-math -msse2 -mmmx -mfpmath=sse" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe -ffast-math -msse2 -mmmx -mfpmath=sse" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig candy distlocks nostrip sandbox sfperms strict" GENTOO_MIRRORS="ftp://194.117.143.70/mirrors/gentoo http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://194.117.143.72/mirrors/gentoo" LANG="it_IT@euro" LDFLAGS="-Wl,-O1" LINGUAS="it" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X a52 aac acpi alsa apm arts avi berkdb bitmap-fonts bonobo browserplugin cdr crypt cups curl divx4linux dv dvb dvd dvdr dvdread eds emboss encode esd fame ffmpeg flac foomaticdb fortran freetype gd gdbm gif gimp gimpprint gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml imagemagick imap imlib ipv6 java jpeg junit libg++ libwww lirc lzo mad maildir mikmod mjpeg mmx motif mozilla mp3 mpeg ncurses nls nptl nsplugin nvidia ogg oggvorbis opengl pam pdflib perl pic png ppds python qt quicktime readline real samba scanner sdl slang spell sse sse2 ssl svg svga tcltk tcpd tiff truetype truetype-fonts type1-fonts unicode usb vorbis win32codecs xine xml xml2 xmms xprint xv xvid zlib linguas_it userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, MAKEOPTS
If you comment out that line, and then run the vol_id program from the command line (as root), what does it output or do? Any kernel log entries get generated?
This is what I see in kernel log running # /sbin/vol_id --export /dev/sda Oct 24 13:32:48 [kernel] ieee1394: sbp2: aborting sbp2 command - Last output repeated 4 times - Oct 24 13:33:48 [kernel] scsi1 (0:0): rejecting I/O to offline device No output from the program itself After this command the unit is unaccessable, and running again the above program gives: /dev/sda: error open volume To get back the drive, I need to switch the unit off and then on.
After some further investigation, I've found that the problem isn't related vo vol_id itself, but it seems to stay somwhere between sbp2 driver and the external firewire interface. Disk is a 160Gb ide I've done a badblock scan of the disk and I've found that exactly at 128*1024*1024+1 block it starts giving the same errors as reported for vol_id. I tested the disk directly to IDE interface and it works perfectly, no badblocks or other problems. My conclusion is that the problem arise because the external disk reports to be 160Gb in size, but driver or firmware is only able to handle 128Gb. Sorry for the WOMBAT...
Ok, marking closed then.