Clara HD Cannot mount KOBOeReader partition once converted to ext4

[bunbury]

I have dropbear running on my Clara HD.
I changed the mount and dosfck commands so it can mount ext4 partitions as well.
It's working quite good. I have converted and expanded the /mnt/onboard partition.
EXCEPT
Linux (or another computer) does not mount the partition over usb anymore.

I still have the dialog on the Kobo, but nothing gets mounted when I accept it.

Do you have any idea how come ?

Can anyone explain to me how this automount works ?
Detection of USB connexion on the Kobo triggers a dialog that when accepted mount the partition over USB ?

[geek1011]

I do not recommend doing this at all. For one, you'll end up with issues after an automatic firmware upgrade. Also, there isn't much benefit to converting the partition in the first place.

If you insist, can you send the output of `lsusb` on the computer, and `fdisk -l`, the last part of `dmesg`, and `mount` on the Kobo?

[bunbury]

Thank you for your help offer and your concern.
For what I am doing, I need symlinks and various things vfat does not provide.
And I have a backup stock sdcard just in case

Here is fdisk -l on the kobo. I did that with parted and it looks ok.
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 768,0,1 1023,3,16 49152 573440 524289 256M 83 Linux
/dev/mmcblk0p2 1023,3,16 1023,3,16 573441 1097729 524289 256M 83 Linux
/dev/mmcblk0p3 1023,3,16 1023,3,16 1097730 124735487 123637758 58.9G 83 Linux

Here are the mount points
/dev/root on / type ext4 (rw,noatime,nodiratime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=254044k,nr_inodes=63511,mode=755 )
none on /proc type proc (rw,relatime)
none on /tmp type tmpfs (rw,relatime,size=16384k)
none on /dev type tmpfs (rw,relatime)
none on /var/lib type tmpfs (rw,relatime,size=16k)
none on /var/log type tmpfs (rw,relatime,size=16k)
none on /var/run type tmpfs (rw,relatime,size=128k)
none on /sys type sysfs (rw,relatime)
/dev/mmcblk0p3 on /mnt/onboard type ext4 (rw,noatime,nodiratime,data=ordered)

And this is the result of dmesg | grep mmc
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
mmc1: new high speed SDIO card at address 0001
mmc1: card 0001 removed
mmc1: new high speed SDIO card at address 0001
mmc1: card 0001 removed
mmc1: new high speed SDIO card at address 0001
mmc1: card 0001 removed
mmc1: new high speed SDIO card at address 0001

This is how the kobo is recognized by lsusb once connected (after dialog confirmation)
Bus 001 Device 009: ID 2237:4228 Kobo Inc. eReader-4.23.15548

This is what the kernel does on the desktop when the kobo is plugged in (dmesg)
[83321.142976] usb 1-6: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[83321.142979] usb 1-6: Product: eReader-4.23.15548
[83321.142982] usb 1-6: Manufacturer: Kobo
[83321.142985] usb 1-6: SerialNumber: N249870178900
[83321.145343] usb-storage 1-6:1.0: USB Mass Storage device detected
[83321.145922] scsi host6: usb-storage 1-6:1.0
[83322.154242] scsi 6:0:0:0: Direct-Access Linux File-Stor Gadget 0401 PQ: 0 ANSI: 2
[83322.154836] sd 6:0:0:0: Attached scsi generic sg1 type 0
[83322.155390] sd 6:0:0:0: Power-on or device reset occurred
[83322.178113] sd 6:0:0:0: [sda] Attached SCSI removable disk

And after that nothing.
There is only /dev/sda. No partition, no sda1, nothing.

Any idea ?

[NiLuJe]

That's probably because the USBMS script auto-detects and only exports vfat partitions (and then only remounts a hard-coded one as vfat).

[bunbury]

Well that was elsewhere but yeah it was a problem of vfat being hardcoded in some script.
Thanks, it is now fixed !