Let met summarize everything:
- I have a WRT610n, build 14929 mega (downloaded as big).
- I have a WD 3TB USB3 Hard drive.
The hard drive is partitioned as follows:
- DOS/MBR;
- part1: 256MB as ext3;
- part2: 256MB as Linux Swap;
- part3: 1.91TB at ext3;
- part4: 840.86GB at ext3.
On part1 Optware is installed.
The settings on the WRT610n are (Service->USB):
- Core USB Support as enabled;
- USB 1.1 Support as disabled;
- USB 2.0 Support as enabled;
- USB printer supprt as disabled;
- USB storage support as enabled;
- ext2 / ext3 file system support as enabled;
- FAT file system support as enabled;
- Automatic drive mount as enabled;
- Run-on-Mount script name as mount -o noatime -t ext3 /dev/scsi/host0/bus0/target0/lun0/part1 /opt
- Disk mount point as /opt
Disk info states:
Code:
--- /dev/discs/disc0/disc
Block device, size 746.5 GiB (801535688704 bytes)
DOS/MBR partition map
Partition 1: 32 MiB (33554432 bytes, 65536 sectors from 256)
Type 0x83 (Linux)
Partition 2: 32 MiB (33554432 bytes, 65536 sectors from 65792)
Type 0x82 (Linux swap / Solaris)
Partition 3: 244.1 GiB (262144000000 bytes, 512000000 sectors from 131328)
Type 0x83 (Linux)
Partition 4: 105.1 GiB (112858628096 bytes, 220427008 sectors from 512131328)
Type 0x83 (Linux)
Status: Not mounted - Unsupported file system or disk not formated
This does not mount the drive automatically.
Are there anymore settings which can have an effect on this misbehaviour
You do not need a mount script. Just specify mount partition under /opt and install OTRW. OTRW has a service (automount) which mounts the other partitions. FAT and USB 1.1 support are optional, so you may disable them. I thought that MBR allows only 2 TB in *total*. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
Joined: 10 Jul 2012 Posts: 28 Location: Sint Maarten, D.W.I
Posted: Sun Aug 19, 2012 0:56 Post subject:
slobodan wrote:
You do not need a mount script. Just specify mount partition under /opt and install OTRW. OTRW has a service (automount) which mounts the other partitions. FAT and USB 1.1 support are optional, so you may disable them. I thought that MBR allows only 2 TB in *total*.
Two questions and my excuse for the very late reply.
1. Without the mount script it does not mount either.
2. Can I choose another type than MBR which the router understands?
in my dealings on this issue with my Asus RT-N16 with R19519 Mega, i;ve pretty much accepted that DD-WRT won;t mount a drive unless it;s mbr-which seems to be limited to 2 tb. Anyone have different results?
i was able to format a 3 TB drive under linux as MBR but DD-WRT did not recognize it.
incidentally, i have 2 ext2 formatted drives on my router. the 1st one mounts under /OPT fine. the 2nd one needs to be mounted manually.
Another thing I haven;t gotten working is mounting a combo of 2 drives of EXT2 and EXT3 under Optware. in this scenerio, I get the error on the 2nd drive of unknown file system EXT3 even though the module for EXT3 looks like they are loaded.
Status: Not mounted - Unsupported file system or disk not formatted
does anyone have that working? I can see plenty of people seem to have formatted their drives with different partitions(EXT3 and SWAP).
revisited trying to get a greater than 2 TB drive mounted under DD-WRT. still getting the unsupported file system message. took a look at the kernel messages and found this entry.
sd 1:0:0:0: [sdb] Too big for this kernel. Use a kernel compiled with support for large block devices.
sd 1:0:0:0: [sdb] 0 512-byte hardware sectors (0 MB)
so is the answer that support for large hard drives needs to be added and compiled at the kernel level? I am using a k26 firmware on my Asus RT-N16.
Support for > 2GB disks is not possible in Linux kernel 2.6.24, it needs GUID partition support which was introduced in K3.3 _________________ Kernel panic: Aiee, killing interrupt handler!
Some Tomato builds are said to support GPT. I did not verify it. See http://tomato.groov.pl/?page_id=78 (under Release 100). _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
I have noticed that my 3tb FAT32 drive mounts up nicely while the same drive as ext3 fails miserably. Might want to try FAT32 if you want a big partition.
I have noticed that my 3tb FAT32 drive mounts up nicely while the same drive as ext3 fails miserably. Might want to try FAT32 if you want a big partition.
On the other hand, no file support for > 4Gb. I'm going to try NTFS.
I have noticed that my 3tb FAT32 drive mounts up nicely while the same drive as ext3 fails miserably. Might want to try FAT32 if you want a big partition.
On the other hand, no file support for > 4Gb. I'm going to try NTFS.
Spent way too many hours on this already. NTFS partition of around 3Tb only shows up as 2Gb, after updating the ntfs-3g modules. Older modules simply failed with no explanation. NTFS is also slower than dog-snot as some suggested.
I think with lack of big drive support in DD-WRT (GPT) I am going to have to just find a router that Tomato supports. A shame, since I've spent so many hours on this already.
Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Thu May 02, 2013 15:46 Post subject:
gpt support is comming. basicly its supported already. just automount wasnt yet able to detect it. i have a 4 TB HDD running right now in test. i also need to rework some toolchains likelly. there is a gcc compiler bug which might cause troubles with bigger drives. this is a kernel related problem. expect full gpt support within the next days _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
BusyBox v1.21.0 (2013-04-28 13:32:41 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
root@DD-WRT:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 17664 17664 0 100% /
/dev/root 17664 17664 0 100% /
/dev/mtdblock/4 98304 9804 88500 10% /jffs
/dev/sda2 3906885628 8732552 3898153076 0% /tmp/mnt/sda_2
root@DD-WRT:~# _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Wed May 08, 2013 13:15 Post subject:
for broadcom devices i need to patch the kernel first since there is no efi support yet in it. but i'm currently also working on migrating the broadcom k26 builds to newer kernels. its already working, but not finished _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s