I am trying to get additional mounts working. I am using 1.1.1
ros os version v1.1.1
I set extra mounts using
ros config set mounts '[["/dev/vdb","/opt/default","ext4"],["/dev/vdc","/opt/fast","ext4"]]'
And it looks like this
ros config get mounts - - /dev/vdb - /opt/default - ext4 - - /dev/vdc - /opt/fast - ext4
When i do not format the disks prior reboot, it reboots but nothing is mounted. If i format the disks using
mkfs.ext4 /dev/vdb mkfs.ext4 /dev/vdc
I can mount them properly using
mount /dev/vdb /opt/default mount /dev/vdc /opt/fast
The boot stucks at
[ 17.266437] docker-sys: port 1(vethfafdb7be) entered blocking state [ 17.267653] docker-sys: port 1(vethfafdb7be) entered forwarding state [ ] ros-sysinit:info: [18/18] [preload-user-images]: Started [ ] ros-sysinit:info: [3/4] Starting sync [ ] ros-sysinit:info: Project [os]: Project started [ ] ros-sysinit:info: [4/4] Starting banner [ ] ros-sysinit:info: RancherOS v1.1.1 started
Interestingly not even the
ttyS0 autologin console does work in this case. It does work if
recovery console is selected in
grub and it does work if the system actually boots, the autologin works on
That said, i cannot really retrieve any logs for further analysis and i cannot really see the docs http://rancher.com/docs/os/v1.1/en/storage/additional-mounts/ being of any help.
So concrete questions are
- Do i need / have to format the disk being mounted prior defining the mounts in rancher ( to have them working )?
- If yes, why does the system stalls on boot?
- (thats kind of a offtopic here, but interesting for analysis for the actual problem): Why is autologin not working at all, does the consol not start up ( ssh is not working either, but that is what i expected ).