Could of course also be due to flash wear out - who knows
My understanding was that jffs partition may be used to store some temporary files like log files, or data (metadata) from minidlna (i use minidlna service). May be i'm wrong
Well, the file system should not be damaged by a reboot.
If you reboot devices properly, processes are terminated and file systems are unmounted.
But if you simply disconnect the power while data is being written, this can cause errors.
And ext2 has no journal, if you use the filesystem as a drive on which you write regularly, you will always have problems with it - caused by power failures or your own flipping of the switch.
But usually not so much is written in the log.
It is also possible that your USB stick is worn out and slowly dying.
Or in the last dd-wrt builds something was defective.
I have no idea, I haven't read anything about USB problems and I don't use a USB stick at the moment.
Well, the file system should not be damaged by a reboot.
If you reboot devices properly, processes are terminated and file systems are unmounted.
But if you simply disconnect the power while data is being written, this can cause errors.
And ext2 has no journal, if you use the filesystem as a drive on which you write regularly, you will always have problems with it - caused by power failures or your own flipping of the switch.
But usually not so much is written in the log.
It is also possible that your USB stick is worn out and slowly dying.
Or in the last dd-wrt builds something was defective.
I have no idea, I haven't read anything about USB problems and I don't use a USB stick at the moment.
Thanks ho1Aetoo,
May be the guide that i followed (https://forum.dd-wrt.com/phpBB2/download.php?id=50452) is outdated, it recommends ext2 for flash usb and ext4 for hard drives (don't know why):
The usb stick i use is from a good brand and less than 2 years old. Also, scan on Mac/PC don't detect any error. May be i should just try ext 4.
I'd have prefered formating disks directly from the router, may be i could install e2fsprogs on "opt" ?
Joined: 16 Nov 2015 Posts: 6437 Location: UK, London, just across the river..
Posted: Mon Jan 30, 2023 23:13 Post subject:
hmmm i thought in ddwrt on thumb drives journaling fs is disabled by default ..in this case this is ext3 but as usual recognised as ext4, as this is the only lsmod all ext2, 3 are ext4
I converted flash drive (opt, jffs) to ext 4, also installed entware then e2fsprogs and tune2fs packages. When executing tune2fs -l /dev/sda1 command, i have : Filesystem state: clean:
Quote:
root@DD-WRT:/opt# tune2fs -l /dev/sda1
tune2fs 1.46.5 (30-Dec-2021)
Filesystem volume name: Backup
Last mounted on: /tmp/mnt/sda1
Filesystem UUID: f0be6719-ece1-d601-60b0-6619ece1d601
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr filetype needs_recovery extent flex_bg sparse_super large_file huge_file extra_isize
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 268435456
Block count: 268435200
Reserved block count: 13421760
Free blocks: 31905576
Free inodes: 268435442
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 32768
Inode blocks per group: 2048
Last mount time: Thu Jan 1 01:00:42 1970
Last write time: Thu Jan 1 01:00:42 1970
Mount count: 597
Maximum mount count: 20
Last checked: Sun Jan 3 18:18:40 2021
Check interval: 15552000 (6 months)
Next check after: Fri Jul 2 18:18:40 2021
Lifetime writes: 1307 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Journal inode: 8
Same when executing tune2fs -l /dev/sda2:
Code:
root@DD-WRT:/opt# tune2fs -l /dev/sda2
tune2fs 1.46.5 (30-Dec-2021)
Filesystem volume name: <none>
Last mounted on: /tmp/mnt/sda2
Filesystem UUID: f5ffff65-f0e1-d601-b0f7-e765f0e1d601
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr filetype needs_recovery extent flex_bg sparse_super large_file huge_file extra_isize
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 708345856
Block count: 708318976
Reserved block count: 35415948
Free blocks: 590956814
Free inodes: 708331637
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 32768
Inode blocks per group: 2048
Last mount time: Thu Jan 1 01:00:43 1970
Last write time: Thu Jan 1 01:00:43 1970
Mount count: 597
Maximum mount count: 20
Last checked: Sun Jan 3 18:49:27 2021
Check interval: 15552000 (6 months)
Next check after: Fri Jul 2 18:49:27 2021
Lifetime writes: 181 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Journal inode: 8
However, i'm a bit lost and confused by message when executing e2fsck /mnt/sda2 (or sda1, same message, even whith command e2fsck -f -C 0 /mnt/sda2, same result:
Quote:
root@DD-WRT:~# e2fsck -b 32768 /mnt/sda2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Is a directory while trying to open /mnt/sda2
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>
What is this superblock thing ? knowing that the files are accessible on the drive that seems to work properly ? The suggested commands e2fsck -b 8193 and e2fsck -b 32768 didn't help
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Jan 31, 2023 22:10 Post subject:
Okay. Not sure what the significance of 0 is in his example, and wondering if he meant -c and not -C. The -b 32768 should be valid, but you can try without that and use -B 4096, since that is the reported block size.
EDIT: I didn't read the man page completely.
Quote:
If the file descriptor specified is 0, e2fsck will print a completion bar as it goes about its business. This requires that e2fsck is running on a video console or terminal.
Joined: 16 Nov 2015 Posts: 6437 Location: UK, London, just across the river..
Posted: Tue Jan 31, 2023 23:05 Post subject:
as your installations are on entware/usb-drive there is no way to unmount it and than use those app's inn it..
Best bet scan those on proper linux installation..no idea how to make it with sucking Win..but there some progs like partition magic and ect. that can scan repair linux partitions...similar like...
and you can run a scan with -c too... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
as your installations are on entware/usb-drive there is no way to unmount it and than use those app's inn it..
Best bet scan those on proper linux installation..no idea how to make it with sucking Win..but there some progs like partition magic and ect. that can scan repair linux partitions...similar like...
and you can run a scan with -c too...
After formatting flash drive with opt and jffs (sdb1, sdb2) (ext 4), there is no more issues at this stage on dmesg but running e2fsck is still recommended for the separate hard drive (sda 1, sda2), that's why i unmounted it and ran the scan. I'll try to run it with -c, thanks