OP here with an update... I managed to kill yet ANOTHER usb drive...
I flashed my AX88U to 386_1.2 last night. Everything went smoothly, and WebGUI prompted me to reboot manually which I did (hard power cycle) --- but stupidly without safely removing/unmounting my EXT4 USB (swap, diversion, entware). The router restarted, but Diversion disappeared so I checked the disk check log and saw a "read-only" e2fsck error. Then I remembered that I've managed to kill 3-4 flash drives this way (manual router reboot or pulling them directly without first unmounting). After the first few losses, I even bought a Patriot Rage recommended by other users thinking my problem was due to low-quality drives. But now I'm convinced that a manual reboot while the drive is in use will cause it to go into write-protect mode. I've had this experience with several drives of various sizes from multiple manufacturers.
I'm assuming the drive went into write-protect mode because it was in use (swap file?) when it was removed/restarted. I don't have any reason to think the drive physically failed...but it's stuck in "read only" mode so I can't reformat it or mount it to backup my files. USB shows up as unmounted in the GUI.
Code:
admin@RT-AX88U-9770:/tmp/home/root# e2fsck -v /dev/sda
e2fsck 1.45.6 (20-Mar-2020)
e2fsck: Read-only file system while trying to open /dev/sda
Disk write-protected; use the -n option to do a read-only
check of the device.
e2fsck -n check says it's good
Code:
admin@RT-AX88U-9770:/tmp/home/root# e2fsck -n /dev/sda1
e2fsck 1.45.6 (20-Mar-2020)
Warning: skipping journal recovery because doing a read-only filesystem check.
rtrusb: clean, 1557/1896832 files, 735522/7575548 blocks
fdisk-l output:
Code:
admin@RT-AX88U-9770:/tmp/home/root# fdisk -l
Disk /dev/sda: 31.0 GB, 31029460992 bytes
64 heads, 32 sectors/track, 29592 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 29592 30302192 83 Linux
DiskPart (windows):
Code:
DISKPART> detail disk
Patriot Memory USB Device
Disk ID: 00000000
Type : USB
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : Yes
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
There are no volumes.
Code:
DISKPART> list partition
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 28 GB 16 KB
Code:
DISKPART> detail partition
Partition 1
Type : 83
Hidden: Yes
Active: No
Offset in Bytes: 16384
There is no volume associated with this partition.
So the partition and file system are still intact? But the device is 'dead' because it went into write-protect? Have others had this same issue? Is there a way to reset the drive or can I force a -rw mount to recover my files?
Thoughts on how to prevent this in the future? I've burned through ~4 drives less than a year (not to mention the pain of reinstalling/reconfiguring scripts).
