Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 04, 2024 11:50AM
Pogoplug e02


After upgrading to Linux Kernel 6.8.7 Kirkwood (from linux-6.7.5-kirkwood-tld-1), cannot login anymore into device.
Linux debian system is on usb device.
I didn't touch anything else, just upgrade via putty ssh port 22 from lan, sync, then reboot.

screnshots from putty, winscp
https://i.postimg.cc/RFsqG1kq/putty.jpg
https://i.postimg.cc/wM1Mryz2/winscp.jpg


"arp -a" shows device is online, i can ping it too.


followed instruction from page
https://forum.doozan.com/read.php?2,12096,page=1

step 4 is 4a.


Regarding 5.a Important Note: Check your uInitrd size to see if it is larger than 11 MB.
i did this last year (adjusted u-boot envs so uInitrd can be larger than 11 MB)
https://forum.doozan.com/read.php?2,132765

https://forum.doozan.com/read.php?3,12381
Quote

B. Load addresses for large systems
Set the env permanently to give another 16MB to load uInitrd (i.e. allow for initrd that is up to 27 MB in size).
i did B.1 step

Quote

fw_setenv load_dtb_addr 0x2c00000


Uboot is latest 2017.07-2023.04 U-Boot.


How can revert back to linux-6.7.5-kirkwood-tld-1 (i didn't remove it) ?



ps
just checked, unplugged ubs drive, i have Jeff Rescue System v2 installed on pogo e02, managed to login via ssh
https://forum.doozan.com/read.php?4,3896
Quote

rescue:~# uname -a
Linux rescue 3.3.2-kirkwide #1 Mon Oct 29 17:52:07 CDT 2012 armv5tel GNU/Linux



here is fw_printenv output:
Quote

arcNumber=3542
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_rescue
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_pogo=run bootcmd_rescue
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
ethact=egiga0
ethaddr=XXXXXXXXXXXXXXXXX
if_netconsole=ping $serverip
ipaddr=XXXXXXXXXXXXXXXXX
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x2c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=dd6
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
rescue_installed=1
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=XXXXXXXXXXXXXXXXX
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi
usb_ready_retry=15



Edited 18 time(s). Last edit at 05/04/2024 12:47PM by jst818.
Attachments:
open | download - putty.jpg (5.9 KB)
open | download - winscp.jpg (17.4 KB)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 04, 2024 12:40PM
I ran netcat
https://forum.doozan.com/read.php?3,14,page=1


output (from win 10), with one (1) usb linux debian device attached :
Quote

\Netcat>nc -l -u -p 6666

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 2048 10235904 fcf2fcf2-01 07 Boot
2 10237952 4192965 fcf2fcf2-02 07
3 14432256 1985964032 fcf2fcf2-03 07

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 661 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
6179248 bytes read in 857 ms (6.9 MiB/s)
loading uInitrd ...
12102926 bytes read in 953 ms (12.1 MiB/s)
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
10322 bytes read in 2076 ms (3.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-6.8.7-kirkwood-tld-1
Created: 2024-05-04 16:29:08 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6179184 Bytes = 5.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-6.8.7-kirkwood-tld-1
Created: 2024-05-04 16:29:13 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 12102862 Bytes = 11.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02c00000
Booting using the fdt blob at 0x2c00000


Starting kernel ...

Imho something went wrong with 5.a step and now weird behaviour follows.



Edited 2 time(s). Last edit at 05/04/2024 12:43PM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 04, 2024 01:43PM
jst818,

> ## Loading init Ramdisk from Legacy Image at
> 01100000 ...
> Image Name: initramfs-6.8.7-kirkwood-tld-1
> Created: 2024-05-04 16:29:13 UTC
> Image Type: ARM Linux RAMDisk Image (gzip
> compressed)
> Data Size: 12102862 Bytes = 11.5 MiB

> Imho something went wrong with 5.a step and now
> weird behaviour follows.

Yes, your Initrd size has grown larger.

Boot with netconsole again as above

Quote

Netcat>nc -l -u -p 6666

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02

Interrupt the count down, and

setenv load_dtb_addr 0x1c00000
setenv load_initrd_addr 0x2100000 
setenv load_uimage_addr 0x800000

And then
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 04, 2024 03:31PM
For some reason boot with netconsole and entering those 3 commands doesn't save settings.

Now i installed "Debian-5.6.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2" into other usb stick, can log into, but got stuck with those 3 commands

-bash: setenv: command not found.

I guess i need to use command
fw_setenv


Is this correct form ?

fw_setenv load_dtb_addr '0x1c00000'
fw_setenv load_initrd_addr '0x2100000'
fw_setenv load_uimage_addr '0x800000'
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 04, 2024 03:47PM
@jst818,

So did it boot OK? please be more verbose. I need to confirm this fact so I can update the instruction.

> For some reason boot with netconsole and entering
> those 3 commands doesn't save settings.

The setenvs are only temporary.

>
> Now i installed
> "Debian-5.6.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2"
> into other usb stick, can log into, but got stuck
> with those 3 commands

> Is this correct form ?
>
> fw_setenv load_dtb_addr '0x1c00000'
> fw_setenv load_initrd_addr '0x2100000'
> fw_setenv load_uimage_addr '0x800000'

Yes, fw_setenv are used in Debian. What you should do in Debian is
fw_printenv
And then see that the envs look OK, go ahead and do

fw_setenv load_dtb_addr '0x1c00000'
fw_setenv load_initrd_addr '0x2100000'
fw_setenv load_uimage_addr '0x800000'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 04, 2024 03:54PM
After doing 3 setenvs it did boot, but problem stayed the same (cannot log into - connection refused).

Will found out what happens when i use fw_setenv from normal boot, but using newly created rootfs "Debian-5.6.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2".



Update:
nope, it didn't help with fw_setenv either (cannot log into - connection refused).



Will continue tomorrow.



Edited 3 time(s). Last edit at 05/04/2024 04:05PM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 04, 2024 04:10PM
OK.

Also see this note it the isntruction for Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2

Quote

Note 7. Ethernet Naming Issue (Optional):

In Debian 12.4, the ethernet "Predictable Names" scheme is enabled. So the ethernet device assigned is no longer "eth0", but is "end0". This "predictable naming" scheme broke a lot of existing applications that still relying on "eth0" is the network device name. It does not affect this Kirkwood rootfs (due to some setup I had in the past).

However, if after a future Debian upgrade of this rootfs, the network is no longer eth0, then this is the way to bring it back.

cat /etc/network/interfaces
rename /end0=eth0
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
Beware of software apps, such as OMV, that do not respect users' configuration and so wiping out this change during its installation! I'd suggest to make a backup of this file, so you can compare that with any new /etc/network/interfaces after installing OMV, and restore the rename command.

There are also many other ways to force the eth0 name. However, it is more cumbersome to do than just watching out for this file being changed by OMV or other major apps installation. Also, other methods might not survive a future Debian upgrade :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 06, 2024 10:11AM
Update

Found debian 11.9 backup (kernel 6.6.3), upgraded to "linux-6.8.7-kirkwood-tld-1-bodhi.tar.bz2" and got the same problem.

I even did: [HowTo] Shrink initramfs (gzip method)
https://forum.doozan.com/read.php?2,135322
uImage 6,08 MB
uInitrd 4,89 MB

before was uInitrd ~10,9MB
plus did all 3
Quote

fw_setenv load_dtb_addr '0x1c00000'
fw_setenv load_initrd_addr '0x2100000'
fw_setenv load_uimage_addr '0x800000'

Issue has nothing to do with
Ethernet Naming Issue in Debian 12.4
https://forum.doozan.com/read.php?2,35581



Edited 2 time(s). Last edit at 05/06/2024 10:12AM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 06, 2024 10:44AM
My latest hypothesis include: PeerGuardian (got this package installed around 8 years ago** and was working fine (the whole system&package) until got kernel "linux-6.8.7")
https://sourceforge.net/projects/peerguardian/files/PeerGuardian%20Linux/2.3.1/

**edit: it was Debian stretch Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 24 Jul 2017 or even Debian jessie from 24 Feb 2015 (Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2)


https://forum.doozan.com/read.php?2,12096
Quote

Updated 18 Apr 2024:

Kernel linux-6.8.7-kirkwood-tld-1 package has been uploaded. The following features were added/updated:

- General kernel upgrade.
"General kernel upgrade" are usually major suspects to break something that was working fine.


Why i believe this is the case (combination of PeerGuardian +kernel linux-6.8.7, not only the latter) ?
Found spare usb and installed clean latest roofs "Debian-5.6.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2", upgraded to kernel "linux-6.8.7" [1], upgraded to debian 12 [2] (one step at time [1], [2]), and i still haven't got "connection refused".

Then i wanted to replicate now my broken setup with installing PeerGuardian 2.3.1 into latest debian with kernel 6.8.7 (upgrade from clean latest roofs 5.6.7), plus debian 12.4.


https://web.archive.org/web/20200225092735/http://lazydroid.com/2013/05/raspberry-pi-peerguardian-moblock-setup/
https://mitchtech.net/peer-guardian-on-raspberry-pi/#comment-3113885377
after some reading (file INSTALL) i got what is bare minimum:
./configure -disable-dbus  -enable-lowmem  -without-qt4 -sysconfdir=/etc

required steps:
unpack pgl-2.3.1.tar.gz
cd /pgl-2.3.1 #where are files

./autogen.sh OR autoreconf
./configure #for bare minimum look above
make
make install


./configure step is where i got stuck, error message was something about netfilter ip tables, something long (2 lines error).
Wasted around 3 hours yesterday, then had something else to do.
From what i remember, 8 years ago had no problems installing PeerGuardian.


Will try again when i have some spare time, right now i am running debian 11.9, kernel 6.7.5 and shrinked initramfs.



Edited 4 time(s). Last edit at 05/06/2024 10:51AM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 06, 2024 01:49PM
@jst818,

Please post serial console boot log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 06, 2024 02:55PM
Serial console boot log when i get "connection refused" error ?



Edited 1 time(s). Last edit at 05/06/2024 02:55PM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 06, 2024 03:24PM
> Serial console boot log when i get "connection
> refused" error ?

Yes!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 08, 2024 12:29PM
Interesting.
debian 11.9, kernel 6.8.7

Cloned rootfs to spare usb key which surprisingly works fine with kernel 6.8.7 (roofs ext4 , swap partition, NO data partition )
ext4 rootfs was made in terminal, and there is no raid/lvm or anything else, only plain ntfs partition which mounted just fine with kernel 6.7.5:
mkfs.ext4  -L rootfs -E lazy_itable_init=0  -O 64bit /dev/sdc1

original rootfs with (roofs, swap partition + ntfs data partition via ntfs-3g) results "connection refused".
I didn't see that coming.

ntfs data partition via ntfs-3 is mounted into /mnt/hdd
cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# /dev/root      /               ext3    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0

LABEL=rootfs    /               ext4    noatime,errors=remount-ro 0 1
/dev/sda3 /mnt/hdd ntfs-3g defaults,big_writes 0 0
/dev/sda2	 none	  swap	   defaults	  0 0


from serial log
Quote

[ OK ] Mounted /tmp.
[ 34.952347][ T312] /dev/sda3: Can't open blockdev
[FAILED] Failed to mount /mnt/hdd.
See 'systemctl status mnt-hdd.mount' for details.
[DEPEND] Dependency failed for Local File Systems.
[ OK ] Stopped Dispatch Password …ts to Console Directory Watch.
[ OK ] Stopped Forward Password R…uests to Wall Directory Watch.
[ OK ] Reached target Timers.
Starting Raise network interfaces...
Starting Preprocess NFS configuration...
[ OK ] Reached target Login Prompts.
[ OK ] Reached target Sockets.
[ OK ] Started Emergency Shell.
[ OK ] Reached target Emergency Mode.
Starting Create Volatile Files and Directories...
[ OK ] Finished Preprocess NFS configuration.
Starting NFSv4 ID-name mapping service...
[ OK ] Reached target NFS client services.
[ OK ] Started NFSv4 ID-name mapping service.
[ OK ] Finished Create Volatile Files and Directories.
Starting RPC bind portmap service...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started RPC bind portmap service.
[ OK ] Finished Update UTMP about System Boot/Shutdown.
[ OK ] Reached target RPC Port Mapper.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Finished Update UTMP about System Runlevel Changes.
[ 39.509640][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): [ 44.460771][ T446] NFSD: Unable to initialize client recovery tracking! (-110)
[ 44.468149][ T446] NFSD: starting 90-second grace period (net f0000000)


[?2004hroot@pogo:~#  systemctl status mnt-hdd.mount
root@pogo:~# systemctl status mnt-hdd.mount
[?2004l
* mnt-hdd.mount - /mnt/hdd
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Sun 2023-06-18 16:56:06 CEST; 56s ago
Where: /mnt/hdd
What: /dev/sda3
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
CPU: 515ms

Jun 18 16:56:04 pogo systemd[1]: Mounting /mnt/hdd...
Jun 18 16:56:05 pogo mount[312]: ntfs-3g-mount: mount failed: Device or resource busy
Jun 18 16:56:06 pogo systemd[1]: mnt-hdd.mount: Mount process exited, code=exited, status=21/n/a
Jun 18 16:56:06 pogo systemd[1]: mnt-hdd.mount: Failed with result 'exit-code'.
Jun 18 16:56:06 pogo systemd[1]: 


apt show ntfs-3g
Quote

[?2004l
Package: ntfs-3g
Version: 1:2017.3.23AR.3-4+deb11u3
Priority: optional
Section: otherosfs
Maintainer: Laszlo Boszormenyi (GCS) <gcs@debian.org>
Installed-Size: 1418 kB
Depends: libc6 (>= 2.17), libgcrypt20 (>= 1.8.0), libgnutls30 (>= 3.7.0), libntfs-3g883 (= 1:2017.3.23AR.3-4+deb11u3), fuse
Suggests: fdisk
Homepage: http://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g.html
Tag: admin::filesystem, hardware::storage, implemented-in::c,
interface::commandline, interface::shell, role::program, scope::utility
Download-Size: 404 kB
APT-Manual-Installed: yes
APT-Sources: http://deb.debian.org/debian bullseye/main armel Packages
Description: read/write NTFS driver for FUSE
NTFS-3G uses FUSE (Filesystem in Userspace) to provide support for the NTFS
filesystem used by Microsoft Windows.



Jun 18 16:56:04
btw, not sure where this date/time from log is coming from (it is both wrong).


Attacked whole log (log.zip).



Edited 1 time(s). Last edit at 05/08/2024 12:35PM by jst818.
Attachments:
open | download - log1.jpg (121.9 KB)
open | download - log2.jpg (110.9 KB)
open | download - log serial.zip (10.6 KB)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 08, 2024 12:46PM
For test purposes commented ntfs line in
/etc/fstab
/dev/sda3 /mnt/hdd ntfs-3g defaults,big_writes 0 0

now system boots fine, debian 11.9, kernel 6.8.7, no "connection refused". via ssh.



On win machine ran chkdsk /f f:
and got result everything is ok with ntfs data partition.
Windows has checked the file system and found no problems.



Edited 1 time(s). Last edit at 05/08/2024 01:05PM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 08, 2024 01:59PM
Quote

Jun 18 16:56:04
btw, not sure where this date/time from log is coming from (it is both wrong).

This box does not have RTC, so we need to install fake-hwclock to get a sane system time each boot.

Quote

For test purposes commented ntfs line in
/etc/fstab

/dev/sda3 /mnt/hdd ntfs-3g defaults,big_writes 0 0

now system boots fine, debian 11.9, kernel 6.8.7, no "connection refused". via ssh.

I'd suggest removing this from fstab permanently. If you use sysvinit, the mount statement can be placed in /etc/rc.local. If you use systemd, then create a target to mount it.

fstab is not useful anymore for things other than for rootfs and swap file/partition. And whenever there is some problem, it could propagate to other part of Debian. So in my systems, all data partitions are mounted after rootfs has been mounted and Debian is running.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 08, 2024 02:18PM
Ok, removed
/dev/sda3 /mnt/hdd ntfs-3g defaults,big_writes 0 0
from /etc/fstab

added it to /etc/rc.local, reboot

and still got mount error:
root@pogo:~# ntfs-3g /dev/sda3 /mnt/hdd
ntfs-3g-mount: mount failed: Device or resource busy

Again, with all previous kernels except 6.8.7 it was ntfs-3g mount doing fine.



Edited 2 time(s). Last edit at 05/08/2024 02:20PM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 08, 2024 02:36PM
How about remove that from /etc/rc.local, and just mount it at command line like this
mount -o noatime,big_writes /dev/sda3 /media/sda3

or if the partition has a label:
mount -L $disk_label -o noatime,big_writes /media/$disk_label

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 08, 2024 03:00PM
ntfs-3g looks like no-go combination with kernel 6.8.7 at least for me (ntfs-3g-mount: mount failed: Device or resource busy)., fstab or mount makes no difference.



Edited 1 time(s). Last edit at 05/08/2024 03:01PM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 09, 2024 04:55AM
Looks like kernel 6.8.7 is not so innocent upgrade for ntfs-3g "module":

https://forum.manjaro.org/t/unable-to-mount-all-ntfs-partitions-in-kernel-6-8-4/159438
https://forum.manjaro.org/t/fstab-ntfs-3g-boots-with-kernel-6-6-26-1-not-with-6-8-5-1/160144
https://forum.manjaro.org/t/unable-to-mount-fat-or-ntfs-drives-after-updating/149354/45?page=3


And if you use ntfs3 (not ntfs-3g), you will probably have to adjust mount options, otherwise you will get read access only

https://forum.manjaro.org/t/not-booting-with-kernel-6-8-infinite-3-dots-manjaro-logo-animation/159597/13

https://forum.manjaro.org/t/stable-update-2024-03-13-plasma-5-27-11-firefox-thunderbird-amdvlk-qemu/158183/2
Quote

issues with auto-mount of ntfs filesystem using Kernel 6.8
The kernel changed default ntfs driver from FUSE one to ntfs3.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab (or any other application, such as VeraCrypt) they need to be changed.

Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev

Solution:
Migrate your mount options. For me the changes were:

allow_other → umask=000
default_permissions → [drop]
user_id=1000 → uid=1000
group_id=1000 → gid=1000

https://wiki.archlinux.org/title/NTFS-3G
https://wiki.archlinux.org/title/NTFS


tl;dr
kernel +6.8.7 + ntfs-3g is no go


Some more happy info
https://forum.manjaro.org/t/unable-to-mount-fat-or-ntfs-drives-after-updating/149354/46
Quote

And because Kernel 6.9 will completely remove ntfs-3g 2, it needs adjusting many things to adopt the new modifications.
https://lore.kernel.org/lkml/20240308-vfs-ntfs-ede727d2a142@brauner/


bonus
https://forum.manjaro.org/t/re-ntfs3-keeps-corrupting-my-ntfs-partitons/157736


this one is newer ntfs as ntfs-3g from debian repo (at least for buster, bullseye).
https://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=ntfs-3g


Release 2022.10.3, Oct 31, 2022
tuxera/ntfs-3g: NTFS-3G Safe Read/Write NTFS Driver
https://github.com/tuxera/ntfs-3g



Edited 8 time(s). Last edit at 05/09/2024 12:53PM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 09, 2024 07:01PM
Quote

Some more happy info
https://forum.manjaro.org/t/unable-to-mount-fat-or-ntfs-drives-after-updating/149354/46
Quote

And because Kernel 6.9 will completely remove ntfs-3g 2, it needs adjusting many things to adopt the new modifications.

Yes. That would be best.

Regardless, I would still recommend avoid mounting data partition in fstab. Let the kernel boot and rootfs mounted first so you'd have a working system.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 05/09/2024 07:03PM by bodhi.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 10, 2024 03:18PM
Will stay with 6.7.5 kernel, my pogo is a minimum decade old (bought second hand).


ntfs3 blacklisted in opensuse
https://forums.opensuse.org/t/ntfs3-kernel-module-suddenly-blacklisted-after-update-to-tumbleweed-20231215/171073
https://lore.kernel.org/ntfs3/bf4e968b-aa2a-d886-afd0-1f6f5c02d24e@gmail.com/T/#t

Where is "60-blacklist_fs-ntfs3.conf" equivalent location in linux debian ?



more bizarre news about ntfs3
https://www.theregister.com/2022/04/29/problems_for_the_linux_kernel_ntfs/



Edited 2 time(s). Last edit at 05/10/2024 03:40PM by jst818.
Re: Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device
May 10, 2024 04:46PM
>
> Where is "60-blacklist_fs-ntfs3.conf" equivalent
> location in linux debian ?

This is how I blacklist the kirkwood_thermal on Zyxel NSA325

cat /etc/modprobe.d/kirkwood-thermal-blacklist.conf
# This file blacklists the kirkwood_thermal module on ZyXEL boxes with 6282 SoC

blacklist kirkwood_thermal

So just add a new conf file blacklist_fs-ntfs3.conf.
blacklist ntfs3

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: