What's new

USB in R/O, how to track IP ?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

gen87u

Occasional Visitor
Hello,

on my newly RT-87U with Asuswrt-Merlin 380.62_1, I just sshed and I see the usb stick in R/O, so checking :

admin@RT-AC87U-EB60:/tmp/mnt/sda1# dmesg | grep sda1
EXT3-fs (sda1): using internal journal
EXT3-fs (sda1): recovery complete
EXT3-fs (sda1): mounted filesystem with ordered data mode
Buffer I/O error on device sda1, logical block 3
lost page write due to I/O error on sda1
EXT3-fs error (device sda1): ext3_find_entry:
Buffer I/O error on device sda1, logical block 10682368
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 10682369
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 10682370
lost page write due to I/O error on sda1
EXT3-fs error (device sda1): read_inode_bitmap: Cannot read inode bitmap - block_group = 194, inode_bitmap = 6356993
EXT3-fs (sda1): error in ext3_new_inode: IO failure
Aborting journal on device sda1.
EXT3-fs (sda1): error: ext3_journal_start_sb: Detected aborted journal
EXT3-fs (sda1): error: remounting filesystem read-only
EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
EXT3-fs error (device sda1): ext3_find_entry: reading directory #1589255 offset 0
admin@RT-AC87U-EB60:/tmp/mnt/sda1# fsck.ext3 /mnt/sda1
e2fsck 1.42.13 (17-May-2015)
fsck.ext3: Is a directory while trying to open /mnt/sda1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>

Which command should I use (64 Go USB stick, I had to use a notepad cooler or it stopped working du to the heat) ?

Also, I would like to track when IP goes up or down, what is the best solution to do this ?

Last question, how to shutdown properly ? There is no "shutdown" command, and "reboot -p" doesnt seem to work either.

Thanks for your help.
 
admin@RT-AC87U-EB60:/tmp/mnt/sda1# fsck.ext3 /mnt/sda1
Wrong. Use this instead.
Code:
cd /
umount /dev/sda1
fsck.ext3 /dev/sda1
reboot


Also, I would like to track when IP goes up or down, what is the best solution to do this ?
You can't.

Last question, how to shutdown properly ? There is no "shutdown" command, and "reboot -p" doesnt seem to work either.
Unmount the USB device and then disconnect the power.
 
Wrong. Use this instead.
Code:
cd /
umount /dev/sda1
fsck.ext3 /dev/sda1
reboot


You can't.

Unmount the USB device and then disconnect the power.

My bad, so umount within ssh didnt work. It worked with the webui.

But "fsck.ext3 /dev/sda1" give me a /dev/sda1 is in use, but lsof and fuser arent available to check the culprit. I switched off the RT87, and put the usb stick in a raspberry, but I get the same message with fsck ("The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem").

I will simply format it again.

You say to shutdown properly I have to umount the USB device and disconnect power, what about the /jffs partition if a write was delayed ?
 
You say to shutdown properly I have to umount the USB device and disconnect power, what about the /jffs partition if a write was delayed ?
The jffs filesystem is designed to work with flash memory on devices like routers. The logging mechanism provides adequate protection for such a device.

A router is not a PC, it is designed to be left on 24/7. It is not anticipated that it would be frequently powered on and off.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top