SliTaz Forum
You are not logged in.
Hi,
I am here on Slitaz 4, 2.6.37-slitaz kernel. My problem is that it cannot recognize a USB-stick that has an ext4 filesystem.
Installed is e2fs.prog 1.41.14 (Filesystem utilities for use with ext2 and ext3 (without fsck*).
But for Slitaz 4 I could not find a newer version.
The konsole tells me:
root@t41deslitaz:~# fdisk -l /dev/sda
Disk /dev/sda: 31.9 GB, 31981568000 bytes
64 heads, 32 sectors/track, 30500 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/sda1 2 30500 31230976 83 Linux
root@t41deslitaz:~# fdisk -l /dev/sda1
Disk /dev/sda1: 31.9 GB, 31980519424 bytes
64 heads, 32 sectors/track, 30499 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk /dev/sda1 doesn't contain a valid partition table
root@t41deslitaz:~# e2fsck /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda1 has unsupported feature(s): 64bit FEATURE_R10
e2fsck: Get a newer version of e2fsck!
Offline
Install the attached e2fsprogs-1.44.2.tazpkg built for slitaz-4.0
Offline
As usual, Mojo: 1001x thanks. I will report here when applying it.
Uninstalling the old one and installing this was flawless. But it did not help:
root@t41deslitaz:/home/tux# mount /dev/hda7 /mnt/sda7
mount: mounting /dev/hda7 on /mnt/sda7 failed: Invalid argument
root@t41deslitaz:/home/tux# uname -a
Linux t41deslitaz 2.6.37-slitaz #2 SMP Sat Oct 22 04:09:26 CEST 2016 i686 GNU/Linux
Offline
I hit the 64bit error on partition sda9 of my computer with slitaz-4.
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda9 has unsupported feature(s): 64bit
e2fsck: Get a newer version of e2fsck!
Don't copy/paste /dev/XXXX as they are from my system for example only.
Updating to e2fsprogs-1.44.2 stopped the error on my slitaz-4.0:
Run e2fsck against an unmounted partition /dev/sda9:
[c]root@slitaz:/home/tux# e2fsck -f -C 0 /dev/sda9[/c]
[c]e2fsck 1.44.2 (14-May-2018)[/c]
[c]Pass 1: Checking inodes, blocks, and sizes[/c]
[c]Pass 2: Checking directory structure[/c]
[c]Pass 3: Checking directory connectivity[/c]
[c]Pass 4: Checking reference counts[/c]
[c]Pass 5: Checking group summary information[/c]
[c]/dev/sda9: 862287/3276800 files (0.3% non-contiguous), 5571617/13107200 blocks[/c]
[c]root@slitaz:/home/tux# e2fsck /dev/sda9[/c]
[c]e2fsck 1.44.2 (14-May-2018)[/c]
[c]/dev/sda9: clean, 862287/3276800 files, 5571617/13107200 blocks[/c]
Using this method you should see an error message on mount failure that may point to a solution.
Open terminal 1,type the following,hit enter,and leave the terminal open:
[c]tail -f /var/log/messages[/c]
Open terminal 2,type the mount command,look for error messages if mount fails in terminal 1:
My mount command in terminal 2:
[c]root@slitaz:/home/tux# mount /dev/sda9 /mnt[/c]
New message in terminal 1 on my system with successful mount:
Mar 4 13:15:37 (none) user.info kernel: EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
Notes:
Slitaz-4 uses busybox mount applet that has no verbose switch for mount command.
Slitaz-5 and most other distributions use mount command from util-linux which has verbose switch for troubleshooting mount failures.
Offline
If I do it like this it fails with the following messages seen in the second konsole:
Mar 4 20:55:06 (none) auth.notice su: + /dev/pts/1 tux:root
Mar 4 20:55:42 (none) daemon.err udevd[1736]: bind failed: Address already in use
Mar 4 20:55:42 (none) user.notice error binding udev control socket
Mar 4 20:55:42 (none) daemon.err udevd[1736]: error binding udev control socket
Mar 4 20:56:19 (none) daemon.err udevd[1739]: bind failed: Address already in use
Mar 4 20:56:19 (none) user.notice error binding udev control socket
Mar 4 20:56:19 (none) daemon.err udevd[1739]: error binding udev control socket
Mar 4 20:56:34 (none) auth.notice su: - /dev/pts/2 tux:root
Mar 4 20:56:39 (none) auth.notice su: + /dev/pts/2 tux:root
Mar 4 20:57:30 (none) user.err kernel: EXT4-fs (hda7): couldn't mount RDWR because of unsupported optional features (400)
Mar 4 20:57:30 (none) daemon.err udevd[1753]: bind failed: Address already in use
Mar 4 20:57:30 (none) user.notice error binding udev control socket
Mar 4 20:57:30 (none) daemon.err udevd[1753]: error binding udev control socket
Mar 4 20:57:30 (none) user.err kernel: EXT4-fs (hda7): couldn't mount RDWR because of unsupported optional features (400)
Mar 4 20:57:30 (none) user.err kernel: EXT4-fs (hda7): couldn't mount RDWR because of unsupported optional features (400)
But I fail to understand what it really means. ;-)
I should mention that it is a 32-bit machine. To install another Linux I had to use the "forcepae" option in the kernel line when booting the Live-CD.
Uff, the error message led me to this thread whereelse:
https://www.snbforums.com/threads/ext4-drive-doesnt-mount.45637/
Seems to be beyond what I could do with ease.
user# tune2fs -l /dev/sda7 | grep features
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Whatever, this might be the solution: "tune2fs -O ^metadata_csum /dev/sda7" in my case. Will report later.
Offline
Ok, done. At least the error message in the 2.nd console is changed! ;-)
tux@t41deslitaz:~$ tail -f /var/log/messages
Mar 4 22:04:02 (none) auth.notice su: + /dev/pts/1 tux:root
Mar 4 22:04:36 (none) daemon.err udevd[1723]: bind failed: Address already in use
Mar 4 22:04:36 (none) user.notice error binding udev control socket
Mar 4 22:04:36 (none) daemon.err udevd[1723]: error binding udev control socket
Mar 4 22:04:36 (none) user.warn kernel: JBD: Unrecognised features on journal
Mar 4 22:04:36 (none) user.err kernel: EXT4-fs (hda7): error loading journal
Mar 4 22:04:36 (none) user.warn kernel: JBD: Unrecognised features on journal
Mar 4 22:04:36 (none) user.err kernel: EXT4-fs (hda7): error loading journal
Mar 4 22:04:36 (none) user.warn kernel: JBD: Unrecognised features on journal
Mar 4 22:04:36 (none) user.err kernel: EXT4-fs (hda7): error loading journal
That is the moment where the careful layman gives up.
Offline
After this result, not being able to mount an ext4-Parition on that laptop, I went back to the USB-stick issue. I made a new partition /dev/sda1 on the stick and formated it under Slitaz with mkfs.ext4 (with the new e2fsprog installed). Then I tried to mount it.
But I got again the same error message:
kernel: EXT4-fs (sda1): couldn't mount RDWR because of unsupported optional features (400)
Then I exited Slitaz, fired up a Debian9 distro on the laptop and formated it again. Mounted it there without a problem. Wrote a test.txt file on it. Took this stick to another PC with Debian 9, and voila: it could be mounted and the test.txt-file could be opened and a new line written into it.
Now again I am at a point where where the careful layman - cannot help! ;-)
Specifically: how to get an e2fsprog on Slitaz that can recognize the feature of the ext4-filsystem done under Debian.
Offline
Ok,, a further look:
http://e2fsprogs.sourceforge.net/
Release 1.44.5 of e2fsprogs is available!
I am happy to announce a new release of the e2fsprogs distribution. All users of e2fsprogs are urged to upgrade to the 1.44.5 version as soon as possible, which can be downloaded from sourceforge or kernel.org.
http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.44.5
A pity that this is not a thing where I can offer any help. But one will understand that this situation (you create a filesystem with the newest e2fsprog on slitaz and this particular slitaz installation cannot mount this stick) is not sustainable.
Offline
@michaelbischof
Hi, on my old test confirm at ext4 grub are the limitations.
Read first this post, if it same bug.
http://forum.slitaz.org/topic/slitaz-fresh-install-boot-problem/page/2#post-46646
Offline
@gibor
Sorry, I am not a techie. Whether this is the same bug or not I do not know and did not learn it from reading. For me the situation is bad as I cannot use slitaz as my safety system on machines where the other installations are on ext4. But in general if one has a bit patience there is no unresolvable problem on Linux, except the hardware is damaged. A techie type pupil said once: Linux one can install on each coffee machine.
Offline
From answer of Bellard then
Grub4DOS. It includes EXT4 support.
But the legagy grub relies on BIOS/INT13 which can be limited to 500MB or 8GB with old BIOS
from your first topic on this thread
My problem is that it cannot recognize a USB-stick that has an ext4 filesystem.
Disk /dev/sda: 31.9 GB
31,9GB is more big of 500Mb or 8GB...
for confirm test installation on same disk but formatted on ext3
IMHO
Offline
@gibor
I did the following thing. I established on this 30 GB-stick a partition sdb1, 1 G size, on this slitaz. Formatted it with the ( e2fsprogs-1.44.2.tazpkg installed, on this 32-bit machine) as ext4. Then I established a 28 G size partition sdb2, formatted it exfat.
Trying to mount both (!) failed.
On the same 32-bit machine on Debian 9 both partitions were recognized and could be mounted and I could write there.
Attached to another PC, a 64-bit one, it was recognized and I could write on it.
So where this „bug“ sits, in the e2fsprog or in the slitaz grub, I do not know.
Ah, my slitaz on this machine is on ext3!
(@gibor: no, it has nothing to do with Grub as I speak of a slitaz 32-bit version which is on ext3 that is already booted! I worked on this partition!)
Offline
Now I booted a Slitaz 5 on a 64-bit machine. The above mentioned stick is now recognized, the ext4 partition could be recognized, the exfat-Partion not. But the programm exfat-utils was not yet installed. - Ext4-Debian partitions could be recognized and mounted as well.
@All: this seems to be a 32-bit problem then with slitaz and ext4, no?
Offline
Sorry guys, this is carnecal tuesday
- the content fits to it.
On a 64-bit slitaz I had created an ext4-filesystem on one partition and an exfat-filesystem on another on (30 GB USB-stick).
I changed to a 32-bit laptop. Made sure everything is updated, exfat-utils installed.
Then this stick was inserted.
Result:
the ext4-partition was recognized and could me mounted. The content was readable.
But the exfat-filesystem could not be mounted.
root@slitaz:/home/tux# mount -t exfat /dev/sdb2 /media/usbdisk/
mount: unknown filesystem type 'exfat'
So I made sure that on this 32-bit install the exfat-utils program is installed and did this:
root@slitaz:/home/tux# mkfs.exfat /dev/sdb2
mkexfatfs 1.3.0
Creating... done.
Flushing... done.
File system created successfully.
root@slitaz:/home/tux# mount /dev/sdb2 /media/usbdisk/
mount: unknown filesystem type 'exfat'
So it could not recognize its own product, so to say. There could be a problem with creating the file system or with reading the filesystem. To find it out I put this stick again on a 64-bit-slitaz-install (exfat-utils installed) and - it could not be recognized.
As said before: happened during carneval. ;-)
Offline
Install fuse-exfat, it's only on slitaz-5.0 repo.
root@slitaz:/home/tux# tazpkg info fuse-exfat
TazPkg information
================================================================================
Package : fuse-exfat
State : mirrored package
Version : 1.3.0
Category : base-system
Short desc : Full-featured exFAT file system implementation.
Depends : fuse
Web site : https://github.com/relan/exfat
Size : 52K/232K
================================================================================
Offline
Ok, thanks a big lot, @Mojo, as usual. But tomorrow!
It is a hard days night! ;-)
Funny:
I had a similar idea. When I inserted this stick under Debian 9 and mounted it I got this message:
root# mount /dev/sdc2 /media/michael/30gb.stick/
FUSE exfat 1.2.5
So I thought: aha, in addition to exfat-utils one needs a suitable version of FUSE.
Offline
Debian has exfat-fuse as recommended when installing exfat-utils.
I have auto installing recommended disabled to minimize the distro size.
[c]root@debian:/home/rj# apt-get install exfat-utils[/c]
[c]Reading package lists... Done[/c]
[c]Building dependency tree[/c]
[c]Reading state information... Done[/c]
[c]Recommended packages:[/c]
[c]exfat-fuse[/c]
[c]The following NEW packages will be installed:[/c]
[c]exfat-utils[/c]
[c]0 upgraded, 1 newly installed, 0 to remove and 15 not upgraded.[/c]
[c]Need to get 45.2 kB of archives.[/c]
[c]After this operation, 232 kB of additional disk space will be used.[/c]
[c]Get:1 http://mirror.clarkson.edu/debian sid/main amd64 exfat-utils amd64 1.3.0-1 [45.2 kB][/c]
[c]Fetched 45.2 kB in 0s (120 kB/s)[/c]
[c]Retrieving bug reports... Done[/c]
[c]Parsing Found/Fixed information... Done[/c]
[c]Selecting previously unselected package exfat-utils.[/c]
[c](Reading database ... 83587 files and directories currently installed.)[/c]
[c]Preparing to unpack .../exfat-utils_1.3.0-1_amd64.deb ...[/c]
[c]Unpacking exfat-utils (1.3.0-1) ...[/c]
[c]Setting up exfat-utils (1.3.0-1) ...[/c]
[c]Processing triggers for man-db (2.8.5-2) ...[/c]
Offline
Situation now on said 32-bit installation:
1. Does recognize the ext4-partition on this usb-stick
2. Does not recognize the exfat-partition on this stick
Error mounting /dev/sdb2 at /media/4ED5-92B7: Command-line `mount -t "exfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,namecase=0,errors=remount-ro" "/dev/sdb2" "/media/4ED5-92B7"' exited with non-zero exit status 32: mount: unknown filesystem type 'exfat'
But fuse-exfat is installed.
root@slitaz:/etc/init.d# tazpkg info fuse-exfat
TazPkg information
================================================================================
Package : fuse-exfat
State : installed package
Version : 1.3.0
Category : base-system
Short desc : Full-featured exFAT file system implementation.
Maintainer : pascal.bellard@slitaz.org
License : GPL3
Depends : fuse
Build deps : autoconf automake perl-getopt-long fuse-dev
Web site : https://github.com/relan/exfat
Size : 52K/232K
Hmmh...
If I try to make a new exfat-filesystem on this installation is seems to be ok but agait it cannot mount the self-created filesystem.
Offline
Status now: the ext4-problem is solved both on 64- and 34-bit slitaz. The exfat-problem is not solved but I leave it like this. Not that much important, would be only pure sport to go on. I can live with formatting my usb sticks with vfat.
Thanks for your patience!
Michael
Offline
Updated to exfat-utils-1.0.3 which includes mount.exfat and mount.exfat-fuse which works now.
Will be removing fuse-exfat as all files are duplicated in exfat-utils.
Remove fuse-exfat and exfat-utils-1.0.0 prior to installing exfat-utils-1.0.3.tazpkg to prevent any potential conflicts.
Offline
What shall I say? Thanks and perfect as usual! Works now, of course.
Have a splendid weekend,
Michael
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]