fsck on startup => recovering journal

Non release banter
benjibasson
Samurai
Samurai
Posts: 140
Joined: 06 Mar 2019, 15:14
Distribution: Arch linux

fsck on startup => recovering journal

Post#1 by benjibasson » 08 Jun 2023, 12:43

Hi

sometime when I launch Porteus v5 with fsck options I get an error message about the recovering journalisation on the sda3's ext4 partitions

here is the dmesg for this session

Code: Select all

dmesg | egrep -i 'fs|fail|error|warn|found|mount|system'
[    0.000000] Command line: BOOT_IMAGE=/porteus64bit_v50/boot/syslinux/vmlinuz from=/dev/sda3/porteus64bit_v50 load=999 resume=/dev/sda3 resume_offset=4268032 login=guest copy2ram ramsize=14% zram=43% noswap noauto fsck
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.007382] found SMP MP-table at [mem 0x000fd790-0x000fd79f]
[    0.008527] ACPI: ASF! 0x00000000DB9B2448 0000A5 (v32 INTEL   HCG     00000001 TFSM 000F4240)
[    0.008581] No NUMA configuration found
[    0.037829] Kernel command line: quiet BOOT_IMAGE=/porteus64bit_v50/boot/syslinux/vmlinuz from=/dev/sda3/porteus64bit_v50 load=999 resume=/dev/sda3 resume_offset=4268032 login=guest copy2ram ramsize=14% zram=43% noswap noauto fsck
[    0.037967] Unknown kernel command line parameters "copy2ram noswap noauto fsck BOOT_IMAGE=/porteus64bit_v50/boot/syslinux/vmlinuz from=/dev/sda3/porteus64bit_v50 load=999 login=guest ramsize=14% zram=43%", will be passed to user space.
[    0.074345] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.074360] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.191299] devtmpfs: initialized
[    0.191883] pinctrl core: initialized pinctrl subsystem
[    0.192541] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.675694] SCSI subsystem initialized
[    0.675694] usbcore: registered new interface driver usbfs
[    0.679423] system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
[    0.679630] system 00:01: [io  0x0680-0x069f] has been reserved
[    0.679634] system 00:01: [io  0xffff] has been reserved
[    0.679637] system 00:01: [io  0xffff] has been reserved
[    0.679638] system 00:01: [io  0xffff] has been reserved
[    0.679640] system 00:01: [io  0x1c00-0x1cfe] has been reserved
[    0.679641] system 00:01: [io  0x1d00-0x1dfe] has been reserved
[    0.679643] system 00:01: [io  0x1e00-0x1efe] has been reserved
[    0.679644] system 00:01: [io  0x1f00-0x1ffe] has been reserved
[    0.679645] system 00:01: [io  0x1800-0x18fe] has been reserved
[    0.679647] system 00:01: [io  0x164e-0x164f] has been reserved
[    0.679650] system 00:01: [io  0x3322-0x3323] has been reserved
[    0.679713] system 00:03: [io  0x1854-0x1857] has been reserved
[    0.679824] system 00:06: [io  0x04d0-0x04d1] has been reserved
[    0.910529] system 00:07: [mem 0xfed1c000-0xfed1ffff] has been reserved
[    0.910532] system 00:07: [mem 0xfed10000-0xfed17fff] has been reserved
[    0.910534] system 00:07: [mem 0xfed18000-0xfed18fff] has been reserved
[    0.910535] system 00:07: [mem 0xfed19000-0xfed19fff] has been reserved
[    0.910537] system 00:07: [mem 0xf8000000-0xfbffffff] has been reserved
[    0.910538] system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved
[    0.910539] system 00:07: [mem 0xfed90000-0xfed93fff] has been reserved
[    0.910541] system 00:07: [mem 0xfed45000-0xfed8ffff] has been reserved
[    0.910542] system 00:07: [mem 0xff000000-0xffffffff] has been reserved
[    0.910544] system 00:07: [mem 0xfee00000-0xfeefffff] could not be reserved
[    0.910546] system 00:07: [mem 0xf7fee000-0xf7feefff] has been reserved
[    0.910547] system 00:07: [mem 0xf7fd0000-0xf7fdffff] has been reserved
[    0.910706] pnp: PnP ACPI: found 8 devices
[    0.918825] Unpacking initramfs...
[    0.922410] Initialise system trusted keyrings
[    0.922585] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.922595] ntfs: driver 2.1.32 [Flags: R/W].
[    0.922602] ntfs3: Max link count 4000
[    0.922603] ntfs3: Enabled Linux POSIX ACLs support
[    0.922604] ntfs3: Read-only LZX/Xpress compression included
[    0.922668] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[    0.922783] aufs 6.3-20230515
[    0.958031] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.03
[    0.958139] hub 1-0:1.0: USB hub found
[    0.959570] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.03
[    0.959739] hub 2-0:1.0: USB hub found
[    0.963856] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.03
[    0.964000] hub 4-0:1.0: USB hub found
[    0.970064] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.03
[    0.970172] hub 3-0:1.0: USB hub found
[    0.980778] rtc_cmos 00:02: setting system clock to 2023-06-08T11:48:08 UTC (1686224888)
[    1.015149] Key type .fscrypt registered
[    1.015151] Key type fscrypt-provisioning registered
[    1.015443] Btrfs loaded, crc32c=crc32c-intel, zoned=no, fsverity=no
[    1.334112] usb 2-7: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
[    1.335310] usb 3-1: New USB device found, idVendor=8087, idProduct=8008, bcdDevice= 0.05
[    1.335710] hub 3-1:1.0: USB hub found
[    1.374681] usb 1-1: New USB device found, idVendor=8087, idProduct=8000, bcdDevice= 0.05
[    1.375279] hub 1-1:1.0: USB hub found
[    1.635575] usb 2-8: New USB device found, idVendor=5986, idProduct=0400, bcdDevice= 6.10
[    2.617328]   No soundcards found.
[    2.619683]     fsck
[    9.857487] EXT4-fs (sda3): mounted filesystem a96e19af-dd3a-46dd-b484-84d9607854ca with ordered data mode. Quota mode: disabled.
[    9.953268] EXT4-fs (sda5): mounted filesystem 63257c50-61e6-4542-8375-2fbc2c63b54d with ordered data mode. Quota mode: disabled.
[    9.992508] EXT4-fs (sda7): mounted filesystem 996a3bb1-ea58-4d10-bdb5-3c0897c1aad7 with ordered data mode. Quota mode: disabled.
[   27.737340] REISERFS warning (device loop14): sh-2006 read_super_block: bread failed (dev loop14, block 2, size 4096)
[   27.737346] REISERFS warning (device loop14): sh-2006 read_super_block: bread failed (dev loop14, block 16, size 4096)
[   28.338061] EXT4-fs (sda3): unmounting filesystem a96e19af-dd3a-46dd-b484-84d9607854ca.
[   28.394128] EXT4-fs (sda5): unmounting filesystem 63257c50-61e6-4542-8375-2fbc2c63b54d.
[   28.424574] EXT4-fs (sda7): unmounting filesystem 996a3bb1-ea58-4d10-bdb5-3c0897c1aad7.
[   29.413871] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20221020/utaddress-204)
[   29.420884] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20221020/utaddress-204)
[   29.426375] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20221020/utaddress-204)
[   29.426384] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20221020/utaddress-204)
[   29.430901] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20221020/utaddress-204)
[   29.430910] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20221020/utaddress-204)
[   29.430918] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   29.570072] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   29.570077] cfg80211: failed to load regulatory.db
[   30.255005] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq failed with error -2
[   30.255012] Bluetooth: hci0: failed to open Intel firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq (-2)
[   30.255052] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.bseq failed with error -2
[   30.255055] Bluetooth: hci0: failed to open default fw file: intel/ibt-hw-37.7.bseq
[   30.487619] intel_rapl_common: Found RAPL domain package
[   30.487622] intel_rapl_common: Found RAPL domain core
[   30.487623] intel_rapl_common: Found RAPL domain uncore
[   30.487624] intel_rapl_common: Found RAPL domain dram
[   30.662995] usb 2-8: Found UVC 1.00 device BisonCam, NB Pro (5986:0400)
[   30.672684] Adding 3471424k swap on /dev/zram0.  Priority:100 extents:1 across:3471424k SSFS
[   32.328903] EXT4-fs (sda3): mounted filesystem a96e19af-dd3a-46dd-b484-84d9607854ca with ordered data mode. Quota mode: disabled.
[   32.371604] Adding 10239996k swap on /mnt/sda3/swapfile.swap.  Priority:-2 extents:148 across:163168256k FS
[  100.748739] aufs may_rename_srcdir:561:Cache2 I/O[2143]: renaming dir who has child(ren) on multiple branches, is not supported
is something going wrong or all is all right?

Cheers

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

fsck on startup => recovering journal

Post#2 by Ed_P » 08 Jun 2023, 17:41

I would try booting with less cheatcodes. I've never heard of some of the ones you're specifying, where did you find a need for them?

Try just:

Code: Select all

BOOT_IMAGE=/porteus64bit_v50/boot/syslinux/vmlinuz from=/dev/sda3/porteus64bit_v50  copy2ram 
Ed

benjibasson
Samurai
Samurai
Posts: 140
Joined: 06 Mar 2019, 15:14
Distribution: Arch linux

fsck on startup => recovering journal

Post#3 by benjibasson » 08 Jun 2023, 21:41

Ed_p
I need them to be able to hybernate to swapfile reserved for porteus
999 is the change in .xzm. smaller than the change directory faster to load

In fact when I write to the ext4 partitions to update module or back up office documents , fsck give the message about journalisation recovery instead to give once 'clean' line per partition.

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

fsck on startup => recovering journal

Post#4 by Ed_P » 08 Jun 2023, 22:14

Rather than hybernating to a swapfile it might be faster to create a savedat file and use a changes=EXIT:yourfolder/changes/save.dat

Another option: menu > Admin > Porteus Settings Centre > 5th option to the right Save Settings > Save Your Current Porteus Session to a module in your /porteus/modules folder.

In reviewing your original posting this line stood out:

Code: Select all

[    0.037967] Unknown kernel command line parameters "copy2ram noswap noauto fsck BOOT_IMAGE=/porteus64bit_v50/boot/syslinux/vmlinuz from=/dev/sda3/porteus64bit_v50 load=999 login=guest ramsize=14% zram=43%", will be passed to user space.
Ed

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

fsck on startup => recovering journal

Post#5 by ncmprhnsbl » 09 Jun 2023, 04:49

benjibasson wrote:
08 Jun 2023, 12:43
sometime when I launch Porteus v5 with fsck options I get an error message about the recovering journalisation on the sda3's ext4 partitions
afaia, it's fairly normal for fsck to report some 'recovering journal', if that's what it decides it needs to do .. not really a error message, but a message about errors with the filesystem that it's fixing.
i gather the cause of this is "unclean unmounting", which is something i'd need to learn more about.
if it reports a failure to recover the journal, now that's a problem.
if you want more time to read the fsck messages, add 'debug' cheatcode and this will stop the initrd sequence at each process.
Ed_P wrote:
08 Jun 2023, 22:14
Rather than hybernating to a swapfile it might be faster to create a savedat file and use changes=EXIT:yourfolder/changes/save.dat
i'm struggling to understand how these two things could be remotely interchangable or even related ??
and all of those cheatcodes are completely legit and not a problem.
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

fsck on startup => recovering journal

Post#6 by Ed_P » 09 Jun 2023, 19:58

ncmprhnsbl wrote:
09 Jun 2023, 04:49
and all of those cheatcodes are completely legit and not a problem.
So this error message is meaningless?

Code: Select all

[    0.037967] Unknown kernel command line parameters "copy2ram noswap noauto fsck BOOT_IMAGE=/porteus64bit_v50/boot/syslinux/vmlinuz from=/dev/sda3/porteus64bit_v50 load=999 login=guest ramsize=14% zram=43%", will be passed to user space.
Ed

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

fsck on startup => recovering journal

Post#7 by ncmprhnsbl » 10 Jun 2023, 00:04

Ed_P wrote:
09 Jun 2023, 19:58
So this error message is meaningless?
it highlights the difference between "kernel command line parameters" and "porteus cheatcodes"
the former are used by the kernel to do stuff and the latter are "passed to user space" for porteus to do stuff(mostly either via initrd or init scripts).
:)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply