[opensuse] mounting an USB device
Trying to mount a harddisk connected with a IDE/Sata USB hub. Lsusb tells me : Bus 001 Device 005: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge Trying to mount this piece of hardware I get the following information: # mount /dev/bus/usb/001/005 /mnt mount: /dev/bus/usb/001/005 is not a block device As I need to do some copying from this harddisk I would like to know what I should do to get this HD mounted. Ideas? -- Linux User 183145 using LXDE and KDE4 on a Pentium IV , powered by openSUSE 11.4 (i586) Kernel: 3.1.0-rc6-2-desktop LXDE WM & KDE Development Platform: 4.7.1 (4.7.1) 15:13pm up 0:16, 3 users, load average: 3.67, 2.30, 1.39 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/09/20 15:21 (GMT+0700) Constant Brouerius van Nidek composed:
Trying to mount a harddisk connected with a IDE/Sata USB hub. Lsusb tells me : Bus 001 Device 005: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA& PATA Combo Bridge
Trying to mount this piece of hardware I get the following information:
# mount /dev/bus/usb/001/005 /mnt mount: /dev/bus/usb/001/005 is not a block device
As I need to do some copying from this harddisk I would like to know what I should do to get this HD mounted. Ideas?
You don't say which OS you run, so just do 'fdisk -l' to find out what partitions are available and which X in /dev/sdX was assigned to it by whichever USB discovery daemon found it when you attached it. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Tue, Sep 20, 2011 at 05:00:01AM -0400, Felix Miata wrote:
You don't say which OS you run, so just do 'fdisk -l' to find out what partitions are available and which X in /dev/sdX was assigned to it by whichever USB discovery daemon found it when you attached it.
That is a good way. Best run it also before to be able to compare what was added. On some machines it can be confusing. I usually run dmesg to see if the USB device was properly detected and what actual disks and partitions where discovered. fdisk is more precise there because it shows what is a partition and what not. Sometimes /dev/sdb is the device to be mounted and sometimes it is /dev/sdf1. -- Bye, Stephan Barth SUSE LINUX GmbH - Novell Technical Services GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409 Nuremberg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday, September 20, 2011 02:18:41 PM Stephan Barth wrote:
Hi,
On Tue, Sep 20, 2011 at 05:00:01AM -0400, Felix Miata wrote:
You don't say which OS you run, so just do 'fdisk -l' to find out what partitions are available and which X in /dev/sdX was assigned to it by whichever USB discovery daemon found it when you attached it.
That is a good way. Best run it also before to be able to compare what was added. On some machines it can be confusing.
I usually run dmesg to see if the USB device was properly detected and what actual disks and partitions where discovered.
fdisk is more precise there because it shows what is a partition and what not. Sometimes /dev/sdb is the device to be mounted and sometimes it is /dev/sdf1.
fdisk -l did not give me any information about the USB device but your dmesg gave me following: [10628.006088] sd 6:0:0:0: [sdh] Test WP failed, assume Write Enabled [10628.007803] sd 6:0:0:0: [sdh] Asking for cache data failed [10628.007812] sd 6:0:0:0: [sdh] Assuming drive cache: write through [10628.011793] sd 6:0:0:0: [sdh] Test WP failed, assume Write Enabled [10628.012914] sd 6:0:0:0: [sdh] Asking for cache data failed [10628.012922] sd 6:0:0:0: [sdh] Assuming drive cache: write through [10628.012930] sd 6:0:0:0: [sdh] Attached SCSI disk At least the drive is attached but does not seem to respond. -- Linux User 183145 using LXDE and KDE4 on a Pentium IV , powered by openSUSE 11.4 (i586) Kernel: 3.1.0-rc6-2-desktop LXDE WM & KDE Development Platform: 4.7.1 (4.7.1) 20:26pm up 5:29, 3 users, load average: 2.37, 1.18, 0.94 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2011-09-20 at 15:21 +0700, Constant Brouerius van Nidek wrote:
Trying to mount a harddisk connected with a IDE/Sata USB hub. Lsusb tells me : Bus 001 Device 005: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Trying to mount this piece of hardware I get the following information:
# mount /dev/bus/usb/001/005 /mnt mount: /dev/bus/usb/001/005 is not a block device
Obviously; you have to give a device name like sdb, sdc, etc. Just look at the last lines of /var/log/messages, or the output of dmesg: it will say the device name. Then you have to find out the partition number. But typically the desktop (kde, gnome) will offer to mount it automatically. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk54jUwACgkQtTMYHG2NR9VUgQCgjGDLUKrBtZPAAYKBrck8Sa2H 42AAoJAamDdyC0ST1f7jvRzYssinFyc0 =qvYG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. said the following on 09/20/2011 08:55 AM:
Just look at the last lines of /var/log/messages, or the output of dmesg: it will say the device name. Then you have to find out the partition number.
Indeed. You can run 'sudo tail -f /var/log/messages' while inserting and removing the USB device and see what the kernel thinks the various settings and characteristics are.
But typically the desktop (kde, gnome) will offer to mount it automatically.
True, but its possible that some setup might need to be done. It is - out there on the boundary of improbability - that the entry in the .IDS file for that particular vendor and device is absent. Just a thought. -- The surest way to corrupt a youth is to instruct him to hold in higher esteem those who think alike than those who think differently. -- Friedrich Nietzsche -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2011-09-20 at 09:12 -0400, Anton Aylward wrote: Just a note :-)
You can run 'sudo tail -f /var/log/messages'
Better use instead "tailf" - less HD ussage. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk54lUUACgkQtTMYHG2NR9UV+QCfVwKEIMu0IVk/u864YC231xak ayYAn3yL7Tg6bfG8yzz2wpa1nHlT8p5B =dHNA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. said the following on 09/20/2011 09:29 AM:
On Tuesday, 2011-09-20 at 09:12 -0400, Anton Aylward wrote:
Just a note :-)
You can run 'sudo tail -f /var/log/messages'
Better use instead "tailf" - less HD ussage.
+1 :-) -- "Each new law makes only a single guarantee. It will create new criminals." -- John Tandervold -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday, September 20, 2011 09:12:25 AM Anton Aylward wrote:
sudo tail -f /var/log/messages
Thanks. The latest info I got from above reads: Sep 20 20:25:04 dhcppc4 kernel: [19659.121101] FAT-fs (sdh): unable to read boot sector Which gives me the reason I presume why I have a problem connecting. This pure fat 16 drive is probably at the end of its usable life? Or are there other reasons for this information? -- Linux User 183145 using LXDE and KDE4 on a Pentium IV , powered by openSUSE 11.4 (i586) Kernel: 3.1.0-rc6-2-desktop LXDE WM & KDE Development Platform: 4.7.1 (4.7.1) 20:33pm up 5:36, 3 users, load average: 0.73, 0.95, 0.93 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Tue, Sep 20, 2011 at 08:36:49PM +0700, Constant Brouerius van Nidek wrote:
Thanks. The latest info I got from above reads: Sep 20 20:25:04 dhcppc4 kernel: [19659.121101] FAT-fs (sdh): unable to read boot sector
Which gives me the reason I presume why I have a problem connecting. This pure fat 16 drive is probably at the end of its usable life? Or are there other reasons for this information?
Doesn't sound good, but I would rather test it on a different USB port on the same machine and also on another PC and a different OS if possible, before giving up on it. -- Bye, Stephan Barth SUSE LINUX GmbH - Novell Technical Services GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409 Nuremberg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 9/20/2011 6:36 AM, Constant Brouerius van Nidek wrote:
On Tuesday, September 20, 2011 09:12:25 AM Anton Aylward wrote:
sudo tail -f /var/log/messages
Thanks. The latest info I got from above reads: Sep 20 20:25:04 dhcppc4 kernel: [19659.121101] FAT-fs (sdh): unable to read boot sector
Which gives me the reason I presume why I have a problem connecting. This pure fat 16 drive is probably at the end of its usable life? Or are there other reasons for this information?
Very odd that it would even try to read the boot sector. I use several external HDDs in IDE/Sata-to-USB enclosures, and they all mount just fine by plugging them in (OS 11.4/KDE4.6x). They all show up in Dolphin under /media and even the NTFS ones are readable. Even known bad disks mount this way, and are sometime functional enough to get some data off of even when they are unbootable). (Apparently 11.4 installs ntfs-3g by default or I did it somewhere along the way). -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/09/20 09:58 (GMT-0700) John Andersen composed:
(Apparently 11.4 installs ntfs-3g by default or I did it somewhere along the way).
It's been installed by default regardless whether NTFS partitions exist at installation time. I don't know when that policy began, but certainly by 11.4. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata said the following on 09/20/2011 01:27 PM:
On 2011/09/20 09:58 (GMT-0700) John Andersen composed:
(Apparently 11.4 installs ntfs-3g by default or I did it somewhere along the way).
It's been installed by default regardless whether NTFS partitions exist at installation time. I don't know when that policy began, but certainly by 11.4.
And you can always check /proc/filesystems to make sure the ntfs-3g module is loaded. -- Education is a better safeguard of liberty than a standing army. --Edward Everett -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-09-20 18:58, John Andersen wrote:
On 9/20/2011 6:36 AM, Constant Brouerius van Nidek wrote:
Very odd that it would even try to read the boot sector. ... Even known bad disks mount this way, and are sometime functional enough to get some data off of even when they are unbootable).
If boot sector is not readable, then it is not mountable. I think in this case it is the MBR, so no partition table. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk54zvcACgkQtTMYHG2NR9Vr5gCeLrMimN1hujBMxHCfn+t0OjIM oCcAnjW0Df5svuZXMlZVXGXzZrwvRxSe =nlKy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. said the following on 09/20/2011 01:35 PM:
On 2011-09-20 18:58, John Andersen wrote:
On 9/20/2011 6:36 AM, Constant Brouerius van Nidek wrote:
Very odd that it would even try to read the boot sector. ... Even known bad disks mount this way, and are sometime functional enough to get some data off of even when they are unbootable).
If boot sector is not readable, then it is not mountable. I think in this case it is the MBR, so no partition table.
Isn't there something you can do with 'dd' to overcome this? -- "Opportunity is missed by most people because it is dressed in overalls and looks like work." -- Thomas A. Edison -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2011-09-20 at 14:31 -0400, Anton Aylward wrote:
Isn't there something you can do with 'dd' to overcome this?
Perhaps. Rather with dd-rescue, which can skip i/o errors. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk548vwACgkQtTMYHG2NR9WOngCfdI1+bsPgTz2d9zPvoUg4ppJM JmEAnAiJNAlEXJXIvYsUlb8gGuEakDpr =SRhG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Anton Aylward -
Carlos E. R. -
Constant Brouerius van Nidek -
Felix Miata -
John Andersen -
Stephan Barth