[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sda disapering



On 8/15/05, Enrique Morfin <enriquemorfin@yahoo.com> wrote:
> 
> 
> --- Bryan Donlan <bdonlan@gmail.com> wrote:
> 
> > On 8/12/05, Enrique Morfin <enriquemorfin@yahoo.com>
> > wrote:
> > > Hi!
> > >
> > > i'm using sid, kernel image 2.6.10:
> > >
> > > # uname -a
> > > Linux quetzalcoatl 2.6.10-1-686-smp #1 SMP Tue Jan
> > 18
> > > 03:03:11 EST 2005 i686 GNU/Linux
> > >
> > > #uptime
> > >  17:08:44 up 160 days, 23:47,  1 user,  load
> > average:
> > > 0.27, 1.02, 1.77
> > >
> > > My usb memory was working flawlessly (all 160
> > days),
> > > until today.
> > >
> > > Then i realize it is no the memory, anything i
> > insert
> > > in usb (flash memory, mouse, hard drive, etc.).
> > So,
> > > lets take the memory for example:
> > >
> > > When i inser it:
> > >
> > > #dmesg
> > > usb 4-1: new full speed USB device using uhci_hcd
> > and
> > > address 46
> > > scsi50 : SCSI emulation for USB Mass Storage
> > devices
> > > usb-storage: device found at 46
> > > usb-storage: waiting for device to settle before
> > > scanning
> > >   Vendor:           Model:                   Rev:
> > >   Type:   Direct-Access                      ANSI
> > SCSI
> > > revision: 02
> > > SCSI device sda: 1024000 512-byte hdwr sectors
> > (524
> > > MB)
> > > sda: assuming Write Enabled
> > > sda: assuming drive cache: write through
> > > SCSI device sda: 1024000 512-byte hdwr sectors
> > (524
> > > MB)
> > > sda: assuming Write Enabled
> > > sda: assuming drive cache: write through
> > >  /dev/scsi/host50/bus0/target0/lun0: p1
> > > Attached scsi removable disk sda at scsi50,
> > channel 0,
> > > id 0, lun 0
> > > usb-storage: device scan complete
> > >
> > > and:
> > >
> > > #ls -alh /dev/sda*
> > > brw-rw----  1 root disk 8,  0 Aug 12 17:06
> > /dev/sda
> > > brw-rw----  1 root disk 8,  1 Aug 12 17:06
> > /dev/sda1
> > > brw-rw----  1 root disk 8, 10 Mar 14  2002
> > /dev/sda10
> > > brw-rw----  1 root disk 8, 11 Mar 14  2002
> > /dev/sda11
> > > brw-rw----  1 root disk 8, 12 Mar 14  2002
> > /dev/sda12
> > > brw-rw----  1 root disk 8, 13 Mar 14  2002
> > /dev/sda13
> > > brw-rw----  1 root disk 8, 14 Mar 14  2002
> > /dev/sda14
> > > brw-rw----  1 root disk 8, 15 Mar 14  2002
> > /dev/sda15
> > > brw-rw----  1 root disk 8,  2 Mar 14  2002
> > /dev/sda2
> > > brw-rw----  1 root disk 8,  3 Mar 14  2002
> > /dev/sda3
> > > brw-rw----  1 root disk 8,  4 Mar 14  2002
> > /dev/sda4
> > > brw-rw----  1 root disk 8,  5 Mar 14  2002
> > /dev/sda5
> > > brw-rw----  1 root disk 8,  6 Mar 14  2002
> > /dev/sda6
> > > brw-rw----  1 root disk 8,  7 Mar 14  2002
> > /dev/sda7
> > > brw-rw----  1 root disk 8,  8 Mar 14  2002
> > /dev/sda8
> > > brw-rw----  1 root disk 8,  9 Mar 14  2002
> > /dev/sda9
> > >
> > > but, when i disconect it (umounting first):
> > > #ls -alh /dev/sda*
> > > brw-rw----  1 root disk 8, 10 Mar 14  2002
> > /dev/sda10
> > > brw-rw----  1 root disk 8, 11 Mar 14  2002
> > /dev/sda11
> > > brw-rw----  1 root disk 8, 12 Mar 14  2002
> > /dev/sda12
> > > brw-rw----  1 root disk 8, 13 Mar 14  2002
> > /dev/sda13
> > > brw-rw----  1 root disk 8, 14 Mar 14  2002
> > /dev/sda14
> > > brw-rw----  1 root disk 8, 15 Mar 14  2002
> > /dev/sda15
> > > brw-rw----  1 root disk 8,  2 Mar 14  2002
> > /dev/sda2
> > > brw-rw----  1 root disk 8,  3 Mar 14  2002
> > /dev/sda3
> > > brw-rw----  1 root disk 8,  4 Mar 14  2002
> > /dev/sda4
> > > brw-rw----  1 root disk 8,  5 Mar 14  2002
> > /dev/sda5
> > > brw-rw----  1 root disk 8,  6 Mar 14  2002
> > /dev/sda6
> > > brw-rw----  1 root disk 8,  7 Mar 14  2002
> > /dev/sda7
> > > brw-rw----  1 root disk 8,  8 Mar 14  2002
> > /dev/sda8
> > > brw-rw----  1 root disk 8,  9 Mar 14  2002
> > /dev/sda9
> > >
> > > sda and sda1 are gone!!
> > >
> > > i have to recreate them (whit mknod) each time i
> > > disconect someting (flash memory, external hd,
> > etc.)
> > >
> > > Any ideas why is happening this? kernel bug?
> > module
> > > bug? too much time running? hardware failing
> > (intel
> > > 865g)?
> > >
> > > Any ideas how to fix this? reboot? (like
> > windogs?),
> > > remove the module and reload it? update kernel?
> > buy a
> > > new motherboard?
> >
> > Looks like you're using udev. udev automatically
> > deletes and creates
> > /dev entries when the hardware is removed and
> > attached - try
> > reattaching the hardware, the /dev entries should
> > reappear.
> >
> It's not reappering!
> 
> i tried to restarted it, but don't want to start
> (needs 2.6.12 kernel, and i'm running 2.6.10), so i'm
> not running it.
> 
> Any other ideas?

You may have upgraded to the wrong version of udev. Newer versions of
udev require linux-image >= 2.6.12, but there was a version at one
point which failed to properly check. If you're running that broken
version, you'll have problems until you upgrade your kernel.

You can try disabling udev with something like:
killall udevd; rm /dev/.udevdb -rf

Hopefully that'll stop it from running, so your dev entries will stick
around. Otherwise, try downgrading to latest testing udev, or
upgrading to >2.6.12 kernel.



Reply to: