amtm amtm - the Asuswrt-Merlin Terminal Menu

[thelonelycoder]

No hope, had to clean &format jffs and re install whole stuff ¯\_(ツ)_/¯

You jad remnants of amtm from a previous install? If so, there would have been a simpler way.

 

[randomName]

Did a recent package update break the putty bufferbloat test?

putty bb test install

mkdir -p /jffs/addons/util
 /usr/sbin/curl -s "https://raw.githubusercontent.com/richb-hanover/OpenWrtScripts/master/betterspeedtest.sh" -o "/jffs/addons/util/betterspeedtest.sh"
 chmod +x /jffs/addons/util/betterspeedtest.sh
 opkg install coreutils-mktemp
 opkg install coreutils-seq
 opkg install netperf
 opkg install procps-ng-pgrep
 /jffs/addons/util/betterspeedtest.sh -t 60 -H netperf-west.bufferbloat.net -p 8.8.8.8

 

[ugandy]

Did a recent package update break the putty bufferbloat test?

putty bb test install

mkdir -p /jffs/addons/util
/usr/sbin/curl -s "https://raw.githubusercontent.com/richb-hanover/OpenWrtScripts/master/betterspeedtest.sh" -o "/jffs/addons/util/betterspeedtest.sh"
chmod +x /jffs/addons/util/betterspeedtest.sh
opkg install coreutils-mktemp
opkg install coreutils-seq
opkg install netperf
opkg install procps-ng-pgrep
/jffs/addons/util/betterspeedtest.sh -t 60 -H netperf-west.bufferbloat.net -p 8.8.8.8

looks like
netperf-west.bufferbloat.net
is down
netperf-eu works

 

[archiel]

looks like
netperf-west.bufferbloat.net
is down
netperf-eu works

As does netperf.bufferbloat.net.

 

[SMS786]

After checking amtm's disk check script logs, it seems like my ext4 usb drive somehow became write protected...

 Wed Sep 30 17:06:48 DST 2020 Probing 'ext4' on device /dev/sda1
Running disk check v2.9, with command 'e2fsck -p' on /dev/sda1
e2fsck: Read-only file system while trying to open /dev/sda1
Disk write-protected; use the -n option to do a read-only
check of the device.
Wed Sep 30 17:06:48 DST 2020 Disk check done on /dev/sda1

Any advice on how disable write protection on the usb stick? And more importantly, anyone have an ideas on how this may have happened?

 

[L&LD]

That's usually a sign of the USB drive gone bad. Time for a new USB drive.

 

[SMS786]

That's usually a sign of the USB drive gone bad. Time for a new USB drive.

Darn! Just checked my syslog...seems you're right..

Sep 30 17:06:47 kernel: scsi 1:0:0:0: Direct-Access     SanDisk  Ultra            2.01 PQ: 0 ANSI: 6
Sep 30 17:06:47 kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
Sep 30 17:06:47 kernel: sd 1:0:0:0: [sda] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB)
Sep 30 17:06:47 kernel: sd 1:0:0:0: [sda] Write Protect is on
Sep 30 17:06:47 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Sep 30 17:06:47 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Sep 30 17:06:47 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Sep 30 17:06:47 kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Sep 30 17:06:48 custom_script: Running /jffs/scripts/pre-mount (args: /dev/sda1 ext4)
Sep 30 17:06:48 amtm disk-check: Probing 'ext4' on device /dev/sda1
Sep 30 17:06:48 amtm disk-check: Running disk check v2.9, with command 'e2fsck -p' on /dev/sda1
Sep 30 17:06:48 amtm disk-check: Disk check done on /dev/sda1
Sep 30 17:06:48 kernel: EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
Sep 30 17:06:48 kernel: EXT4-fs (sda1): write access unavailable, cannot proceed
Sep 30 17:06:48 kernel: EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (244)
Sep 30 17:06:48 kernel: EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
Sep 30 17:06:48 kernel: EXT4-fs (sda1): write access unavailable, cannot proceed
Sep 30 17:06:48 kernel: EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (244)

 

[SMS786]

Just for good measure, I tried 'fd' on amtm to try to reformat the drive and got the following output:

_____________________________________________

Formatting sda SanDisk Ultra (16.0 GB) now!
_____________________________________________

Stopping file serving services and swap file

Unmounting device(s)

Zeroing disk sda SanDisk Ultra (16.0 GB)

dd: can't open '/dev/sda': Read-only file system

Creating partition(s) on sda SanDisk Ultra (16.0 GB)

'/dev/sda' is opened for read only

The number of cylinders for this disk is set to 15267.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.


The number of cylinders for this disk is set to 15267.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): First cylinder (1-15267, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-15267, default 15267): Using default value 15267

Command (m for help): fdisk: short write

Formatting disk as "ext4", enabling journalling

mke2fs 1.42.13 (17-May-2015)
/dev/sda1: Read-only file system while setting up superblock
Setting disk device label "ultra"

tune2fs: Read-only file system while trying to open /dev/sda1
Couldn't find valid filesystem superblock.
tune2fs 1.42.13 (17-May-2015)

_____________________________________________

Done formatting device

The log file can be viewed with fdl

Your router will now reboot for the changes
to take effect.

Press Enter to continue

Just leaving it here for reference, in case the same happens to folks in the future.

 

[thelonelycoder]

Just for good measure, I tried 'fd' on amtm to try to reformat the drive and got the following output:

_____________________________________________

Formatting sda SanDisk Ultra (16.0 GB) now!
_____________________________________________

Stopping file serving services and swap file

Unmounting device(s)

Zeroing disk sda SanDisk Ultra (16.0 GB)

dd: can't open '/dev/sda': Read-only file system

Creating partition(s) on sda SanDisk Ultra (16.0 GB)

'/dev/sda' is opened for read only

The number of cylinders for this disk is set to 15267.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.


The number of cylinders for this disk is set to 15267.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): First cylinder (1-15267, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-15267, default 15267): Using default value 15267

Command (m for help): fdisk: short write

Formatting disk as "ext4", enabling journalling

mke2fs 1.42.13 (17-May-2015)
/dev/sda1: Read-only file system while setting up superblock
Setting disk device label "ultra"

tune2fs: Read-only file system while trying to open /dev/sda1
Couldn't find valid filesystem superblock.
tune2fs 1.42.13 (17-May-2015)

_____________________________________________

Done formatting device

The log file can be viewed with fdl

Your router will now reboot for the changes
to take effect
Press Enter to continue

Just leaving it here for reference, in case the same happens to folks in the future.

Time for a new device, that's my advice. You could try to format it in a computer and try again with fd but there's the risk that it will fail again soon.

 

[ptys]

Time for a new device, that's my advice. You could try to format it in a computer and try again with fd but there's the risk that it will fail again soon.

is it "normal" that i killed 4 different flashdrives over two years?

 

[thelonelycoder]

is it "normal" that i killed 4 different flashdrives over two years?

No, that's not normal. I personally have never lost a USB stick in all these years. My first stick I bought more than 20 years ago still is in use, in one of my test routers. I did have file corruption on sticks that are plugged into my routers two or three times but thats it. For other reasons I use an older SSD on my main router though.

 

[thelonelycoder]

Please post questions, observances, suggestions and errors for amtm in a new separate thread that you create - and tag it with amtm. Thanks
Goodbye old thread, you served us well.