How should I convert ext4 to F2FS for main system usage?How To Make Use Of F2FS?How to format my pendrive...
Multiplication via squaring and addition
Most significant research articles for practical investors with research perspectives
It took me a lot of time to make this, pls like. (YouTube Comments #1)
A "strange" unit radio astronomy
If nine coins are tossed, what is the probability that the number of heads is even?
How to acknowledge an embarrassing job interview, now that I work directly with the interviewer?
Can you use a beast's innate abilities while polymorphed?
Non-Italian European mafias in USA?
Contradiction with Banach Fixed Point Theorem
What is the difference between throw e and throw new Exception(e)?
What is the wife of a henpecked husband called?
Can I become debt free or should I file for bankruptcy? How do I manage my debt and finances?
Is my plan for fixing my water heater leak bad?
What is the difference between ashamed and shamed?
What's the difference between a cart and a wagon?
Easy code troubleshooting in wordpress
What to do when being responsible for data protection in your lab, yet advice is ignored?
What can I substitute for soda pop in a sweet pork recipe?
How to add multiple differently colored borders around a node?
Use comma instead of & in table
What is better: yes / no radio, or simple checkbox?
Why do members of Congress in committee hearings ask witnesses the same question multiple times?
Auto Insert date into Notepad
Where is the fallacy here?
How should I convert ext4 to F2FS for main system usage?
How To Make Use Of F2FS?How to format my pendrive with f2fs filsystem using gparted?F2FS is being displayed as an “Unknown” file system after formatting my pendrive. Does anyone know the reason behind this?How To Enable Disk Encryption For F2FS Formatted Drives?
Below is what I've tried, but any solution is welcome.
I'm doing this in VirtualBox-6.0 (static size VHDs) before doing it live which may be a factor.
I've edited an ISO with cubic, removing packages and running apt install f2fs* -f -y
so I'd be able to format partitions into F2FS from live CD. Kubuntu, the OS I want to use, uses Ubiquity to install the system which isn't able to read F2FS. A solution could be to find an installer that can read F2FS but I don't know any.
So what I've done instead is made a 512mb EFI boot partition and two separate ext4 partitions for root and home, intending to convert home to F2FS. The root/home separation was because I believe less things would break.
I installed as ext4, confirmed system running, then used Clonezilla to copy home to a separate partition. I then rebooted into a live CD to format the home partition to F2FS then copy over the folders located in home.
Now the problem: it shows the splash but systemctl --failed | grep not-found
outputs:
tmp.mount
auditd.service
connman.service
console-screen.service
-screen.service
kbd.service
systemd-sysusers.service
systemd-update-done.service
update-done.service
systemd-vconsole-setup.service
-vconsole-setup.service
all.target
syslog.target
And notable output from journalctl -xb
is MODSIGN: Couldn't get UEFI db list
.
I went back into live CD, chrooted and updated. Errors were encountered while processing:
ca-certificates-java
grub-pc
openjdk-11-jre-headless:amd64
grub-efi-amd-signed
openjdk-11-jre:amd64
shim-sgned
friendly-recovery
linux-image-4.15.0-45-generic
Probably because:
update-initramfs: Generating (the kernel)
Warning:couldn't identify filesystem type for fsck hook, ignoring
Attempting install returns E: Internal Error. No file name for [the packages I checked]
. I am assuming F2FS is only supported for data storage with this line
f2fs
add a comment |
Below is what I've tried, but any solution is welcome.
I'm doing this in VirtualBox-6.0 (static size VHDs) before doing it live which may be a factor.
I've edited an ISO with cubic, removing packages and running apt install f2fs* -f -y
so I'd be able to format partitions into F2FS from live CD. Kubuntu, the OS I want to use, uses Ubiquity to install the system which isn't able to read F2FS. A solution could be to find an installer that can read F2FS but I don't know any.
So what I've done instead is made a 512mb EFI boot partition and two separate ext4 partitions for root and home, intending to convert home to F2FS. The root/home separation was because I believe less things would break.
I installed as ext4, confirmed system running, then used Clonezilla to copy home to a separate partition. I then rebooted into a live CD to format the home partition to F2FS then copy over the folders located in home.
Now the problem: it shows the splash but systemctl --failed | grep not-found
outputs:
tmp.mount
auditd.service
connman.service
console-screen.service
-screen.service
kbd.service
systemd-sysusers.service
systemd-update-done.service
update-done.service
systemd-vconsole-setup.service
-vconsole-setup.service
all.target
syslog.target
And notable output from journalctl -xb
is MODSIGN: Couldn't get UEFI db list
.
I went back into live CD, chrooted and updated. Errors were encountered while processing:
ca-certificates-java
grub-pc
openjdk-11-jre-headless:amd64
grub-efi-amd-signed
openjdk-11-jre:amd64
shim-sgned
friendly-recovery
linux-image-4.15.0-45-generic
Probably because:
update-initramfs: Generating (the kernel)
Warning:couldn't identify filesystem type for fsck hook, ignoring
Attempting install returns E: Internal Error. No file name for [the packages I checked]
. I am assuming F2FS is only supported for data storage with this line
f2fs
add a comment |
Below is what I've tried, but any solution is welcome.
I'm doing this in VirtualBox-6.0 (static size VHDs) before doing it live which may be a factor.
I've edited an ISO with cubic, removing packages and running apt install f2fs* -f -y
so I'd be able to format partitions into F2FS from live CD. Kubuntu, the OS I want to use, uses Ubiquity to install the system which isn't able to read F2FS. A solution could be to find an installer that can read F2FS but I don't know any.
So what I've done instead is made a 512mb EFI boot partition and two separate ext4 partitions for root and home, intending to convert home to F2FS. The root/home separation was because I believe less things would break.
I installed as ext4, confirmed system running, then used Clonezilla to copy home to a separate partition. I then rebooted into a live CD to format the home partition to F2FS then copy over the folders located in home.
Now the problem: it shows the splash but systemctl --failed | grep not-found
outputs:
tmp.mount
auditd.service
connman.service
console-screen.service
-screen.service
kbd.service
systemd-sysusers.service
systemd-update-done.service
update-done.service
systemd-vconsole-setup.service
-vconsole-setup.service
all.target
syslog.target
And notable output from journalctl -xb
is MODSIGN: Couldn't get UEFI db list
.
I went back into live CD, chrooted and updated. Errors were encountered while processing:
ca-certificates-java
grub-pc
openjdk-11-jre-headless:amd64
grub-efi-amd-signed
openjdk-11-jre:amd64
shim-sgned
friendly-recovery
linux-image-4.15.0-45-generic
Probably because:
update-initramfs: Generating (the kernel)
Warning:couldn't identify filesystem type for fsck hook, ignoring
Attempting install returns E: Internal Error. No file name for [the packages I checked]
. I am assuming F2FS is only supported for data storage with this line
f2fs
Below is what I've tried, but any solution is welcome.
I'm doing this in VirtualBox-6.0 (static size VHDs) before doing it live which may be a factor.
I've edited an ISO with cubic, removing packages and running apt install f2fs* -f -y
so I'd be able to format partitions into F2FS from live CD. Kubuntu, the OS I want to use, uses Ubiquity to install the system which isn't able to read F2FS. A solution could be to find an installer that can read F2FS but I don't know any.
So what I've done instead is made a 512mb EFI boot partition and two separate ext4 partitions for root and home, intending to convert home to F2FS. The root/home separation was because I believe less things would break.
I installed as ext4, confirmed system running, then used Clonezilla to copy home to a separate partition. I then rebooted into a live CD to format the home partition to F2FS then copy over the folders located in home.
Now the problem: it shows the splash but systemctl --failed | grep not-found
outputs:
tmp.mount
auditd.service
connman.service
console-screen.service
-screen.service
kbd.service
systemd-sysusers.service
systemd-update-done.service
update-done.service
systemd-vconsole-setup.service
-vconsole-setup.service
all.target
syslog.target
And notable output from journalctl -xb
is MODSIGN: Couldn't get UEFI db list
.
I went back into live CD, chrooted and updated. Errors were encountered while processing:
ca-certificates-java
grub-pc
openjdk-11-jre-headless:amd64
grub-efi-amd-signed
openjdk-11-jre:amd64
shim-sgned
friendly-recovery
linux-image-4.15.0-45-generic
Probably because:
update-initramfs: Generating (the kernel)
Warning:couldn't identify filesystem type for fsck hook, ignoring
Attempting install returns E: Internal Error. No file name for [the packages I checked]
. I am assuming F2FS is only supported for data storage with this line
f2fs
f2fs
edited Feb 18 at 3:27
Olorin
2,467924
2,467924
asked Feb 18 at 2:54
avisitoritseemsavisitoritseems
10110
10110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I took the shotgun approach + ended up choosing a distribution that uses Calamares as its installer. I partitioned the /usr as ext4 because GRUB's files are located there and I kept running into issues with /usr as F2FS (didn't retain permissions if copied to F2FS part, unreadable by system, couldn't boot, f2fs-tools is located in /usr)
/boot/efi - FAT32
/usr - ext4
/ - F2FS
apt commands in the extracted ISO. Installed F2FS libraries so the system could read itself, gparted for convenience and to set ESP flag for boot partition
apt install f2fs* libf2fs* gparted
I tried using kvpm to create logical volumes (and used mkfs.f2fs to format them as f2fs) but installation would fail.
List of modules loaded in /etc/initramfs-tools/modules
crct10dif_pclmul
crc32_pclmul
libcrc32c
f2fs
Post installation:
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot/efi
mount --bind /dev /mnt/dev
. . .
chroot /mnt
apt install refind
refind-install
cp /usr/share/refind/refind/drivers_x64 /boot/efi
curl -a http://efi.akeo.ie/downloads/efifs-1.3/x64/f2fs_x64.efi -o /boot/efi/EFI/refind/drivers_x64/f2fs_x64.efi
For the sake of information, GRUB 2.04 is right around the corner. I now understand why there is little discussion on F2FS installations for Ubuntu. Things that failed:
Running the whole drive as F2FS with a FAT32 boot partition failed to load OS
Copying an ext partition to F2FS failed. GRUB 2.02 can't read F2FS UUIDs properly. Editing /boot/grub/grub.cfg to change labels to UUIDs did not help.
Built the current branch of GRUB 2.03 and was hit with a fail when running
make check TESTS='f2fs_test'
; the list of dependencies is incomplete for novices (me).Partitioning root as ext4, then the rest as F2FS. GRUB's files are located in /usr.
Tried formatting boot as NTFS to retain the ability to dual boot Windows and symlink GRUB's needed files (FAT32 can't). This did not work because NTFS is not respected as a ESP partition, flags irregardless.
References:
https://ubuntuforums.org/showthread.php?t=2326934&p=13705533#post13705533
https://github.com/void-linux/void-packages/issues/4436
http://www.rodsbooks.com/refind/
http://efi.akeo.ie/
https://www.phoronix.com/scan.php?page=news_item&px=GRUB-Now-Supports-F2FS
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119109%2fhow-should-i-convert-ext4-to-f2fs-for-main-system-usage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I took the shotgun approach + ended up choosing a distribution that uses Calamares as its installer. I partitioned the /usr as ext4 because GRUB's files are located there and I kept running into issues with /usr as F2FS (didn't retain permissions if copied to F2FS part, unreadable by system, couldn't boot, f2fs-tools is located in /usr)
/boot/efi - FAT32
/usr - ext4
/ - F2FS
apt commands in the extracted ISO. Installed F2FS libraries so the system could read itself, gparted for convenience and to set ESP flag for boot partition
apt install f2fs* libf2fs* gparted
I tried using kvpm to create logical volumes (and used mkfs.f2fs to format them as f2fs) but installation would fail.
List of modules loaded in /etc/initramfs-tools/modules
crct10dif_pclmul
crc32_pclmul
libcrc32c
f2fs
Post installation:
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot/efi
mount --bind /dev /mnt/dev
. . .
chroot /mnt
apt install refind
refind-install
cp /usr/share/refind/refind/drivers_x64 /boot/efi
curl -a http://efi.akeo.ie/downloads/efifs-1.3/x64/f2fs_x64.efi -o /boot/efi/EFI/refind/drivers_x64/f2fs_x64.efi
For the sake of information, GRUB 2.04 is right around the corner. I now understand why there is little discussion on F2FS installations for Ubuntu. Things that failed:
Running the whole drive as F2FS with a FAT32 boot partition failed to load OS
Copying an ext partition to F2FS failed. GRUB 2.02 can't read F2FS UUIDs properly. Editing /boot/grub/grub.cfg to change labels to UUIDs did not help.
Built the current branch of GRUB 2.03 and was hit with a fail when running
make check TESTS='f2fs_test'
; the list of dependencies is incomplete for novices (me).Partitioning root as ext4, then the rest as F2FS. GRUB's files are located in /usr.
Tried formatting boot as NTFS to retain the ability to dual boot Windows and symlink GRUB's needed files (FAT32 can't). This did not work because NTFS is not respected as a ESP partition, flags irregardless.
References:
https://ubuntuforums.org/showthread.php?t=2326934&p=13705533#post13705533
https://github.com/void-linux/void-packages/issues/4436
http://www.rodsbooks.com/refind/
http://efi.akeo.ie/
https://www.phoronix.com/scan.php?page=news_item&px=GRUB-Now-Supports-F2FS
add a comment |
I took the shotgun approach + ended up choosing a distribution that uses Calamares as its installer. I partitioned the /usr as ext4 because GRUB's files are located there and I kept running into issues with /usr as F2FS (didn't retain permissions if copied to F2FS part, unreadable by system, couldn't boot, f2fs-tools is located in /usr)
/boot/efi - FAT32
/usr - ext4
/ - F2FS
apt commands in the extracted ISO. Installed F2FS libraries so the system could read itself, gparted for convenience and to set ESP flag for boot partition
apt install f2fs* libf2fs* gparted
I tried using kvpm to create logical volumes (and used mkfs.f2fs to format them as f2fs) but installation would fail.
List of modules loaded in /etc/initramfs-tools/modules
crct10dif_pclmul
crc32_pclmul
libcrc32c
f2fs
Post installation:
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot/efi
mount --bind /dev /mnt/dev
. . .
chroot /mnt
apt install refind
refind-install
cp /usr/share/refind/refind/drivers_x64 /boot/efi
curl -a http://efi.akeo.ie/downloads/efifs-1.3/x64/f2fs_x64.efi -o /boot/efi/EFI/refind/drivers_x64/f2fs_x64.efi
For the sake of information, GRUB 2.04 is right around the corner. I now understand why there is little discussion on F2FS installations for Ubuntu. Things that failed:
Running the whole drive as F2FS with a FAT32 boot partition failed to load OS
Copying an ext partition to F2FS failed. GRUB 2.02 can't read F2FS UUIDs properly. Editing /boot/grub/grub.cfg to change labels to UUIDs did not help.
Built the current branch of GRUB 2.03 and was hit with a fail when running
make check TESTS='f2fs_test'
; the list of dependencies is incomplete for novices (me).Partitioning root as ext4, then the rest as F2FS. GRUB's files are located in /usr.
Tried formatting boot as NTFS to retain the ability to dual boot Windows and symlink GRUB's needed files (FAT32 can't). This did not work because NTFS is not respected as a ESP partition, flags irregardless.
References:
https://ubuntuforums.org/showthread.php?t=2326934&p=13705533#post13705533
https://github.com/void-linux/void-packages/issues/4436
http://www.rodsbooks.com/refind/
http://efi.akeo.ie/
https://www.phoronix.com/scan.php?page=news_item&px=GRUB-Now-Supports-F2FS
add a comment |
I took the shotgun approach + ended up choosing a distribution that uses Calamares as its installer. I partitioned the /usr as ext4 because GRUB's files are located there and I kept running into issues with /usr as F2FS (didn't retain permissions if copied to F2FS part, unreadable by system, couldn't boot, f2fs-tools is located in /usr)
/boot/efi - FAT32
/usr - ext4
/ - F2FS
apt commands in the extracted ISO. Installed F2FS libraries so the system could read itself, gparted for convenience and to set ESP flag for boot partition
apt install f2fs* libf2fs* gparted
I tried using kvpm to create logical volumes (and used mkfs.f2fs to format them as f2fs) but installation would fail.
List of modules loaded in /etc/initramfs-tools/modules
crct10dif_pclmul
crc32_pclmul
libcrc32c
f2fs
Post installation:
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot/efi
mount --bind /dev /mnt/dev
. . .
chroot /mnt
apt install refind
refind-install
cp /usr/share/refind/refind/drivers_x64 /boot/efi
curl -a http://efi.akeo.ie/downloads/efifs-1.3/x64/f2fs_x64.efi -o /boot/efi/EFI/refind/drivers_x64/f2fs_x64.efi
For the sake of information, GRUB 2.04 is right around the corner. I now understand why there is little discussion on F2FS installations for Ubuntu. Things that failed:
Running the whole drive as F2FS with a FAT32 boot partition failed to load OS
Copying an ext partition to F2FS failed. GRUB 2.02 can't read F2FS UUIDs properly. Editing /boot/grub/grub.cfg to change labels to UUIDs did not help.
Built the current branch of GRUB 2.03 and was hit with a fail when running
make check TESTS='f2fs_test'
; the list of dependencies is incomplete for novices (me).Partitioning root as ext4, then the rest as F2FS. GRUB's files are located in /usr.
Tried formatting boot as NTFS to retain the ability to dual boot Windows and symlink GRUB's needed files (FAT32 can't). This did not work because NTFS is not respected as a ESP partition, flags irregardless.
References:
https://ubuntuforums.org/showthread.php?t=2326934&p=13705533#post13705533
https://github.com/void-linux/void-packages/issues/4436
http://www.rodsbooks.com/refind/
http://efi.akeo.ie/
https://www.phoronix.com/scan.php?page=news_item&px=GRUB-Now-Supports-F2FS
I took the shotgun approach + ended up choosing a distribution that uses Calamares as its installer. I partitioned the /usr as ext4 because GRUB's files are located there and I kept running into issues with /usr as F2FS (didn't retain permissions if copied to F2FS part, unreadable by system, couldn't boot, f2fs-tools is located in /usr)
/boot/efi - FAT32
/usr - ext4
/ - F2FS
apt commands in the extracted ISO. Installed F2FS libraries so the system could read itself, gparted for convenience and to set ESP flag for boot partition
apt install f2fs* libf2fs* gparted
I tried using kvpm to create logical volumes (and used mkfs.f2fs to format them as f2fs) but installation would fail.
List of modules loaded in /etc/initramfs-tools/modules
crct10dif_pclmul
crc32_pclmul
libcrc32c
f2fs
Post installation:
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot/efi
mount --bind /dev /mnt/dev
. . .
chroot /mnt
apt install refind
refind-install
cp /usr/share/refind/refind/drivers_x64 /boot/efi
curl -a http://efi.akeo.ie/downloads/efifs-1.3/x64/f2fs_x64.efi -o /boot/efi/EFI/refind/drivers_x64/f2fs_x64.efi
For the sake of information, GRUB 2.04 is right around the corner. I now understand why there is little discussion on F2FS installations for Ubuntu. Things that failed:
Running the whole drive as F2FS with a FAT32 boot partition failed to load OS
Copying an ext partition to F2FS failed. GRUB 2.02 can't read F2FS UUIDs properly. Editing /boot/grub/grub.cfg to change labels to UUIDs did not help.
Built the current branch of GRUB 2.03 and was hit with a fail when running
make check TESTS='f2fs_test'
; the list of dependencies is incomplete for novices (me).Partitioning root as ext4, then the rest as F2FS. GRUB's files are located in /usr.
Tried formatting boot as NTFS to retain the ability to dual boot Windows and symlink GRUB's needed files (FAT32 can't). This did not work because NTFS is not respected as a ESP partition, flags irregardless.
References:
https://ubuntuforums.org/showthread.php?t=2326934&p=13705533#post13705533
https://github.com/void-linux/void-packages/issues/4436
http://www.rodsbooks.com/refind/
http://efi.akeo.ie/
https://www.phoronix.com/scan.php?page=news_item&px=GRUB-Now-Supports-F2FS
edited 34 secs ago
answered 22 mins ago
avisitoritseemsavisitoritseems
10110
10110
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119109%2fhow-should-i-convert-ext4-to-f2fs-for-main-system-usage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown