[RT-AC68U] usb mounting wierdness sda/sdb

[Juggler]

Hello!
firmware 3.0.0.4.374_371.
I have usb disk @ usb 2.0 port.
Tried to install download manager. Actually I don't need it, I just want easy optware install.
Sometimes disk mounted as /sda1, sometimes as /sdb1. This breaks optware install completely...

 

[RMerlin]

Hello!
firmware 3.0.0.4.374_371.
I have usb disk @ usb 2.0 port.
Tried to install download manager. Actually I don't need it, I just want easy optware install.
Sometimes disk mounted as /sda1, sometimes as /sdb1. This breaks optware install completely...

Give your disk a label, that way it will always be mounted using its label rather than its device name (which can change during enumeration if you have more than on disk plugged in).

With ext2/ext3/ext4, this can be done using:

tune2fs -L /dev/sda1

 

[Juggler]

Give your disk a label, that way it will always be mounted using its label rather than its device name (which can change during enumeration if you have more than on disk plugged in).

Thanks. I've googled it too. But in that case it works even more wierd.
Drive is really mounted at /tmp/mnt/label always!
But:
1) it is not shown in mount output
2) coz of 1) it can't be unmounted using umount /tmp/mnt/label
3) asus web gui doesn't "see" - "no usb disk" - so no ipkg install, no minidlna etc...

 

[RMerlin]

1) it is not shown in mount output
2) coz of 1) it can't be unmounted using umount /tmp/mnt/label
3) asus web gui doesn't "see" - "no usb disk" - so no ipkg install, no minidlna etc...

Sounds like your drive isn't properly mounted. Mounting by label works fine for me on both accounts.

admin@stargate4:/tmp/home/root# mount
<snip>
/dev/sda1 on /tmp/mnt/KT410 type ext4 (rw,nodev,relatime,user_xattr,barrier=1,data=ordered)

 

[Juggler]

Sounds like your drive isn't properly mounted. Mounting by label works fine for me on both accounts.

In your firmware or stock asus? Could it be important?
Have you tried mounting when plugging in running router or mounting after reboot?
I know your test router is AC56U, could AC68U be the problem?
Maybe something wrong with nvram settings, could reset to factory defaults cure the problem?

I am asking because AC68U is my only router for a moment and I can't experiment much myself...

 

[RMerlin]

In your firmware or stock asus? Could it be important?
Have you tried mounting when plugging in running router or mounting after reboot?
I know your test router is AC56U, could AC68U be the problem?

My main router is actually an RT-AC68U now for the past couple of weeks. It has no issue mounting that Kingston Traveler 410 by its label, like the AC56 (and the AC66 before that) always did.

Check your syslog for any additional info as to why the mounting failed.

The firmware you use shouldn't matter - that functionality is the same as in the original FW code.

 

[Juggler]

Sounds like your drive isn't properly mounted. Mounting by label works fine for me on both accounts.

admin@stargate4:/tmp/home/root# mount
<snip>
/dev/sda1 on /tmp/mnt/KT410 type ext4 (rw,nodev,relatime,user_xattr,barrier=1,data=ordered)

I will post syslog here if you don't mind.
BTW, please check - your drive mounts as EXT4. Is it supported? I have not found fsck.ext4 in the system, and it complains it can't find fsck.ext4 to check filesystem integrity after reboot!
One more thing. In most linux distros reboot always unmounts everything before actually turn off/reboot.
And I see this is not the case with asus routers. Is it a bug?

 

[Juggler]

admin@RT-AC68U:/jffs# blkid
/dev/sdb1: LABEL="mydrive" UUID="89cb4501-7a7e-4369-854e-b10480b01d77"
admin@RT-AC68U:/jffs# fsck.ext3 /dev/sdb1
e2fsck 1.38 (30-Jun-2005)
mydrive: clean, 5474/3662848 files, 289313/14650880 blocks
admin@RT-AC68U:/jffs#reboot

checked - looks ok.

admin@RT-AC68U:/tmp/mnt# cd /mnt
admin@RT-AC68U:/tmp/mnt# nvram show | grep mydrive
size: 40118 bytes (25418 left)
usb_path2_label1=mydrive
admin@RT-AC68U:/tmp/mnt# ls -la /tmp/opt
lrwxrwxrwx    1 admin    root            29 Jan  1  2011 /tmp/opt -> /tmp/mnt/mydrive/asusware.arm
admin@RT-AC68U:/tmp/mnt# mount
/dev/sdb1 on /tmp/mnt/mydrive(1) type ext4 (rw,nodev,relatime,barrier=1,data=ordered)
admin@RT-AC68U:/tmp/mnt#

WTF? Why (1)?

btw - auto mount after reboot - EXT4
umount->mount /dev/sdb1 /mnt -> EXT3 - which is correct.
Why is that?

now syslog (spaces are skipped line):
to me it look like power or driver issues. what do you think?

Jan  1 04:00:13 kernel: scsi 0:0:0:0: Direct-Access     IC25N060 ATMR04-0         0014 PQ: 0 ANSI: 0
Jan  1 04:00:13 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan  1 04:00:13 kernel: sd 0:0:0:0: [sda] 117210240 512-byte logical blocks: (60.0 GB/55.8 GiB)
Jan  1 04:00:13 kernel: sd 0:0:0:0: [sda] Write Protect is off
Jan  1 04:00:13 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jan  1 04:00:13 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jan  1 04:00:13 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jan  1 04:00:13 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jan  1 04:00:14 hotplug[529]: USB partition unmounted from /tmp/mnt/mydrive

Jan  1 04:00:20 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #2142113: comm [: reading directory lblock 0

Jan  1 04:00:21 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:21 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #2142113: comm sh: reading directory lblock 0
Jan  1 04:00:21 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:21 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #2142113: comm sh: reading directory lblock 0
Jan  1 04:00:21 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:21 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #2142113: comm sh: reading directory lblock 0

Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): __ext4_get_inode_loc:4908: inode #2142114: block 8585218: comm .asusrouter: unable to read itable block
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1) in ext4_reserve_inode_write:5747: IO failure
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #2: comm hotplug: reading directory lblock 0
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): ext4_read_inode_bitmap:156: comm hotplug: Cannot read inode bitmap - block_group = 0, inode_bitmap = 1026
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1) in ext4_new_inode:1052: IO failure
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #2: comm hotplug: reading directory lblock 0
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): ext4_read_inode_bitmap:156: comm hotplug: Cannot read inode bitmap - block_group = 0, inode_bitmap = 1026
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1) in ext4_new_inode:1052: IO failure
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #2: comm hotplug: reading directory lblock 0
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): ext4_read_inode_bitmap:156: comm hotplug: Cannot read inode bitmap - block_group = 0, inode_bitmap = 1026
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1) in ext4_new_inode:1052: IO failure
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): ext4_read_inode_bitmap:156: comm hotplug: Cannot read inode bitmap - block_group = 0, inode_bitmap = 1026
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1) in ext4_new_inode:1052: IO failure
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected

Jan  1 04:00:23 kernel: EXT4-fs error (device sda1): ext4_read_inode_bitmap:156: comm hotplug: Cannot read inode bitmap - block_group = 0, inode_bitmap = 1026
Jan  1 04:00:23 kernel: EXT4-fs error (device sda1) in ext4_new_inode:1052: IO failure
Jan  1 04:00:23 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:23 rc_service: hotplug 529:notify_rc restart_nasapps

Jan  1 04:00:24 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Jan  1 04:00:24 kernel: EXT4-fs error (device sda1): ext4_find_entry:921: inode #2142113: comm wanduck: reading directory lblock 0

Jan  1 04:00:26 kernel: scsi 1:0:0:0: Direct-Access     IC25N060 ATMR04-0         0014 PQ: 0 ANSI: 0
Jan  1 04:00:26 kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
Jan  1 04:00:26 kernel: sd 1:0:0:0: [sdb] 117210240 512-byte logical blocks: (60.0 GB/55.8 GiB)
Jan  1 04:00:26 kernel: sd 1:0:0:0: [sdb] Write Protect is off
Jan  1 04:00:26 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Jan  1 04:00:26 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Jan  1 04:00:26 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Jan  1 04:00:26 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk

Jan  1 04:00:28 kernel: end_request: I/O error, dev sda, sector 58200104
Jan  1 04:00:28 kernel: Aborting journal on device sda1-8.
Jan  1 04:00:28 kernel: JBD2: I/O error detected when updating journal superblock for sda1-8.

Dec  3 13:06:01 kernel: EXT4-fs (sda1): previous I/O error to superblock detected
Dec  3 13:06:01 hotplug[882]: USB partition unmounted from /tmp/mnt/mydrive

Dec  3 13:06:01 rc_service: hotplug 882:notify_rc restart_nasapps
Dec  3 13:06:01 kernel: EXT4-fs error (device sda1): ext4_put_super:720: Couldn't clean up the journal
Dec  3 13:06:01 kernel: EXT4-fs (sda1): Remounting filesystem read-only
Dec  3 13:06:01 kernel: EXT4-fs (sda1): previous I/O error to superblock detected