Status of IDE support in WL 500 Gx firmware?

[hugo]

should I expect fdisk to work? Even if it looks like it works, I don't get any change done:

here is a sample:

[admin@(none) /bin]$ fdisk /dev/hda

Command (m for help): p

Disk /dev/hda: 5403 MB, 5403525120 bytes
240 heads, 63 sectors/track, 698 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1               1         698     5276848+  83  Linux

Command (m for help): d 1
Selected partition 1

Command (m for help): p

Disk /dev/hda: 5403 MB, 5403525120 bytes
240 heads, 63 sectors/track, 698 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes

   Device Boot    Start       End    Blocks   Id  System

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.
[admin@(none) /bin]$ fdisk /dev/hda

Command (m for help): p

Disk /dev/hda: 5403 MB, 5403525120 bytes
240 heads, 63 sectors/track, 698 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1               1         698     5276848+  83  Linux

Command (m for help):

Is it a normal behaviour, or does this mean there is still not full access to IDE?

[hugo]

It's just a waste of the flash space. I think ASUS will switch to ext3.


Should work out of the box. Probably settings problem.

I was thinking about asus users that don't have access to their HD without the wl-hdd. This ones will have to use dedicated format tools or to have ext2 support as this is the only type you can get using the web interface or the telnet access. As you planned to add tools to format in ext3, this should be solved by the next version.


As for the wireless, going to router mode then back to AP mode make it works. There should be a parameter that is not set by default

[Oleg]

no, either busybox was not correctly rebuild or fdisk is buggy.
Try wl500g.dyndns.org/WLHDD-1.8.1.7-3-pre15.trx - I've recompiled busybox and added mke2fs and e2fsck.
To create ext3 fs just type

mke2fs -j /dev/ide/...

[hugo]

faliing at journal creation:

[admin@wl-hdd /]$ mke2fs -j /dev/ide/host0/bus0/target0/lun0/part1
mke2fs 1.35 (28-Feb-2004)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
ide/host0/bus0/target0/lun0/part1 is mounted.
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
659936 inodes, 1319212 blocks
65960 blocks (5.00%) reserved for the super user
First data block=0
41 block groups
32768 blocks per group, 32768 fragments per group
16096 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Writing inode tables: done
Creating journal (8192 blocks): mke2fs: No such file or directory
        while trying to create journal
[admin@wl-hdd /]$ mount /dev/ide/host0/bus0/target0/lun0/part1 /tmp/harddisk
mount: Mounting /dev/ide/host0/bus0/target0/lun0/part1 on /tmp/harddisk failed:
Invalid argument
[admin@wl-hdd /]$

Works without journaling. I still have to find the proper mount command

[Oleg]

Try creating with journal size of zero, I will check for this error.

[hugo]

Got it. Had to create 2 partitions, create a journal using the -O journal_dev paramter, then make the fs using the -J device=/dev/hda2

Mount is ok. I can start working now

[Oleg]

Uploaded pre16 - please check it, should work with -j

[hugo]

working ok. We just need to automont HD now. I've been testing copy and file operations, and it is behaving correctly. Wireless is ok too. Samba is awfully buggy and slow and there is no way to access the HDD out of the box. But it's just a question of time now

EDIT: This comment is for pre15, as I could finaly get my fs created.

I'm trying the pre16 right now

[hugo]

pre16 can format using the -j option as planned

[Oleg]

Well, for now mount your disk in the post-boot script, this is really easy.

As for samba - you need create correct config files for using it. Also, you should set LAN hostname for samba to work. And yes, samba is now uses users/passwords.

Mine files are as following:

[root@wl500g etc]$ cat /etc/passwd
root:$1$$LMuXuAPfSStW8rhnojbc41:0:0:root:/usr/local/root:/bin/sh
nobody:x:99:99:nobody:/:/sbin/nologin
oleg:x:100:100:oleg:/tmp/harddisk:/sbin/nologin
nk:x:100:100:nk:/tmp/harddisk:/sbin/nologin
 
[root@wl500g etc]$ cat /etc/smbpasswd
# Samba SMB password file
root:0:6F9F65B23B4B48E7613E8293942509F0:7741DF71C748ABCC71C6C263B99C2B08:root:/usr/local/root:/bin/sh
oleg:100:9EE3D0611811EA5C417EAF50CEAC29C3:F3AC46A6CB04CB32FE1C77A025CF6C53:oleg:/tmp/harddisk:/sbin/nologin
nk:100:8A5D3EB54FF11B0DB79AE2610DF89D4C:9FDB1AFF3084809671715D8AE948AA35:nk:/tmp/harddisk:/sbin/nologin
[root@wl500g etc]$ cat /etc/smbusers
root = administrator
[root@wl500g etc]$ cat /etc/smb.conf
[global]
        workgroup = WORKGROUP
        guest account = nobody
        security = user
        encrypt passwords = yes
        log level = 1
        max log size = 100
        username map = /etc/smbusers
        client code page = 866
        character set = 1251
[share]
        path = /tmp/harddisk
        writable = yes
[root$]
        path = /
        writable = yes
[root@wl500g etc]$

[Antiloop]

As for the wireless, going to router mode then back to AP mode make it works. There should be a parameter that is not set by default

wireless works here after restoring defaults via the button out of box..

[Antiloop]

ehmz..

well mounting goes out of box..?
at this moment i'm too lazy to get out of my bed to unplug the usbstick that i've sticked in.. maybe the usb stick is causing the auto-mount of both devices:

[admin@WLHDD root]$ mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
proc on /proc type proc (rw)
ramfs on /tmp type ramfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/discs/disc0/part1 on /tmp/harddisk type ext3 (rw,noatime)
/dev/discs/disc1/part1 on /tmp/harddisk/part1 type vfat (rw,sync)

i've found an error, when using DHCP (as client thus in AP mode) /etc/hosts uses 192.168.1.1 as ip_address and thus NMBD thinks it's that IP..
when setting it static, it works around the problem

at this moment i can't write when using samba.. have to look further..
i will also try ftp..

[Antiloop]

writing speed sux..
Transfer queue completed
Transferred 1 file totaling 1,66 MB in 20,94 (83,83 KBps)

downloading went fast.. (700kb/sec) so i'm uploading 15mb now to measure it a bit more effectivily

ps.. currently i'm doing everything wireless (using wireless from wl-hdd)

[Antiloop]

150 Opening BINARY mode data connection for 'test' (52342784 bytes).
226 Transfer complete.
Transferred: test 49,92 MB in 38,99 (1.311,17 KBps)
Transfer queue completed
Transferred 1 file totaling 49,92 MB in 40,59 (1.311,17 KBps)

... :S

tested with wire..

[hugo]

ehmz..

well mounting goes out of box..?
at this moment i'm too lazy to get out of my bed to unplug the usbstick that i've sticked in.. maybe the usb stick is causing the auto-mount of both devices:

That's it: Automount only work with an USB stick inserted. Otherwise, you have to mount manually

I've added the correct parameters in post boot to sort this out