You are not logged in.
I have this weird problem that I can't mount my USB HD anymore since the last reboot.
I can see that it is connected in /var/log/messages, but the block device that is mentioned in the log just isn't created. I have no idea what's going on, since it worked perfectly before.
Here's the relevant portion of the log:
Oct 12 18:01:49 kumquad usb 5-4: new high speed USB device using ehci_hcd and address 8
Oct 12 18:01:49 kumquad usb 5-4: configuration #2 chosen from 1 choice
Oct 12 18:01:49 kumquad scsi6 : SCSI emulation for USB Mass Storage devices
Oct 12 18:01:54 kumquad scsi 6:0:0:0: Direct-Access TOSHIBA MK6006GAH BY00 PQ: 0 ANSI: 0 CCS
Oct 12 18:01:54 kumquad sd 6:0:0:0: [sdb] 117210240 512-byte hardware sectors (60012 MB)
Oct 12 18:01:54 kumquad sd 6:0:0:0: [sdb] Write Protect is off
Oct 12 18:01:54 kumquad sd 6:0:0:0: [sdb] 117210240 512-byte hardware sectors (60012 MB)
Oct 12 18:01:54 kumquad sd 6:0:0:0: [sdb] Write Protect is off
Oct 12 18:01:54 kumquad sdb: sdb1
Oct 12 18:01:54 kumquad sd 6:0:0:0: [sdb] Attached SCSI disk
Oct 12 18:01:54 kumquad sd 6:0:0:0: Attached scsi generic sg2 type 0
I think I'm correct in assuming that this means I should find the drive under /dev/sdb1, but it just doesn't exist.
Last edited by kamagurka (2007-10-13 13:25:33)
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
Umm, help? Even a "yes, your assumption is correct, and this is weird" would be helpful now.
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
So ls -l /dev/sdb1 gives "file not found"? Yes, your assumption is correct, and this is weird. :]
1000
Offline
OK, a reboot fixed it. Which pisses me off, as I hate rebooting to solve a problem, and still don't have a way to fix it next time it comes up, but I needed to move my computer, so there.
I always roll 20s on my disbelieve checks.
You better believe it.
Offline
This problem almost certainly would be related to udev, but I have no idea why it would have happened unless you have some custom rules that might have interfered with the creation of the device node, but I doubt that would be the case since it worked after a reboot.
If it does happen again, you could just try restarting udev with "/etc/rc.d/udev restart" as root, which might be as good as a reboot to fix it.
Offline