Page 1 of 2

PorteuX 2.1 bug reports

Posted: 04 Jun 2025, 04:24
by Ed_P
Unable to update text files on NFTS drives.

PorteuX 2.1 has been released

Posted: 04 Jun 2025, 07:51
by porteux
We need a better explanation on how exactly to replicate the issue, expected behavior, current behavior, etc.

PorteuX 2.1 has been released

Posted: 04 Jun 2025, 08:45
by rych
Ed_P wrote:
04 Jun 2025, 04:24
Unable to update text files on NFTS drives.
...because they are read-only :) The whole NTFS partition was dirty and therefore mounted read-only. At least that's what used to happen to me 10 years ago :)

PorteuX 2.1 has been released

Posted: 04 Jun 2025, 18:15
by Ed_P
Boot porteuX 2.1, attempt to update grub2 menu, can't save the update, drive read only, reboot to porteus 5.01, update the grub2 menu, save it.

Could save these images to the EFI drive for posting later.

Image

Image
rych wrote:
04 Jun 2025, 08:45
...because they are read-only The whole NTFS partition was dirty and therefore mounted read-only.
chkdsk /f clears those problems on Windows.

PorteuX 2.1 has been released

Posted: 04 Jun 2025, 18:39
by porteux
NTFS partitions shouldn't be read-only. Please, add the following cheatcodes at the boot menu once:

Code: Select all

delay=5 fsck
This should fix any error in the NTFS partitions and make them writable.

PorteuX 2.1 has been released

Posted: 04 Jun 2025, 18:53
by Ed_P
porteux wrote:
04 Jun 2025, 18:39

Code: Select all

delay=5 fsck
This should fix any error in the NTFS partitions and make them writable.
Thanks. Never have had to do this with porteux before, or porteus, even after rebooting to it. Will try it later and get back to you.

Added in 1 hour 22 minutes 13 seconds:
I haven't tried the fsck code yet but this is the same drive, porteus 5.1 view.

Image

Similar views for the nvme0n1p5 drive on both systems.

Does the fsck code work for all drives or just the boot drive, which for me is an ISO.

PorteuX 2.1 has been released

Posted: 04 Jun 2025, 22:00
by porteux
Ed_P wrote:
04 Jun 2025, 20:16
Does the fsck code work for all drives or just the boot drive, which for me is an ISO.
It should check all available disks, and after the boot process finishes, a log file will be shown so you can check which drivers were scanned.

PorteuX 2.1 has been released

Posted: 04 Jun 2025, 23:36
by Ed_P

Code: Select all

root@porteux:/home/guest# fsck --help

Usage:
 fsck [options] -- [fs-options] [<filesystem> ...]

Check and repair a Linux filesystem.

Options:
 -A         check all filesystems
 -C [<fd>]  display progress bar; file descriptor is for GUIs
 -l         lock the device to guarantee exclusive access
 -M         do not check mounted filesystems
 -N         do not execute, just show what would be done
 -P         check filesystems in parallel, including root
 -R         skip root filesystem; useful only with '-A'
 -r [<fd>]  report statistics for each device checked;
            file descriptor is for GUIs
 -s         serialize the checking operations
 -T         do not show the title on startup
 -t <type>  specify filesystem types to be checked;
            <type> is allowed to be a comma-separated list
 -V         explain what is being done

 -?, --help     display this help
     --version  display version

See the specific fsck.* commands for available fs-options.
For more details see fsck(8).
root@porteux:/home/guest# 

Code: Select all

root@porteux:/home/guest# fsck -A
fsck from util-linux 2.41
root@porteux:/home/guest#
:hmmm:

PorteuX 2.1 has been released

Posted: 05 Jun 2025, 00:30
by porteux
Ed_P wrote:
04 Jun 2025, 23:36

Code: Select all

root@porteux:/home/guest# fsck --help
That's not what I told you to do. Read it again. :)

PorteuX 2.1 has been released

Posted: 05 Jun 2025, 02:53
by Ed_P
porteux wrote:
05 Jun 2025, 00:30
That's not what I told you to do.
True. This is:

Code: Select all

Partition /dev/nvme0n1p6 scan result:
Checking Volume /dev/nvme0n1p6...
Type of the filesystem is NTFS.
Volume label is: Recovery.
Verifying 256 records...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%Verifying 19 folders...
5%10%15%21%26%31%36%42%47%52%57%63%68%73%78%84%89%94%100%Verifying files security...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%$UpCase file is formatted for use in Windows 7 and later versions.
Resizing $LogFile.
Checking volume bitmap (32 kBytes)
Used clusters 0x15595 - 0x158cc marked as free.
Correcting $Bitmap data attribute.
   1048572 KB total disk space.
    713940 KB in 13 files.
        84 KB in 21 directories.
      5680 KB in use by the system.
         8 MB occupied by the log/journal file.
         4 KB in each allocation unit.
    262143 total allocation units on volume (0.99 GB).
     81414 allocation units available on volume (0.31 GB).
The volume /dev/nvme0n1p6 has been repaired successfully.

----------
Partition /dev/nvme0n1p5 scan result:
Checking Volume /dev/nvme0n1p5...
Type of the filesystem is NTFS.
Volume label is: Bkups.
Verifying 3840 records...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%Verifying 32 folders...
3%6%9%12%15%18%21%25%28%31%34%37%40%43%46%50%53%56%59%62%65%68%71%75%78%81%84%87%90%93%96%100%Verifying files security...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%$UpCase file is formatted for use in Windows 7 and later versions.
Checking volume bitmap (16671 kBytes)
12%24%36%49%61%73%85%98%100%    520.96 GB total disk space.
    252.29 GB in 3542 files.
      1048 KB in 34 directories.
     87512 KB in use by the system.
        64 MB occupied by the log/journal file.
         4 KB in each allocation unit.
 136566015 total allocation units on volume (520.96 GB).
  70408972 allocation units available on volume (268.59 GB).
The volume /dev/nvme0n1p5 has been repaired successfully.

----------
Partition /dev/nvme0n1p4 scan result:
Checking Volume /dev/nvme0n1p4...
Type of the filesystem is NTFS.
Volume label is: Data.
Verifying 50688 records...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%Verifying 7 file(s) with EAs...
Verifying 4065 folders...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%Verifying files security...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%$UpCase file is formatted for use in Windows 7 and later versions.
Checking volume bitmap (8344 kBytes)
24%49%73%98%100%    260.74 GB total disk space.
    216.51 GB in 46540 files.
     17300 KB in 4067 directories.
    142300 KB in use by the system.
        64 MB occupied by the log/journal file.
         4 KB in each allocation unit.
  68351999 total allocation units on volume (260.74 GB).
  11559789 allocation units available on volume (44.10 GB).
The volume /dev/nvme0n1p4 has been repaired successfully.

----------
Partition /dev/nvme0n1p3 scan result:
Checking Volume /dev/nvme0n1p3...
Type of the filesystem is NTFS.
Volume label is: OS.
Volume is marked as dirty.
Verifying 946432 records...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%Verifying 54876 file(s) with EAs...
Verifying 47917 folders...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%Minor inconsistencies detected on the volume. 35481 files contain incorrect links count.
Verifying files security...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%$UpCase file is formatted for use in Windows 7 and later versions.
Checking volume bitmap (5469 kBytes)
37%74%100%    170.90 GB total disk space.
     63.01 GB in 238751 files.
    137516 KB in 47919 directories.
      1.11 GB in use by the system.
        64 MB occupied by the log/journal file.
         4 KB in each allocation unit.
  44799999 total allocation units on volume (170.90 GB).
  30902495 allocation units available on volume (117.88 GB).
The volume /dev/nvme0n1p3 has been repaired successfully.

----------
Partition /dev/nvme0n1p1 scan result:
Checking Volume /dev/nvme0n1p1...
Check FAT fix error is not implemented
Init FAT from BOOT sector 0
Check BOOT sector
Compare FAT tables
Scan subdirectories tree
0%3%7%8%9%10%11%12%13%17%18%19%20%21%22%23%24%25%26%31%37%39%43%44%45%46%50%51%52%53%57%61%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%85%90%93%97%98%99%Scan FAT table
Look for lost clusters
    262152 KB total disk space.
     66990 KB in 303 files.
         0 KB in 97 directories.
         4 KB in each allocation unit.
     65538 total allocation units on volume (0.25 GB).
     48580 allocation units available on volume (0.19 GB).
The volume /dev/nvme0n1p1 appears to be OK.

----------
And nemo stills shows everything on nvme0n1p4 as locked, and unwritable. :)

Hopefully Windows still boots.

Added in 1 hour 56 minutes 34 seconds:
PorteuX 2.1 bug reports
Executable .sh files set to Open With Autorun Prompt don't get the prompt when dbl clicked. Right-clicking on the files and selecting the option doesn't work either.

PorteuX 2.1 bug reports

Posted: 05 Jun 2025, 11:17
by rych
Ed_P wrote:
05 Jun 2025, 04:50
And nemo stills shows everything on nvme0n1p4 as locked, and unwritable.
Is that on PorteuX straight after
The volume /dev/nvme0n1p4 has been repaired successfully.
by the fsck magic code?!
Consult GParted status on that partition, maybe use chkntfs, or reboot into Winddows for the ultimate chkdsk /f. See NTFS3 Kernel Module (Post by rych #99942)

PorteuX 2.1 bug reports

Posted: 05 Jun 2025, 17:43
by Ed_P
rych wrote:
05 Jun 2025, 11:17
Is that on PorteuX straight after
The volume /dev/nvme0n1p4 has been repaired successfully.
by the fsck magic code?!
Yes.
rych wrote:
05 Jun 2025, 11:17
reboot into Winddows for the ultimate chkdsk /f.
No problem shown on Windows, or any other OS.

Added in 4 minutes 9 seconds:

Code: Select all

Microsoft Windows [Version 10.0.26100.4061]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>chkdsk d: /f
The type of the file system is NTFS.
Volume label is Data.

Stage 1: Examining basic file system structure ...
  50688 file records processed.
File verification completed.
 Phase duration (File record verification): 532.09 milliseconds.
  9 large file records processed.
 Phase duration (Orphan file record recovery): 0.41 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.93 milliseconds.

Stage 2: Examining file name linkage ...
  105 reparse records processed.
  58818 index entries processed.
Index verification completed.
 Phase duration (Index verification): 1.02 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 8.45 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 2.26 milliseconds.
  105 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 1.97 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 2.21 milliseconds.
  4066 data files processed.
 Phase duration (Data attribute verification): 1.11 milliseconds.
CHKDSK is verifying Usn Journal...
  221360 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 3.22 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 273407999 KB total disk space.
 227026284 KB in 46532 files.
     17300 KB in 4067 indexes.
         0 KB in bad sectors.
    125259 KB in use by the system.
     65536 KB occupied by the log file.
  46239156 KB available on disk.

      4096 bytes in each allocation unit.
  68351999 total allocation units on disk.
  11559789 allocation units available on disk.
Total duration: 1.59 seconds (1592 ms).

C:\Windows\System32>
Added in 5 hours 4 minutes 6 seconds:
Ed_P wrote:
05 Jun 2025, 17:47
or any other OS.
Including "from=/ISOs/PorteuX/porteux-v2.0-current-cinnamon-6.4.9-x86_64.iso"

But the bash .sh files' Open With Autorun Prompt doesn't work here either.

The good thing is Porteux 2.0 & 2.1 support my Acer's display. :good:

PorteuX 2.1 bug reports

Posted: 06 Jun 2025, 10:46
by rych
Ed_P, Could you start Gparted and see if there is a warning sign about dirty bit, "Information" in partition context menu?

For example, I still get this: NTFS3 Kernel Module (Post by rych #99942) and would fix it by running under root:

Code: Select all

 chkntfs /dev/disk/by-label/Data -f
In your case, GParted might also report that it's mounted read-only, and why.

Porteus still uses a different driver by default, ntfs-3g. In Porteus, could you run something like

Code: Select all

mount | grep ntfs
in order to confirm that?

PorteuX 2.1 bug reports

Posted: 06 Jun 2025, 11:13
by porteux
Just to let you guys know that PorteuX comes with a proper NTFS fix utility that avoids using Windows at all.

It can be called either by 'fsck' cheatcode during boot time, or 'check-filesystem' after boot (requiring the units to be unmounted).

PorteuX 2.1 bug reports

Posted: 06 Jun 2025, 12:43
by Ed_P
As noted previously porteux, the ntfs problem doesn't exist in porteux 2.0. Or earlier porteux releases.

Code: Select all

~#  cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/PorteuX/porteux-v2.0-current-cinnamon-6.4.9-x86_64.iso volume=33 reboot=cold extramod=/porteux/Modules;/porteux/modsavedat kmap=us norootcopy noload=mychanges;My
Image

Will reboot 2.1 and update.