You are not logged in.
Hi, I currently am running Arch on an SSD using F2FS, as I read that for this drive, it's better than ext4. I also have, however, an HDD that previously had my system, but I switched from it to the new SSD since it was showing signs of failure. I completely erased all data on it and reformatted it as a single ext4 partition. I can't seem to be able, though, to mount it. When adding the partition mount to fstab, my system booted into emergency mode, and when manually trying to mount it with:
sudo mount /dev/sda1 /media/sda-storage
I get the following errors from sudo dmesg:
[ 256.140471] F2FS-fs (sda): Magic Mismatch, valid(0xf2f52010) - read(0xfc63daf)
[ 256.140475] F2FS-fs (sda): Can't find valid F2FS filesystem in 1th superblock
[ 256.140607] F2FS-fs (sda): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 256.140608] F2FS-fs (sda): Can't find valid F2FS filesystem in 2th superblock
[ 256.140741] FAT-fs (sda): bogus number of reserved sectors
[ 256.140743] FAT-fs (sda): Can't find a valid FAT filesystem
I initially thought the drive itself was failing, but the errors don't point to that I think. So it seems like there's some kind of compatibility issue that I'm not sure how to solve, or if it is even solvable. I don't plan on wiping my SSD to make it ext4, and I'm not sure if f2fs for a hard disk drive is a good idea. What can I do?
Last edited by CLR123 (2024-07-29 02:36:08)
Offline
Please post your fstab.
If I understand you correctly, you're trying to boot the system while both the SSD (F2FS) and the HDD (ext4) are connected?
A journal from a failed boot might help, also.
Cheers,
"Before Enlightenment chop wood, carry water. After Enlightenment chop wood, carry water." -- Zen proverb
Offline
Oh I'm stupid. I put "default" in the options, instead of "defaults", lol. I still don't understand why the partition couldn't be manually mounted, but oh well... It works now haha.
Offline