Or, you could just tell Mr. Gates' monopoly to stick it and migrate to Linux.
That's a progress, however, sometimes it is simply necessary to unplug the hdd and use it on a windows machine, without the need to do anything just plug and play. That's why I prefer NTFS. Sometimes I get a feeling we are going backwards instead of forward in terms of usability. Actually, I just want it as it used to be / work.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Thu Aug 11, 2022 16:24 Post subject:
Perhaps you can then determine if repairing the filesystem suffices for your reported issue, you have been advised of it, if it does, you will need to find a way to run a repair script automatically on router boot.
Then there should be no problem.
If problem persists DD-WRT the only thing that it could do is perhaps handle this repair for you assuming the necessary module are available. Other than that these are all 3rd party developed components, and if any of those are determined to be at fault a bug report upstream is needed, however we have no such indication.
If its NTFS itself that cant handle power-failures or whatever its again not a DD-WRT issue, so idk what DD-WRT could do for you.
I provided links twice in this thread also a third time in a build thread. Wrong hdd capacity bug is ksmbd not dd-wrt.
Script is not programming. Without learning commands, or search, highly suggested to take advice of many others.
Use ext4, a native linux file system. Use a dedicated drive for the router. Do not unplug for other tasks usage or OS.
In Linux chkdsk command does not exist, Paragon has chkntfs not free, ntfsfix both are not replacement, equivalent.
Even if you do manage a script to fix NTFS partition(s) flagged as dirty then properly mount a ksmbd bug still exists.
Currently ksmbd is using ->f_bsize from vfs_statfs() as sector size.
If fat/exfat is a local share, ->f_bsize is a cluster size that is too
large to be used as a sector size. Sector sizes larger than 4K cause
problem occurs when mounting an iso file through windows client.
The error message can be obtained using Mount-DiskImage command,
the error is:
"Mount-DiskImage : The sector size of the physical disk on which the
virtual disk resides is not supported."
This patch reports fixed 4KB sector size if ->s_blocksize is bigger
than 4KB.
I just checked, my router RT-AC68U is running ntfs3 which does not include ntfsfix since that is part of ntfs-3g and if this is the case on yours, not even a chance to do any scripted solution to see if ntfs volume is clean/dirty and repair.
But I'll take that with a grain of salt since all the configs are probably not completely sync'd 100% and because of kernel version in use - which is actually which kernel? Linux 4.9? _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
@FireStorm@ to determine if the DD-WRT interface USB Disk Info reports wrong size, then we known its not ksmbd but ntfs-3g or ntfs3 depending on router. Then we will have a better idea where you need to report bug.
dd-wrt shows the right size, but I get two information
--- /dev/sda
Block device, size 4.548 TiB (5000981078016 bytes)
DOS/MBR partition map
Partition 1: 582.2 GiB (625121148928 bytes, 1220939744 sectors from 256)
Type 0x07 (NTFS/HPFS)
First 896 KiB are blank
/dev/sda not mounted Unsupported Filesystem
--- /dev/sda1
Block device, size 4.548 TiB (5000969191424 bytes)
Windows BOOTMGR boot loader
NTFS file system
UUID XXXXXXXXXXXXXXXXXXXXXXXX
Volume size 4.548 TiB (5000969187328 bytes, 1220939743 sectors of 4 KiB)
/dev/sda1 mounted to /jffs
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Mon Aug 15, 2022 15:01 Post subject:
You'd get that same information in a Linux desktop after plugging that drive in with the appropriate utilities as well as in the same Windows utilities as @egc stated. I guess we should petition the master wizard to not display the root physical drive partition information (sda) in the webUI? _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon Aug 15, 2022 18:01 Post subject:
OK tested, So The size thing is real, my 500GB Drive shows up as 1.81TB thank you very much ksmbd for making my drive bigger. This happens only when share is mapped to a drive, but tbh I never saw any value in mapping samba shares to a drive letter, Im quite happy with the Networking folders Windows side, and if anything needs mounting I do it directly on the target applications like VLC.
Anyway HDD size bug is real via kmsbd so bug needs to be reported upstream. (Im looking at the op)
As for share NOT showing up on Android, I guess this depends on Android, app or user?
On my android File manager it shows up just fine on auto detect, VLC side, not so much even though all my other shares show up fine, but this is a VLC bug and its a long standing bug (I'm a beta tester), the trick is to add your share manually, and VLC side its an interesting way to do it, you need to add any share as a favorite and edit that share with correct IP blablabla and voilla.
Laptop side Linux OS, no issues, share available and visible and works, Can't test on SmartTV cause my TV doent pretend to be smart, it knows its just a TV and is very happy being just a TV and doesn't want to be smart either, Ill assume those last parts, I dont have conversations with the TV .
Media Center side (KODI) running on my home grown custom rolled distro Linux based, Share appears just fine and is obviously working.
Only real issue is the HDD size when share is mapped to a letter, the rest, works and keeps working.
I dont particularly think the DD-WRT drive detection via ntfs3 is all that, but it works.
Attached is my basic test config.
Code:
~# mount
/dev/sda1 on /tmp/mnt/sda1 type ntfs3 (rw,noatime,nls=utf8,nodiratime)
There were some issues which I have corrected by fixing it directly connected to a Windows machine, but appears ntfs3 didn't like my umount /dev/sda1
Code:
dmesg| grep sda1
[ 44.776348] sda: sda1
[ 2847.648862] Buffer I/O error on dev sda1, logical block 786436, lost async page write
[ 2847.657006] Buffer I/O error on dev sda1, logical block 786441, lost async page write
[ 2847.665149] Buffer I/O error on dev sda1, logical block 786442, lost async page write
[ 2847.673292] Buffer I/O error on dev sda1, logical block 786443, lost async page write
[ 2847.681445] Buffer I/O error on dev sda1, logical block 786444, lost async page write
[ 2847.689693] Buffer I/O error on dev sda1, logical block 786445, lost async page write
[ 2847.697867] Buffer I/O error on dev sda1, logical block 786446, lost async page write
[ 2847.697886] Buffer I/O error on dev sda1, logical block 786447, lost async page write
[ 2847.697900] Buffer I/O error on dev sda1, logical block 786449, lost async page write
[ 2847.697913] Buffer I/O error on dev sda1, logical block 786450, lost async page write
[ 2924.431369] Buffer I/O error on dev sda1, logical block 19342, lost async page write
[ 2924.439161] Buffer I/O error on dev sda1, logical block 19624, lost async page write
[ 2924.446918] Buffer I/O error on dev sda1, logical block 19627, lost async page write
[ 2924.454754] Buffer I/O error on dev sda1, logical block 19628, lost async page write
[ 2924.462622] Buffer I/O error on dev sda1, logical block 20600, lost async page write
[ 2924.470697] Buffer I/O error on dev sda1, logical block 2, lost async page write
[ 2924.478364] VFS: Dirty inode writeback failed for block device sda1 (err=-5).
Things to investigate?!
Code:
~# dmesg| grep ksmbd
[ 1622.085093] Out of memory in ksmbd_auth_ntlmv2:476
[ 1623.272589] Out of memory in ksmbd_auth_ntlmv2:476
[ 2846.932092] ksmbd: kill command received
[ 2849.903648] ksmbd: Server reset is in progress, can't start daemon
[ 2850.631429] ksmbd: sock_read failed: -108
Syslog
Code:
Aug 15 20:15:14 Nexus local5.err ksmbd: [ksmbd-worker/5170]: ERROR: Recv() error Invalid input data or parameter [-7]
Aug 15 20:15:14 Nexus local5.err ksmbd: [ksmbd-manager/5169]: ERROR: WARNING: child process exited abnormally: 5170
Aug 15 20:15:14 Nexus local5.err ksmbd: [ksmbd-manager/5169]: ERROR: Fatal IPC error. Terminating. Check dmesg.
Aug 15 20:15:14 Nexus local5.err ksmbd: [ksmbd-manager/5169]: ERROR: can't execute kill 5170: No such process
Aug 15 20:15:14 Nexus local5.info ksmbd: [ksmbd-manager/5169]: INFO: Exiting. Bye!
Aug 15 19:32:38 Nexus local5.err ksmbd: [ksmbd-manager/2763]: ERROR: Can't open `/tmp/ksmbd.subauth': No such file or directory
Aug 15 19:32:38 Nexus local5.info ksmbd: [ksmbd-worker/2764]: INFO: User already exists
Aug 15 19:33:11 Nexus local5.err ksmbd: [ksmbd-worker/2764]: ERROR: Unsupported share info level (write): 2
Aug 15 19:33:11 Nexus local5.err ksmbd: [ksmbd-worker/2764]: ERROR: Unsupported share info level (read): 2