You are not logged in.
sda1 = /boot (formatted as ext4)
sda2 = / (formatted as f2fs)
I need to somehow pass the -t f2fs to the
mount command as the initramfs is loading. Any ideas?
http://i1122.photobucket.com/albums/l53 … 3d9ff3.jpg
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by na5m (2013-06-25 07:34:36)
Let's go check out Hades!
Offline
Oops! Thanks for fixing my faux pas, mod.
falconindy: the initramfs fully loads successfully. From the emergency shell,
I'm able to use the mount command and successfully mount sda2 onto /
Question is, how can I address the problem mentioned by mount
when the loading of initramfs is non-interactive?
Let's go check out Hades!
Offline
Not sure if this is what falconindy is referring to, but on the kernel command line it might help to specify the filesystem type.
Offline
Perhaps give wipefs(8) a try?
Offline
Perhaps give wipefs(8) a try?
Do you know what wipefs does? That is definitely not what the OP wants to do here.
Offline
Yes, I do know what wipefs does; I gave the man page a read since I didn't know beforehand.
If his partition indeed contains several signatures, then it would be advisable to remove the false one(s).
Offline
So I fail to understand how making the filesystem invisible is going to help mount it.
Offline
If the case is that, in addition to a valid f2fs signature, there's also some other filesystem signature left over from previous use, that can confuse mount.
So, if there are ext4, xfs, btrfs, ntfs etc. signatures on the partition, it would be advisable to remove them.
Offline
Agreed with falconindy and cedeel. It's worth mentioning that, despite it's scary name, wipefs doesn't do anything the the filesystem by default.
# wipefs /dev/sda2
will simply show you what filesystems the partition identifies as, including the offset of their signatures. It's a simple matter of then using wipefs with the -o flag and the offset to remove the offending signature.
Of course, it's always a good idea to back up any important/irreplaceable data before messing with partitions.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
you have f2fs-tools and f2fs in the MODULES in the /etc/mkinitcpio.conf and rebuilding the initramfs and rotfs=f2fs in the bootloader options??
Well, I suppose that this is somekind of signature, no?
Offline
Thanks everyone. wipefs was the fix.
Linux was telling me what the solution
was, but was too blind to see (and more than a little scared
of a command named wipefs)
Arch boots like a charm now.
http://i1122.photobucket.com/albums/l53 … 9bfd65.jpg
wipefs -f -o 0x10040 /dev/sda2 did the trick.
I had to use -f because the sda2 was mounted.
Funny thing is now that I'm in Arch proper, when I run
wipefs, the btrfs entry still shows up, but with a different
offset. No big deal, I guess. I'm just happy that I can
boot into Arch.
http://i1122.photobucket.com/albums/l53 … 1599ae.jpg
We can mark this thread as solved. Thanks again, everyone.
Let's go check out Hades!
Offline