Opened 14 months ago
Closed 11 months ago
#2497 closed (duplicate)
ASUS RT-N66U is unable to read Ext2 and Ext3 filesystems
| Reported by: | GH0 | Owned by: | |
|---|---|---|---|
| Keywords: | N66U | Cc: |
Description
Build: DD-WRT v24-sp2 (04/07/12) mega (SVN revision 18946M NEWD-2 K2.6 Eko) & Big builds
I have two USB Drives (one a PNY 2GB Flash Drive, the other a Corsair 8 GB Voyager Drive). When partitioning to fit the Optware partition scheme shown here: http://dd-wrt.com/wiki/index.php/How_to_-_Format_and_Partition_External_Storage_Device
They fail to show up in the USB Services, and the output shows the following: --- /dev/discs/disc0/disc Status: Not mounted - Unsupported file system or disk not formated Status: Not mounted - Unsupported file system or disk not formated
Plugging the drives into my WRT350N & my linux server the drives work fine and are partitioned:
WRT350N - DD-WRT v24-sp2 (12/20/11) mega (SVN revision 18024)
--- /dev/discs/disc0/disc Block device, size 1.870 GiB (2008023040 bytes) DOS/MBR partition map Partition 1: 680 MiB (713031680 bytes, 1392640 sectors from 2048) Type 0x83 (Linux) Ext2 file system Volume name "Optware" UUID B3C4F9D6-C4E0-4CAC-A61B-C8CAB70EEAA9 (DCE, v4) Volume size 680 MiB (713031680 bytes, 174080 blocks of 4 KiB) Partition 2: 256 MiB (268435456 bytes, 524288 sectors from 1394688) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 256.0 MiB (268427264 bytes, 65534 pages of 4 KiB) Partition 3: 978 MiB (1025507328 bytes, 2002944 sectors from 1918976) Type 0x83 (Linux) Ext2 file system Volume name "Data" UUID 3A8C931D-2E04-4AD8-AEBC-28FE269C62F1 (DCE, v4) Volume size 978 MiB (1025507328 bytes, 250368 blocks of 4 KiB) Status: Mounted on /opt
Linux
Disk /dev/sdg: 8100 MB, 8100249600 bytes 255 heads, 63 sectors/track, 984 cylinders, total 15820800 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000334d9 Device Boot Start End Blocks Id System /dev/sdg1 63 4176899 2088418+ 83 Linux /dev/sdg2 4176900 7341704 1582402+ 82 Linux swap / Solaris /dev/sdg3 7341705 15807959 4233127+ 83 Linux
This seems to be a problem with the build as Fractal has mentioned that he can use NTFS perfectly fine.
Attachments (2)
Change History (8)
comment:1 Changed 14 months ago by BrainSlayer
comment:2 Changed 14 months ago by GH0
dmesg of Corsair Voyager Drive:
usb 1-1.1: USB disconnect, address 7 usb 1-1.2: new high speed USB device using ehci_hcd and address 8 usb 1-1.2: configuration #1 chosen from 1 choice scsi5 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 8 usb-storage: waiting for device to settle before scanning scsi 5:0:0:0: Direct-Access Corsair Voyager 1100 PQ: 0 ANSI: 0 CCS sd 5:0:0:0: [sda] 15820800 512-byte hardware sectors (8100 MB) sd 5:0:0:0: [sda] Write Protect is off sd 5:0:0:0: [sda] Mode Sense: 43 00 00 00 sd 5:0:0:0: [sda] Assuming drive cache: write through sd 5:0:0:0: [sda] 15820800 512-byte hardware sectors (8100 MB) sd 5:0:0:0: [sda] Write Protect is off sd 5:0:0:0: [sda] Mode Sense: 43 00 00 00 sd 5:0:0:0: [sda] Assuming drive cache: write through /dev/scsi/host5/bus0/target0/lun0: p1 p2 p3 sd 5:0:0:0: [sda] Attached SCSI removable disk usb-storage: device scan complete root@Dark-Knight:/tmp/var/log#
If you need any more specific log messages, let me know. To be clear this is using the Automatic Drive Mount functionality under the Services > USB menu.
comment:3 Changed 14 months ago by GH0
I have been trying over the past couple days to get the USB Drive mounted, and I have been unsuccessful.
The projected path:
root@Dark-Knight:/dev/scsi/host5/bus0/target0/lun0# ls -l brw------- 1 root root 8, 0 Jan 1 1970 disc brw------- 1 root root 8, 1 Jan 1 1970 part1 brw------- 1 root root 8, 2 Jan 1 1970 part2 brw------- 1 root root 8, 3 Jan 1 1970 part3 root@Dark-Knight:/dev/scsi/host5/bus0/target0/lun0#
comment:4 Changed 14 months ago by GH0
Another user having a problem: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=683273#683273
Brainslayer, or anyone else familiar with this process, what other information needs to be taken down (besides dmesg)?
comment:5 Changed 12 months ago by GH0
Brainslayer: http://pastebin.com/LsxNcJuu
Hope this helps as well.Output of cat /proc/*
comment:6 Changed 11 months ago by GH0
- Resolution set to duplicate
- Status changed from new to closed
Ticket http://svn.dd-wrt.com:8000/ticket/2580 contains more information and usefulness.

this is the output of your WRT350N which works. okay. but we need the output of your non working device since we need some error messages to track down the problem. so basicly. what shows dmesg etc. use the telnet console to give us some more informations