Hello, i have hdd with 1 partition and with fat32, when i connect hdd and run telnet, login and run command DF i don't see my hdd in dev/disc etc. Do you know what is the problem? THX
Printable View
Hello, i have hdd with 1 partition and with fat32, when i connect hdd and run telnet, login and run command DF i don't see my hdd in dev/disc etc. Do you know what is the problem? THX
Assuming it's a USB disk what does dmesg tell you after it's been plugged in?
Excuse me for excavating this old thread but I've got the same problem. Just have set up newest Oleg following Wengi's tutorial so that my disc0 is a 4GB Kingston flash-drive - this config is working perfectly. What I'd like to do now is to attach a second drive, 1TB 3,5" Trekstor HDD with one FAT32 formatted partition on it. However after booting WL500GPV2 with both drives connected only /dev/discs/disc0 is there, no disc1 or anything like this so that the Trekstor is not visible/mountable. lsusb shows "new" device, so does dmesg:
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Setting latency timer of device 00:03.0 to 64
usb-ohci.c: USB OHCI at membase 0xb8003000, IRQ 6
usb-ohci.c: usb-00:03.0, PCI device 14e4:471a
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:03.1 to 64
ehci_hcd 00:03.1: PCI device 14e4:471a
ehci_hcd 00:03.1: irq 6, pci mem b8003800
usb.c: new USB bus registered, assigned bus number 2
ehci_hcd 00:03.1: USB 0.0 enabled, EHCI 1.00, driver 10 Dec 2004/2.4
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver usblp
printer.c: v0.13: USB Printer Device Class driver
Linux video capture interface: v1.00
SCSI subsystem driver Revision: 1.00
hub.c: new USB device 00:03.1-1, assigned address 2
hub.c: USB hub found
hub.c: 2 ports detected
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
vlan1: Setting MAC address to 00 0c 6e 20 74 e3.
vlan1: add 33:33:00:00:00:01 mcast address to master interface
vlan1: add 33:33:ff:20:74:e3 mcast address to master interface
hub.c: new USB device 00:03.1-1.1, assigned address 3
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Kingston Model: DataTraveler 2.0 Rev: PMAP
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
sda: Waiting for disc 0 to settle.
SCSI device sda: 7936000 512-byte hdwr sectors (4063 MB)
sda: Write Protect is off
Partition check:
/dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3. Host: 0
hub.c: new USB device 00:03.1-1.2, assigned address 4
scsi1 : SCSI emulation for USB Mass Storage devices
vlan0: no IPv6 routers present
eth0: no IPv6 routers present
eth1: no IPv6 routers present
br0: no IPv6 routers present
vlan1: no IPv6 routers present
Adding Swap: 506008k swap-space (priority -1)
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,3), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
scsi: device set offline - not ready or command retry failed after bus reset: host 1 channel 0 id 0 lun 0
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4. Host: 1
I can see the error message in the 4 line from the end of the log - could you please suggest me what I could do?
It seems like it may either have been not cleanly unmounted previously, or you may have better luck with an ext2/ext3 filesystem.
Thanks for help! My problem was actually easy to resolve - Trekstor's electronics makes it spin down once it's disconnected from usb (even though it still is connected to wall outlet) and somehow the drive didn't spin up hooked up to the router. After a reset and reconnecting the usb cable the hdd woke up so now it's up and running.