I'm attempting to get an SD card to mount on boot for permanent storage and I'm pretty sure I screwed it up. This is my first time with Linux and I'm not a programmer. I've never even partitioned anything before.
I'm running Lubuntu 22.04 on a Chromebook, which came with a 16gb eMMC drive.
After doing some research, I mounted my SD to root (which I assume is where I went wrong):
sudo mount /dev/mmcblk1p1 /
Then I got into /etc/fstab and added the following (with the appropriate whitespace and an extra newline at the bottom):
/dev/mmcblk1p1 / ext2 defaults 0 0
Things seemed fine.
However! Before I remounted the SD, running df -h ~ showed this:
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 15G 14G 0 100% /
Similarly, df -h showed all the usual drives, including both mmcblk0p2 (the eMMC) and mmcblk1p1 (the SD).
Imagine my horror when, after mounting the SD to root, I check df -h ~ and it shows me this:
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk1p1 15G 14G 0 100% /
mmcblk1p1 has 128gb.
mmcblk0p2 has also disappeared from the df -h result.
So, how badly did I mess this up? Is there a way to fix this?
mountat/?? That would cause your existing/to be shadowed and thus effects from that point would I'd expect to be flaky (had you prepared for this??).... so your approach either strikes me as wrong, or I'm missing something in what you're trying to do. Is your Lubuntu installed? or are you trying tomountin order to install it as your provided details seem wrong to me.echo $HOMEin a terminal to see what I mean) for a GUI session to start & operate, if you have insufficient space you won't get past the greeter (ie.sddmfor Lubuntu)... but you will be able to login & work at terminal. If your system is booted & running, do not cause that file-system to be shadowed (ie. yoursudo mount /dev/mmcblk1p1 /could be risky/dangerous if you were booted & thus your system already had/mounted.. results after that command maybe untrustworthy unless you cleared caches etc.. or get corrupted