You have to pay more attention when you execute commands.
You have created mountpoints at /tmp/mnt/sda1 but then you tried to mount the partition at /mnt/sda1. This cannot work.
The error should be obvious to you.
Code:
mkdir -p /tmp/mnt/sda1
mount -t ext4 /dev/sda1 /tmp/mnt/sda1
This should work.
If not check with lsmod if the ext4 module is loaded. It should when you activate USB Storage Support under Services -> USB
I noticed that if I enable automount the ext4 module is loaded and visible in lsmod.
Loading the module with the mobprobe ext4 command solved the problem! I was able to mount the drive correctly. My question is, why do I have to manually load the module at every boot?
To be honest, I have been running my router with 3 drives attached to it in a LVM setup for more then 10 years.
I have always loaded the modules manually via Startup. Back then it was necessary, I guess.
My own routine checks if the modules I need are already loaded and only loads them if they are not found.
Code:
for MODULE in mbcache crc16 jbd2 ext4 dm-mod; do
[ $(lsmod |grep -c $MODULE) -eq 0 ] && insmod $MODULE; done
This doesn't look like a UUID to me. Check again with blkid.
You can use the whole UUID or simply a small but significant/uniqe part of it.
I myself use the last part after the last dash "-". It is sufficient.
If you want to work with the fs-label, you can use this routine instead:
Glad to see your issues resolved.
You could get yourself more familiar with scripting and align all sorts of stuff to better fit your needs. It is not difficult and it gets you in the position to really get stuff going, if needed.
