I hope this is the right place for this question.... sorry if not!
I have a NAS running Linux which is having some problems and I'm trying
to save my data before doing a factory-restore.
I can log in using telnet and have managed to mount the internal drive
(which contains the data I want to save). I want to use an external USB
drive to save the data on. I've plugged the drive in, but can't work out
how to get the system to recognise it.
dmesg gives:
[snip]
ehci_platform ehci_platform.4523: EHCI Host Controller
ehci_platform ehci_platform.4523: new USB bus registered, assigned bus number 1
ehci_platform ehci_platform.4523: irq 17, io mem 0x00000000
ehci_platform ehci_platform.4523: park 0
ehci_platform ehci_platform.4523: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ehci_platform ehci_platform.16781: EHCI Host Controller
ehci_platform ehci_platform.16781: new USB bus registered, assigned bus number 2
ehci_platform ehci_platform.16781: irq 12, io mem 0x00000000
ehci_platform ehci_platform.16781: park 0
ehci_platform ehci_platform.16781: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v2.2
usb 2-1: new high speed USB device using ehci_platform and address 2
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
qh_schedule: frame=255, uframe=0, cmask=0x0, smask=0x1, period=256, u_period=2048
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
mice: PS/2 mouse device common for all mice
[snip]
usb 2-1.3: new high speed USB device using ehci_platform and address 3
usb 2-1.3: USB disconnect, address 3
usb 2-1.3: new high speed USB device using ehci_platform and address 4
usb 2-1.3: USB disconnect, address 4
usb 2-1.3: new high speed USB device using ehci_platform and address 5
What next? My googling seems to suggest I should expect more output than
just the single "new high speed" lines. (As you can see I turned the
external drive on and off a couple of times). Any help gratefully
received!
Thanks,
Adam
--
Adam Richardson
Carpe Diem
1) see if the USB device is being accepted. Try
lsusb
and
cat /proc/bus/usb/devices
before and after attaching the USB device to see the changes
(that way you know to ignore the hubs and other USB devices).
2) On Fedora Linux, dmesg shows this for a USB flash drive
scsi 2:0:0:0: Direct-Access USB Flash Memory 1.04 PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: [sdb] 2007040 512-byte hardware sectors (1028 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg2 type 0
The drive is now /dev/sdb and /dev/sdb1.
"fdisk -l /dev/sdb" shows the partition table,
/dev/sdb1 is the partition with the file system that you mount.
If the drive is not set to auto-spinup
or spins itself down (such as Seagate Freeagent)
then Linux will be /very unhappy/.
In message <gn66gh$pfk$1...@panix5.panix.com>, Jeff Jonas wrote:
> Adam wrote:
> > I want to use an external USB drive to save the data on.
> > I've plugged the drive in, but can't work out how to get the system to recognise it.
> >dmesg gives: ...
> > usb 2-1.3: new high speed USB device using ehci_platform and address 3
> > usb 2-1.3: USB disconnect, address 3
> > usb 2-1.3: new high speed USB device using ehci_platform and address 4
> > usb 2-1.3: USB disconnect, address 4
> > usb 2-1.3: new high speed USB device using ehci_platform and address 5
>
> 1) see if the USB device is being accepted. Try
> lsusb
"command not found"
> and
> cat /proc/bus/usb/devices
> before and after attaching the USB device to see the changes
> (that way you know to ignore the hubs and other USB devices).
OK, that produces a new entry:
T: Bus=02 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 7 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=13fd ProdID=0540 Rev= 2.37
S: Manufacturer=Initio
S: Product=ST3802110A
S: SerialNumber=00101005400001AA0
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
How do I make use of this info?
> 2) On Fedora Linux, dmesg shows this for a USB flash drive
> scsi 2:0:0:0: Direct-Access USB Flash Memory 1.04 PQ: 0 ANSI: 0 CCS
> sd 2:0:0:0: [sdb] 2007040 512-byte hardware sectors (1028 MB)
> sd 2:0:0:0: [sdb] Write Protect is off
> sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
> sd 2:0:0:0: [sdb] Assuming drive cache: write through
> sdb: sdb1
> sd 2:0:0:0: [sdb] Attached SCSI removable disk
> sd 2:0:0:0: Attached scsi generic sg2 type 0
>
> The drive is now /dev/sdb and /dev/sdb1.
> "fdisk -l /dev/sdb" shows the partition table,
> /dev/sdb1 is the partition with the file system that you mount.
Unfortunately dmesg here doesn't reveal much of any use.
> If the drive is not set to auto-spinup
> or spins itself down (such as Seagate Freeagent)
> then Linux will be /very unhappy/.
This should be fine. I can hear the drive spin up when I turn it on and
I've never been able to get it to spin down when I've tried!
Thanks a lot for the help,
> T: Bus=02 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 7 Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=13fd ProdID=0540 Rev= 2.37
> S: Manufacturer=Initio
> S: Product=ST3802110A
> S: SerialNumber=00101005400001AA0
> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
> E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
>
>How do I make use of this info?
Let's see
1) Product=ST3802110A means the adapter is
properly passing back information that you have a
Seagate Barracuda 7200.9 ST3802110A 80GB Hard Drive
2) I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
The "Driver=none" means your USB system is not recognizing the adapter
so it's not being assigned to any driver.
Nothing's happening until that's fixed.
Perhaps there's a clue here:
http://ars.userfriendly.org/cartoons/read.cgi?id=20070106&tid=2326220
>Let's see
also try dmesg and see what is being printed there
also check /proc/scsi/scsi. The drive will get a letter based on
it's position in that list -- /dev/sdd would be the device for the fourth
entry, /dev/sdd1 would be the first partition.
Try 'fdisk -l /dev/sdd' (or whatever device it is) to get the list of
partitions,
Then mkdir a directory to mount it such as /mnt/removable, and
mount it with 'mount /dev/sdd1 /mnt/removable'
you may need '-t vfat' or '-t msdos' to indicate the file system type.
> On 14 Feb 2009 16:42:35 -0500, Jeff Jonas <je...@panix.com> wrote:
> >>> cat /proc/bus/usb/devices
>
> >> T: Bus=02 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 7 Spd=480 MxCh= 0
> >> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> >> P: Vendor=13fd ProdID=0540 Rev= 2.37
> >> S: Manufacturer=Initio
> >> S: Product=ST3802110A
> >> S: SerialNumber=00101005400001AA0
> >> C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
> >> I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
> >> E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
> >> E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
> >>
> >>How do I make use of this info?
>
> >Let's see
>
> >1) Product=ST3802110A means the adapter is
> >properly passing back information that you have a
> > Seagate Barracuda 7200.9 ST3802110A 80GB Hard Drive
>
> >2) I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
>
> >The "Driver=none" means your USB system is not recognizing the adapter
> >so it's not being assigned to any driver.
> >Nothing's happening until that's fixed.
>
> >Perhaps there's a clue here:
> >http://ars.userfriendly.org/cartoons/read.cgi?id=20070106&tid=2326220
If there is, I'm afraid it's missed me.
> also try dmesg and see what is being printed there
dmesg doesn't give much info (see my first post).
> also check /proc/scsi/scsi. The drive will get a letter based on
> it's position in that list -- /dev/sdd would be the device for the fourth
> entry, /dev/sdd1 would be the first partition.
>
> Try 'fdisk -l /dev/sdd' (or whatever device it is) to get the list of
> partitions,
Thanks, I've done all that but it doesn't show up anywhere.
/proc/scsi/scsi only shows the internal drive. I've played around with
"fdisk -l" and tried "fdisk -l xxx" for basically every entry in /dev to
try and find it with trial and error, but no joy. I guess that's not
surprising if, as Jeff says, the drive is not being recognized by the
USB system. I've no idea how to make that work though. :(
Thanks,
> [...]
> Thanks, I've done all that but it doesn't show up anywhere.
> /proc/scsi/scsi only shows the internal drive. I've played around with
> "fdisk -l" and tried "fdisk -l xxx" for basically every entry in /dev
> to try and find it with trial and error, but no joy. I guess that's
> not surprising if, as Jeff says, the drive is not being recognized by
> the USB system. I've no idea how to make that work though. :(
Do you have a matching usb_storage module? What does lsmod tell you?
The drive is detected by the USB sub system but to me it looks like the
appropriate module (usb_storage) isn't loaded.
b.r.,
Marc
> On Sun, 15 Feb 2009 10:54:14 GMT
> Adam <ne...@snowstone.org.uk> wrote:
>
> > [...]
> > Thanks, I've done all that but it doesn't show up anywhere.
> > /proc/scsi/scsi only shows the internal drive. I've played around with
> > "fdisk -l" and tried "fdisk -l xxx" for basically every entry in /dev
> > to try and find it with trial and error, but no joy. I guess that's
> > not surprising if, as Jeff says, the drive is not being recognized by
> > the USB system. I've no idea how to make that work though. :(
>
> Do you have a matching usb_storage module? What does lsmod tell you?
lsmod gives no output (and /proc/modules is empty).
> The drive is detected by the USB sub system but to me it looks like the
> appropriate module (usb_storage) isn't loaded.
Sounds sensible. After a bit of googling, I discovered a
"usb-storage.ko" file in /lib/modules. I then did an "insmod" on it and
my USB drive showed up with "fdisk -l" :D
I've now got it mounted happily and am in the process of backing up my
files as I type :)
Thanks a lot for the help,