Announcement

**toad** · Jan 06, 2009, 03:45 PM

Re: USB drives not recognised or automounted.

Two suggestions for further checking:

plug a stick in and run

Code:

dmesg

Wot says?

Also, you might want to try and restart hal:

Code:

sudo /etc/init.d/hald restart

and repeat the above.

**bag** · Jan 06, 2009, 03:56 PM

Re: USB drives not recognised or automounted.

Hey Toad,

Thanks for the reply.

dmesg returns:

Code:

[122048.080540] sd 3:0:0:0: [sdf] Sense Key : No Sense [current]
[122048.080548] sd 3:0:0:0: [sdf] Add. Sense: No additional sense information
[122049.912606] sd 3:0:0:0: [sdf] Sense Key : No Sense [current]
[122049.912606] sd 3:0:0:0: [sdf] Add. Sense: No additional sense information
[122051.732537] usb 2-5: new high speed USB device using ehci_hcd and address 12
[122051.744885] sd 3:0:0:0: [sdf] Sense Key : No Sense [current]
[122051.744885] sd 3:0:0:0: [sdf] Add. Sense: No additional sense information
[122051.876522] usb 2-5: configuration #1 chosen from 1 choice
[122051.877524] scsi13 : SCSI emulation for USB Mass Storage devices
[122051.877824] usb-storage: device found at 12
[122051.877824] usb-storage: waiting for device to settle before scanning
[122053.580568] sd 3:0:0:0: [sdf] Sense Key : No Sense [current]
[122053.580568] sd 3:0:0:0: [sdf] Add. Sense: No additional sense information
[122055.412589] sd 3:0:0:0: [sdf] Sense Key : No Sense [current]
[122055.412589] sd 3:0:0:0: [sdf] Add. Sense: No additional sense information

And here may be something that is causing the problem... trying to restart hald pops up the following...

Code:

sudo: /etc/init.d/hald: command not found

Does this mean that hald has been uninstalled? I am by no means up to speed with these things, but hald is a basic component of linux isn't it? It really should be there, shouldn't it? I mean, it hasn't been superseded by something under KDE4 or whatever?

Should I just run?:

Code:

sudo apt-get install hald

Could this solve my problem?

Thanks.

Bag.

**toad** · Jan 06, 2009, 04:08 PM

Re: USB drives not recognised or automounted.

hald is the daemon, hal the package. hal should, no must have been installed from the install CD.

You could also try

Code:

sudo /etc/init.d/hal start

and with any luck it wasn't running in the first place. Now try again...

**bag** · Jan 06, 2009, 04:21 PM

Re: USB drives not recognised or automounted.

OK, so I've restarted hal and it worked fine... gave notice that it was restarting, no problems.

Then I plugged in a USB thumb drive and got the following in dmesg:

Code:

123598.752563] usb 2-5: new high speed USB device using ehci_hcd and address 13                                
[123598.892978] usb 2-5: configuration #1 chosen from 1 choice                                         
[123598.892994] scsi14 : SCSI emulation for USB Mass Storage devices                                      
[123598.900618] usb-storage: device found at 13                                                
[123598.900623] usb-storage: waiting for device to settle before scanning                                   
[123599.008581] sd 3:0:0:0: [sdf] Sense Key : No Sense [current]                                        
[123599.008581] sd 3:0:0:0: [sdf] Add. Sense: No additional sense information
[123600.840803] sd 3:0:0:0: [sdf] Sense Key : No Sense [current]
[123600.840803] sd 3:0:0:0: [sdf] Add. Sense: No additional sense information
[123602.676638] sd 3:0:0:0: [sdf] Sense Key : No Sense [current]
[123602.676638] sd 3:0:0:0: [sdf] Add. Sense: No additional sense information
[123603.900682] usb-storage: device scan complete
[123603.901017] scsi 14:0:0:0: Direct-Access   Verbatim STORE N GO    5.00 PQ: 0 ANSI: 0 CCS
[123603.905433] scsi 14:0:0:0: Attached scsi generic sg9 type 0

Which shows that it was registered as being there. But still, no joy on being notified, or not there in /media

Any ideas?

**magic-chef** · Jan 06, 2009, 06:11 PM

Re: USB drives not recognised or automounted.

I am having a similar problem with USB. I purchased a USB hard drive and get no notification when plugged in. I have followed the recommendations above with no success. Is there a way to get the drives to show up in my computer. I have IDE drives that show up.

Is there a CLI command that will mount the USB device?

**dibl** · Jan 06, 2009, 06:53 PM

Re: USB drives not recognised or automounted.

Run

Code:

lspci

and make sure the device is being seen by your hardware.

**magic-chef** · Jan 06, 2009, 08:14 PM

Re: USB drives not recognised or automounted.

[code]I ran the command and this result:

richard@yyyyyy:~$ dmesg

[ 4.688692] usbcore: registered new interface driver usbfs
[ 4.688759] usbcore: registered new interface driver hub
[ 4.692438] usbcore: registered new device driver usb
[ 4.702109] USB Universal Host Controller Interface driver v3.0
[ 4.702237] uhci_hcd 0000:00:11.2: PCI INT D -> GSI 21 (level, low) -> IRQ 21
[ 4.702256] uhci_hcd 0000:00:11.2: UHCI Host Controller
[ 4.702375] uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
[ 4.702430] uhci_hcd 0000:00:11.2: irq 21, io base 0x0000a400
[ 4.702807] usb usb1: configuration #1 chosen from 1 choice
[ 4.702866] hub 1-0:1.0: USB hub found
[ 4.702890] hub 1-0:1.0: 2 ports detected
[ 4.705032] libata version 3.00 loaded.
[ 4.908749] uhci_hcd 0000:00:11.3: PCI INT D -> GSI 21 (level, low) -> IRQ 21
[ 4.908773] uhci_hcd 0000:00:11.3: UHCI Host Controller
[ 4.908832] uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 2
[ 4.908870] uhci_hcd 0000:00:11.3: irq 21, io base 0x0000a000
[ 4.909217] usb usb2: configuration #1 chosen from 1 choice
[ 4.909275] hub 2-0:1.0: USB hub found
[ 4.909297] hub 2-0:1.0: 2 ports detected
[ 5.116706] pata_acpi 0000:00:11.1: can't derive routing for PCI INT A
[ 5.116826] pata_acpi 0000:00:11.1: can't derive routing for PCI INT A
[ 5.124262] pata_via 0000:00:11.1: version 0.3.3
[ 5.124293] pata_via 0000:00:11.1: can't derive routing for PCI INT A
[ 5.126309] scsi0 : pata_via
[ 5.126683] scsi1 : pata_via
[ 5.127923] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xa800 irq 14
[ 5.127931] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xa808 irq 15
[ 5.345453] ata1.00: ATA-7: MAXTOR STM3160812A, 3.AAJ, max UDMA/100
[ 5.345463] ata1.00: 312581808 sectors, multi 16: LBA48
[ 5.346264] ata1.01: ATA-4: WDC WD102AA, 82.10A82, max UDMA/66
[ 5.346272] ata1.01: 20044080 sectors, multi 16: LBA
[ 5.411976] ata1.00: configured for UDMA/100
[ 5.429126] ata1.01: configured for UDMA/66
[ 5.616477] ata2.00: ATAPI: ATAPI DVD A DH20A1P, 6X14, max UDMA/66
[ 5.616511] ata2.01: ATAPI: CREATIVE CD-RW RW8433E, 1R04, max MWDMA2
[ 5.648363] ata2.00: configured for UDMA/66
[ 5.664360] ata2.01: configured for MWDMA2
[ 5.664643] scsi 0:0:0:0: Direct-Access ATA MAXTOR STM316081 3.AA PQ: 0 ANSI: 5
[ 5.664970] scsi 0:0:1:0: Direct-Access ATA WDC WD102AA 82.1 PQ: 0 ANSI: 5
[ 5.666355] scsi 1:0:0:0: CD-ROM ATAPI DVD A DH20A1P 6X14 PQ: 0 ANSI: 5
[ 5.667745] scsi 1:0:1:0: CD-ROM CREATIVE CD-RW RW8433E 1R04 PQ: 0 ANSI: 5
[ 6.319254] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[ 6.319353] scsi 0:0:1:0: Attached scsi generic sg1 type 0
[ 6.319435] scsi 1:0:0:0: Attached scsi generic sg2 type 5
[ 6.319516] scsi 1:0:1:0: Attached scsi generic sg3 type 5
[ 6.420868] Driver 'sd' needs updating - please use bus_type methods
[ 6.421147] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[ 6.421191] sd 0:0:0:0: [sda] Write Protect is off
[ 6.421196] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 6.421259] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.421434] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
[ 6.421471] sd 0:0:0:0: [sda] Write Protect is off
[ 6.421476] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 6.421535] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.421547] sda:<4>Driver 'sr' needs updating - please use bus_type methods
[ 6.441051] sda1 sda2 < sda5 >
[ 6.468699] sd 0:0:0:0: [sda] Attached SCSI disk
[ 6.468975] sd 0:0:1:0: [sdb] 20044080 512-byte hardware sectors (10263 MB)
[ 6.469021] sd 0:0:1:0: [sdb] Write Protect is off
[ 6.469027] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[ 6.469097] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.469268] sd 0:0:1:0: [sdb] 20044080 512-byte hardware sectors (10263 MB)
[ 6.469308] sd 0:0:1:0: [sdb] Write Protect is off
[ 6.469313] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[ 6.469381] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6.469392] sdb: sdb1 sdb2 < sdb5 >
[ 6.497681] sd 0:0:1:0: [sdb] Attached SCSI disk
[ 6.509785] sr0: scsi3-mmc drive: 62x/125x writer dvd-ram cd/rw xa/form2 cdda tray
[ 6.509798] Uniform CD-ROM driver Revision: 3.20
[ 6.510031] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 6.512192] sr1: scsi3-mmc drive: 8x/32x writer cd/rw xa/form2 cdda tray
[ 6.512426] sr 1:0:1:0: Attached scsi CD-ROM sr1
[ 7.099853] PM: Starting manual resume from disk
[ 7.099866] PM: Resume from partition 8:5
[ 7.099869] PM: Checking hibernation image.
[ 7.100185] PM: Resume from disk failed.
[ 7.185239] kjournald starting. Commit interval 5 seconds
[ 7.185277] EXT3-fs: mounted filesystem with ordered data mode.
[ 15.056898] udevd version 124 started
[ 16.318653] Linux agpgart interface v0.103
[ 16.413457] agpgart: Detected VIA KT266/KY266x/KT333 chipset
[ 16.434359] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 16.436207] agpgart-via 0000:00:00.0: AGP aperture is 64M @ 0xe0000000
[ 16.469998] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 17.403008] input: PC Speaker as /devices/platform/pcspkr/input/input2

[ 24.405506] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 24.405519] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 24.405529] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 24.405540] end_request: I/O error, dev sr0, sector 40
[ 24.405553] Buffer I/O error on device sr0, logical block 5
[ 24.405570] Buffer I/O error on device sr0, logical block 6
[ 24.405577] Buffer I/O error on device sr0, logical block 7
[ 24.405583] Buffer I/O error on device sr0, logical block 8
[ 24.405588] Buffer I/O error on device sr0, logical block 9
[ 24.405594] Buffer I/O error on device sr0, logical block 10
[ 24.405600] Buffer I/O error on device sr0, logical block 11
[ 24.405606] Buffer I/O error on device sr0, logical block 12
[ 24.405612] Buffer I/O error on device sr0, logical block 13
[ 24.405617] Buffer I/O error on device sr0, logical block 14
[ 24.456996] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 24.457010] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 24.457019] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 24.457030] end_request: I/O error, dev sr0, sector 240
[ 24.460290] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 24.460305] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 24.460314] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 24.460325] end_request: I/O error, dev sr0, sector 240
[ 24.464219] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 24.464233] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 24.464242] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 24.464253] end_request: I/O error, dev sr0, sector 240
[ 25.161906] firmware: requesting ess/maestro3_assp_minisrc.fw
[ 26.912645] lp0: using parport0 (interrupt-driven).
[ 27.238695] Adding 746980k swap on /dev/sda5. Priority:-1 extents:1 across:746980k
[ 27.865935] EXT3 FS on sda1, internal journal
[ 28.179703] device-mapper: uevent: version 1.0.3
[ 28.182842] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
[ 29.983796] __ratelimit: 16 callbacks suppressed

[ 64.060506] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 64.060515] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 64.060525] end_request: I/O error, dev sr0, sector 64
[ 64.060594] Buffer I/O error on device sr0, logical block 8
[ 64.227896] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 64.227915] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 64.227924] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 64.227936] end_request: I/O error, dev sr0, sector 112
[ 64.228016] Buffer I/O error on device sr0, logical block 14
[ 64.228074] Buffer I/O error on device sr0, logical block 15
[ 64.228130] Buffer I/O error on device sr0, logical block 16
[ 64.228186] Buffer I/O error on device sr0, logical block 17
[ 64.228241] Buffer I/O error on device sr0, logical block 18
[ 64.228296] Buffer I/O error on device sr0, logical block 19
[ 64.228352] Buffer I/O error on device sr0, logical block 20
[ 64.228407] Buffer I/O error on device sr0, logical block 21
[ 64.266628] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 64.266646] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 64.266655] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 64.266666] end_request: I/O error, dev sr0, sector 64
[ 64.270521] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 64.270541] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 64.270549] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 64.270560] end_request: I/O error, dev sr0, sector 64
[ 64.274444] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 64.274462] sr 1:0:0:0: [sr0] Sense Key : Hardware Error [current]
[ 64.274471] sr 1:0:0:0: [sr0] Add. Sense: Logical unit communication CRC error (Ultra-DMA/32)
[ 64.274482] end_request: I/O error, dev sr0, sector 64
[ 64.277934] sr 1:0:0:0: [sr0] Re

**magic-chef** · Jan 06, 2009, 08:15 PM

Re: USB drives not recognised or automounted.

Sorry for the long post previous to this. I was not sure what was important.

**toad** · Jan 07, 2009, 01:53 AM

Re: USB drives not recognised or automounted.

@ magic-chef

Could you please use the the quote and code block commands to make long posts more readable. Also, have you tried starting the hal daemon?

@ bag

Normally dmesg tells us where a device was mounted - not in your case, however. Go with dibl's recommendation and post the result.

**bag** · Jan 07, 2009, 06:19 AM

Re: USB drives not recognised or automounted.

Dibl,

I've tried lspci and it returns:

Code:

@kubuntu-desktop:~$ lspci
00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP55 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2)
00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1)
00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
00:06.0 PCI bridge: nVidia Corporation MCP55 PCI bridge (rev a2)
00:06.1 Audio device: nVidia Corporation MCP55 High Definition Audio (rev a2)
00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
00:0d.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
00:0f.0 PCI bridge: nVidia Corporation MCP55 PCI Express bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
01:00.3 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev 46)
01:02.0 SCSI storage controller: Adaptec AHA-2930CU (rev 03)
06:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GS] (rev a1)

However, I'm not sure that you wanted that... Did you really mean to run: lsusb

Output of lsusb was posted earlier.

It's just that these are usb drives - so don't understand why they might be visible on the PCI side of things. Am I missing something??

I'm getting confused with the dmesg thing. Normally, it should show not only that it registered me plugging in a device, but also where it has mounted it. It does the first thing - I can see that it's registered but it doesn't show where it's mounted.

What are the system processes that govern how a device is allocated a mount point etc? Obviously, this doesn't seem to be happening, so can I check if there's something gone wrong there?

This is (almost) a fresh install. It's only basically been installed, updated, and had some packages installed. This hasn't gone through an update from 8.04 to 8.10 (which is what borked it last time and required a complete reinstall).

Any advice would be much appreciated.

Bag.

**dibl** · Jan 07, 2009, 09:05 AM

Re: USB drives not recognised or automounted.

Interesting -- there appear to be two or even three different models of USB controller, from two different manufacturers, on the motherboard -- I dunno whether that is relevant to the issues or not.

You have said "not mounted", but USB devices are not supposed to be mounted (via the linux "mount" command) automatically when they are plugged in, as far as I know. They are, however, supposed to be detected and accessible via the HAL and/or udev driver, so you can open them and use them. Remember, there are many kinds of USB devices that are not for storage, so they are not assumed by the OS to be hard drives or storage devices. If you want to mount USB storage devices using the "mount" command, you can certainly do so -- you can also usually right-click them in a GUI window like Dolphin, and choose "mount" to mount them that way.

You can probably learn a lot (maybe more than you want to know) by reviewing this:

https://bugzilla.redhat.com/show_bug...iple&id=473017

**toad** · Jan 07, 2009, 09:19 AM

Re: USB drives not recognised or automounted.

So you have an onboard usb device and a pci card? Try one, do dmesg, try the other, do dmesg. If still no joy, disable onboard usb and repeat.

Google USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) and nVidia Corporation MCP55 USB Controller (rev a1) and see what they say.

**bag** · Jan 07, 2009, 02:38 PM

Re: USB drives not recognised or automounted.

Dibl,

You're a star. Please help me to understand here though. In the link to redhat's bug tracker, it's basically saying that this is caused by a problem in the kernel. Is that right? A commit that is looking at RAID arrays...

It also mentions that it's causing damage to RAID arrays because it's looking for the wrong thing - is that right?

My two hard drives (that have now died - or so I thought) were initially set up in a RAID array.

I can't seem to see how to try their workaround though. This will be because of differences between Fedora and Ubuntu setup. Can you point me in the right direction to try and get their workaround working on my system? I've found the "/etc/udev/rules.d/60-persistent-storage.rules" file and backed it up before looking into it to change. It doesn't seem to have the line that needs changing in it.

I can't find the phrase: KERNEL!="sr*", IMPORT{program}="vol_id --export $tempnode"

anywhere in the file.

So I'm a bit stuck here. Any ideas on how to get the workaround working on my system?

Other points - I'd forgotten that I had a Firewire card in the PC that has multiple USB ports on it. However, it's badly designed and I can't use any of the USB ports because they all clash with the rear facia of the computer. Impossible to plug anything in since it can't get past the rear of the case.

I understand now the difference about mounting USB devices, but still, it should be assigned a device and partition though, shouldn't it? Something like sdb1 or whatever. Anyway my USB drives (and USB thumb/pen drives) don't seem to get this - otherwise, I could mount them by changing fstab (I presume).

Later on, will try to reboot using a different kernel to see if the same thing happens there. Hadn't really thought about it but the bugzilla report on Fedora mentions that it might be kernel specific. Will see if my other kernel has the same problem. (Feel a bit red-faced that I haven't tried this previously! D'oh!)

Toad - another good suggestion. Will try that after rebooting with a different kernel.

Will get back to you both.

Thanks.

Bag.

**magic-chef** · Jan 07, 2009, 07:17 PM

Re: USB drives not recognised or automounted.

Originally posted by toad

@ magic-chef

Could you please use the the quote and code block commands to make long posts more readable. Also, have you tried starting the hal daemon?

@ bag

Normally dmesg tells us where a device was mounted - not in your case, however. Go with dibl's recommendation and post the result.

Oops!. I accidentally erased the closing code tag when I was cleaning up the output a little.

Yes, i restarted hald.

Announcement

USB drives not recognised or automounted.

USB drives not recognised or automounted.

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment