zram mount error #11
Comments
|
Linux 4.13-rc5 works fine, so perhaps it is a problem with Liquorix. |
|
Okay, so can I close this issue? |
|
I would at least like to know why the problem occurred, entering the kill-ryzen script manually into the terminal didn't reveal anything and I didn't see anything in dmesg to indicate what the problem is. Linux 4.12-rc7 also works, so almost certainly a Liquorix specific thing. |
|
Which interpreter do you use? |
|
Bash 4.4-5. I am using Debian Sid. My guess would be Liquorix has changed Zram settings or virtual filesystem settings or something in such a way that the script fails. Just to be clear, Liquorix is a kernel optimized for desktop use: |
|
Looking at the kill-ryzen.sh script, the mounting error occurs because we're mounting a ram disk with "discard" option. Discard isn't supported on devices that don't support ATA_TRIM, e.g., ram disks. Why Ubuntu's kernel allows you to mount ram disks with discard is a mystery in itself. Perhaps the discard option itself is ignored silently for compatibility reasons? |
Discard should only be enabled for block devices that expose ATA_TRIM, such as SSDs. Ram disks don't and shouldn't expose ATA_TRIM, and don't suffer from wear the same way SSDs do. Fixes: suaefar#11
Discard should only be enabled for block devices that expose ATA_TRIM, such as SSDs. Ram disks don't and shouldn't expose ATA_TRIM, and don't suffer from wear the same way SSDs do. Closes suaefar#11
The command 'mke2fs' can have different results depending on the configuration of /etc/mke2fs.conf. If an ext2 or ext3 filesystem is created, mount with "-o discard" will fail. Use standard mkfs.ext4 command available on all distributions to eliminate potential variation in resulting filesystem. Per Arch's wiki, ext4 supports continuous fstrim while ext3 does not: https://wiki.archlinux.org/index.php/Solid_State_Drives#TRIM Closes suaefar#11
The command 'mke2fs' can have different results depending on the configuration of /etc/mke2fs.conf. If an ext2 or ext3 filesystem is created, mount with "-o discard" will fail. Use standard mkfs.ext4 command available on all distributions to eliminate potential variation in resulting filesystem. Per Arch's wiki, ext4 supports continuous fstrim while ext3 does not: https://wiki.archlinux.org/index.php/Solid_State_Drives#TRIM Closes suaefar#11
The command 'mke2fs' can have different results depending on the configuration of /etc/mke2fs.conf. If an ext2 or ext3 filesystem is created, mount with "-o discard" will fail. Use standard mkfs.ext4 command available on all distributions to eliminate potential variation in resulting filesystem. Per Arch's wiki, ext4 supports continuous fstrim while ext3 does not: https://wiki.archlinux.org/index.php/Solid_State_Drives#TRIM Closes suaefar#11
The command 'mke2fs' can have different results depending on the configuration of /etc/mke2fs.conf. If an ext2 or ext3 filesystem is created, mount with "-o discard" will fail. Use standard mkfs.ext4 command available on all distributions to eliminate potential variation in resulting filesystem. Per Arch's wiki, ext4 supports continuous fstrim while ext3 does not: https://wiki.archlinux.org/index.php/Solid_State_Drives#TRIM Closes #11
Using the latest GIT version I get this in the terminal:
$ ./kill-ryzen.sh
Install required packages
[sudo] password for keantoken:
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.3).
0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
Create compressed ramdisk
64G
mount: wrong fs type, bad option, bad superblock on /dev/zram0,
missing codepage or helper program, or other error
The text was updated successfully, but these errors were encountered: