search

jhtwu / vigor2130

Automatically exported from code.google.com/p/vigor2130
0 stars 0 forks source link

320GB USB HDD won't mount properly #36

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Connect usb hdd
2. it will show up like the attachment in the webinterface

What is the expected output? What do you see instead?
root@Vigor2130:~# tail -f /var/log/messages
Jul 14 05:16:44 Vigor2130 syslog.info syslogd started: BusyBox v1.11.2
Jul 14 05:17:03 Vigor2130 user.info syslog: [draytek_hsdpa] Try to wake up 
modem ...
Jul 14 05:17:03 Vigor2130 local4.notice hotplug.3gusb: *****Try to wake up USB 
device 13fd/1840/0, will use interface /dev/ttyUSB0 later
Jul 14 05:17:05 Vigor2130 local4.notice hotplug.3gusb: skip 3G hotplug 
PRODUCT=13fd/1840/108 INTERFACE=8/6/80
Jul 14 05:17:05 Vigor2130 user.notice usb-storage: 1-1.3.1:1.0: usb device is 
mass storage
Jul 14 05:17:05 Vigor2130 user.notice usb-storage: waiting on usb drive 
1-1.3.1:1.0: 1 ...
Jul 14 05:17:07 Vigor2130 user.notice usb-storage: Have some block devices: 
/sys/devices/platform/grocx-ehci/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/host2/target
2:0:0/2:0:0:0/block:sdb
Jul 14 05:17:07 Vigor2130 user.notice usb-storage: Investigate 
/sys/devices/platform/grocx-ehci/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/host2/target
2:0:0/2:0:0:0/block:sdb
Jul 14 05:17:09 Vigor2130 user.notice usb-storage: 1-1.3.1:1.0 - mounting 
/dev/sdb on /mnt/usb_sdb ID c
Jul 14 05:17:10 Vigor2130 user.notice usb-storage: Mount Fail!!!
Jul 14 05:17:10 Vigor2130 user.notice usb-storage: the size of /mnt/usb_sdb = 
312571224
Jul 14 05:17:10 Vigor2130 user.notice usb-storage: 312571224 is greater than 
100MB!
Jul 14 05:17:10 Vigor2130 user.notice usb-storage: recover process!!!

What version of the product are you using? On what operating system?
v2130_r2273P.7z

Please provide any additional information below.
I formatted the harddrive via the router and everything seems in order. Here is 
the log of that.

root@Vigor2130:~# mkfs.ext3 /dev/sdb
mke2fs 1.40.11 (17-June-2008)
/dev/sdb is entire device, not just one partition!
Proceed anyway? (y,n) y
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
19537920 inodes, 78142806 blocks
3907140 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
2385 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

Original issue reported on code.google.com by TheEvilO...@googlemail.com on 14 Jul 2011 at 3:32

GoogleCodeExporter commented 9 years ago 
I forgot the attachment.
Also the HDD is the only device connected on a 7-port usbhub, which can supply 
2500 mA, so power shouldn't be an issue.

Original comment by TheEvilO...@googlemail.com on 14 Jul 2011 at 3:41

Attachments:

GoogleCodeExporter commented 9 years ago 
From the log:

Jul 14 05:17:09 Vigor2130 user.notice usb-storage: 1-1.3.1:1.0 - mounting 
/dev/sdb on /mnt/usb_sdb ID c
Jul 14 05:17:10 Vigor2130 user.notice usb-storage: Mount Fail!!!

You can try to mount the disk manual and check the error message.

Original comment by jht...@gmail.com on 14 Jul 2011 at 4:33

GoogleCodeExporter commented 9 years ago 
For some reason the manual mount works without a problem.

Original comment by TheEvilO...@googlemail.com on 14 Jul 2011 at 3:26