Unable to mount Pendrive
Hi All,
I have a RHEL5 machine here and trying to use 2GB pendrive on it. But i am getting error "can't mount device" How can i make it mountable ? Is there any way where I can change the settings and use my flashdrive(pendrive) ? Thank You in advance, Kapil |
Plug in pendrive and then run dmesg from the command line. Give us the last 20 or so lines from the output to determine the problem or how to mount the drive.
|
If you're not the administrator, you may not be allowed to mount other drives for security reasons.
|
Flash drives mounting
Quote:
Otherwise, how can i reinstall the device ? Our admin is in other office, but i am free to uninstall/reinstall devices. So may be i can do that here.. Thanks for the concern... Kapil. |
Quote:
|
Quote:
I tried again, but got the same error. I am attaching first 30 lines of the output from 'dmesg' command: Linux version 2.6.18-53.el5 (brewbuilder@hs20-bc1-7.build.redhat.com) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Oct 10 16:34:19 EDT 2007 Command line: ro root=LABEL=/ rhgb quiet BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000008f000 (usable) BIOS-e820: 000000000008f000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000007e666000 (usable) BIOS-e820: 000000007e666000 - 000000007e705000 (ACPI NVS) BIOS-e820: 000000007e705000 - 000000007f595000 (usable) BIOS-e820: 000000007f595000 - 000000007f59d000 (reserved) BIOS-e820: 000000007f59d000 - 000000007f62b000 (usable) BIOS-e820: 000000007f62b000 - 000000007f62f000 (reserved) BIOS-e820: 000000007f62f000 - 000000007f6a9000 (usable) BIOS-e820: 000000007f6a9000 - 000000007f6e9000 (ACPI NVS) BIOS-e820: 000000007f6e9000 - 000000007f6ed000 (usable) BIOS-e820: 000000007f6ed000 - 000000007f6ff000 (ACPI data) BIOS-e820: 000000007f6ff000 - 000000007f700000 (usable) BIOS-e820: 000000007f700000 - 0000000080000000 (reserved) BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) DMI 2.4 present. ACPI: RSDP (v000 INTEL ) @ 0x00000000000fe020 ACPI: RSDT (v001 INTEL D945GCR 0x00000011 0x01000013) @ 0x000000007f6fd038 ACPI: FADT (v001 INTEL D945GCR 0x00000011 MSFT 0x01000013) @ 0x000000007f6fc000 ACPI: MADT (v001 INTEL D945GCR 0x00000011 MSFT 0x01000013) @ 0x000000007f6f6000 ACPI: WDDT (v001 INTEL D945GCR 0x00000011 MSFT 0x01000013) @ 0x000000007f6f5000 ACPI: MCFG (v001 INTEL D945GCR 0x00000011 MSFT 0x01000013) @ 0x000000007f6f4000 ACPI: ASF! (v032 INTEL D945GCR 0x00000011 MSFT 0x01000013) @ 0x000000007f6f3000 ACPI: HPET (v001 INTEL D945GCR 0x00000011 MSFT 0x01000013) @ 0x000000007f6f2000 ACPI: SSDT (v001 INTEL CpuPm 0x00000011 MSFT 0x01000013) @ 0x000000007f6f1000 ACPI: SSDT (v001 INTEL Cpu0Ist 0x00000011 MSFT 0x01000013) @ 0x000000007f6f0000 ACPI: SSDT (v001 INTEL Cpu1Ist 0x00000011 MSFT 0x01000013) @ 0x000000007f6ef000 ACPI: SSDT (v001 INTEL Cpu2Ist 0x00000011 MSFT 0x01000013) @ 0x000000007f6ee000 ACPI: SSDT (v001 INTEL Cpu3Ist 0x00000011 MSFT 0x01000013) @ 0x000000007f6ed000 ACPI: DSDT (v001 INTEL D945GCR 0x00000011 MSFT 0x01000013) @ 0x0000000000000000 No NUMA configuration found Faking a node at 0000000000000000-000000007f700000 Bootmem setup node 0 0000000000000000-000000007f700000 Memory for crash kernel (0x0 to 0x0) notwithin permissible range disabling kdump On node 0 totalpages: 513249 DMA zone: 2694 pages, LIFO batch:0 DMA32 zone: 510555 pages, LIFO batch:31 ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 6:15 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 6:15 APIC version 20 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to physical flat ACPI: HPET id: 0x8086a201 base: 0xfed00000 Using ACPI (MADT) for SMP configuration information Nosave address range: 000000000008f000 - 00000000000a0000 Nosave address range: 00000000000a0000 - 00000000000e0000 Nosave address range: 00000000000e0000 - 0000000000100000 Nosave address range: 000000007e666000 - 000000007e705000 Nosave address range: 000000007f595000 - 000000007f59d000 Nosave address range: 000000007f62b000 - 000000007f62f000 Nosave address range: 000000007f6a9000 - 000000007f6e9000 Nosave address range: 000000007f6ed000 - 000000007f6ff000 Allocating PCI resources starting at 88000000 (gap: 80000000:7ff80000) SMP: Allowing 4 CPUs, 2 hotplug CPUs Built 1 zonelists. Total pages: 513249 Kernel command line: ro root=LABEL=/ rhgb quiet Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Checking aperture... Memory: 2046948k/2087936k available (2434k kernel code, 39524k reserved, 1235k data, 192k init) Calibrating delay using timer specific routine.. 4392.15 BogoMIPS (lpj=2196079) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K using mwait in idle threads. CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 CPU0: Thermal monitoring enabled (TM2) SMP alternatives: switching to UP code ACPI: Core revision 20060707 Using local APIC timer interrupts. result 12468782 Detected 12.468 MHz APIC timer. Do suggest me, if i need to do something else Thank you, Kapil. |
Quote:
|
Quote:
below is the output of the given command :dmesg | tail -n 20 usb 5-5: USB disconnect, address 2 usb 5-5: new high speed USB device using ehci_hcd and address 3 usb 5-5: configuration #1 chosen from 1 choice scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning Vendor: JetFlash Model: TS2GJFV30 Rev: 0.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sdb: 3964928 512-byte hdwr sectors (2030 MB) sdb: Write Protect is off sdb: Mode Sense: 00 00 00 00 sdb: assuming drive cache: write through SCSI device sdb: 3964928 512-byte hdwr sectors (2030 MB) sdb: Write Protect is off sdb: Mode Sense: 00 00 00 00 sdb: assuming drive cache: write through sdb: unknown partition table sd 3:0:0:0: Attached scsi removable disk sdb sd 3:0:0:0: Attached scsi generic sg1 type 0 usb-storage: device scan complete [oracle@anthurium ~]$ Thank you, Kapil. |
Quote:
|
Quote:
|
looks like you have plugged a completely blank keydrive in, or one with a corrupt partition table.
you could try Code:
fdisk -l /dev/sdb (tip when you post some output enclose it in [code] and [/code] tags to make it easier to read |
Quote:
The device is working fine with other windows machines. It is not working only with the RHEL machine. It contains data as well, and it is not blank. It contains the installers for various products, we have here. I think, having data or not, is a matter of concern once the devices got recognized. Thank You, Kapil. |
Quote:
The device is working fine with other windows machines. It is not working only with the RHEL machine. It contains data as well, and it is not blank. It contains the installers for various products, we have here. I think, having data or not in the device, is a matter of concern once the devices got recognized. Thank You, Kapil. |
Quote:
The device is working fine with other windows machines. It is not working only with the RHEL machine. It contains data as well, and it is not blank. It contains the installers for various products, we have here. I think, having data or not, is a matter of concern once the devices got recognized. If required, then i have to take backup of this data first and then I can format it, but is it essential ?? Thank You, Kapil. |
Sounds to me then you have a pen drive only recognizable by windows. In windows, can you find out how it's formatted? Anything else special about this pen drive, make/model?
|
I have two pen drives.
One is called Transcend Jetflash which could not be accessed by Mandriva 10.1, Debian Sarge and most Linux of that era and older, but it sometimes could be seen by Mandriva 10.2 and any Linux OS newer than that. But every now and then it disappears from the Linux OSs. The cure would be to boot into Windows (as Windows could always read it) and back up any data and re-format it. Then it would be visible again for a little while by most Linux, but would eventually disappear again and required another format job. The only difference though, is that when it disappears, nothing shows up when it's plugged in, no error, nothing saying it cannot be mounted, nothing! My Sandisk Cruiser never had this issue with any Linux OS. |
All times are GMT -5. The time now is 05:20 PM. |