Hello, I previously did a pacman -Syu and noticed there was a 66-tools update. Well I'm am just now seeing this so I did not do a 66-update before I shutdown this morning. Now upon boot I am getting 
66-init: fatal: unable to copy earlier service /var/lib/66/system/boot/servicedirs/svc/tty12 to: boot: Read-only file system
Give root password for maintenance
(or press Control-D to continue):
On one of my Obarun installs I can enter root password and I get 
archlinux#
The other neither root password nor control-d do anything. Is there a process I can do to remedy any of this?
Thank you
The other neither root password nor control-d do anything
This is surprising. Do you are sure to enter the correct password? I mean by default the keyboard keymap should be in english(i think).

Anyway if you can enter root password and you get the prompt, first remount the / to rw 
# mount -o remount,rw /
now try to update with 66-update
then reboot and don't forget to update your user trees before trying to launch your X session.

If you're not able to get the prompt of the sulogin , you need to first boot on a ISO and chroot your system. Then try to run a 66-update command inside the chroot.
Booted up this morning, ran -Syu and backed up.

On reboot, startup stalled at [start stage1 ...

Rolled back previous backup (Apr 28 11:45am edt) and successfully rebooted.

Again ran -Syu (but have a nagging feeling the number of updates were far less than I remember..).

On reboot, startup stalled at [start stage1 ...

Sorry, but I'm a geriatric noob....
@ jbkeh
rollback and reboot
now update the 66 package, then as root 
# 66-update -d
this make a dry-run update, meaning nothing is changed on your system. So no error showed? then make a real update. 
# 66-update
do the same with regular user.
reboot
@ Eric
Many thanks.
Five minutes well spent.
@ eric

Just a final update as I subsequently locked up yet again...

Full sequence:

1. Roll back to last bootable state.
2. Execute sudo pacman -Syu.
3. DO NOT REBOOT.
4. As root, execute 66-update -d, ensure successful.
5. As root, execute 66-update, ensure successful.
6. As prime user, repeat steps 4 & 5.
7. Cross fingers & REBOOT
8. BACKUP!
i repeat again:

The 66-update -d do not really update your system. You MUST run the 66-update tool without the -d options to really update your system.
So:
66-update -d check if the real future update will go right.
66-update really update your system.

If the 66-update -d command finish successfully you don't need to cross your fingers. The real update will go right and you will get the exact same machine state as previously.

66-update allow you to have a safe update and you should guarantee you to have an operational boot.
jbkeh wrote@ eric

Just a final update as I subsequently locked up yet again...

Full sequence:

1. Roll back to last bootable state.
2. Execute sudo pacman -Syu.
3. DO NOT REBOOT.
4. As root, execute 66-update -d, ensure successful.
5. As root, execute 66-update, ensure successful.
6. As prime user, repeat steps 4 & 5.
7. Cross fingers & REBOOT
8. BACKUP!
Thank you!
But what do you mean with Backup?
The whole System?
The settings?
eric wrote now try to update with 66-update
then reboot and don't forget to update your user trees before trying to launch your X session.

If you're not able to get the prompt of the sulogin , you need to first boot on a ISO and chroot your system. Then try to run a 66-update command inside the chroot.
Thanks for the instruction. With everything I tried I could not get either install to boot.
I did a reinstall on one machine with the newest image "obarun-2020.03.01-x86_64.iso" and it hangs at 
ObarunX login: trying to run a sulogin command
Give root password for maintenance
(or press control-D to continue):
I also tried a fresh installl with the newest image on a Vbox and got the same result.
I'm not having much luck at the moment. any help would be appreciated
Thanks
From live or another installation chroot and run "66-update -v4 -d" copy the output here

Say the installation is at /dev/sda13 
mount /dev/sda13 /mnt
arch-chroot /mnt zsh
66-update -v4 -d >/root/66-up.output
The output is at /root/66-up.output or from another terminal in live it would be /mnt/root/66-up.output, before you exit the chroot copy that file here so we can see what is wrong.
Hello fungalnet.. As far as fixing my installation I think that is above my head. also I have tried a totally fresh virtualbox install with the latest image
"obarun-2020.03.01-x86_64.iso" 3 times end each time the boot hangs at 
Ob66 login: trying to run a sulogin command
Give root password for maintenance
(or press control-D to continue):
My installation process is the same I have used successfully tens of times so I'm assuming there is a problem with the installation image.
I have switched my main machine back to Arch for the time being. I will give Obarun another spin if the problem gets sorted out. Thanks
@ sticksix
Your report surprise me a lot. Please consider to answer of the following questions:
Which templates do you try to install?
Do you have a successful installation or you got some errors?
Do you have the tty12 running or not?
If you have the tty12 running, please post the content of /run/66/log/0/current file?
@ eric

I've tried to install plasma on an actual machine and several times in virtualbox with no success.
The installation appears to be successful. I see no errors except I can see what looks like something written in red for just an instant before it takes me to the screen where you choose host, locale, user, etc. but when the installation is complete it says success. not sure what you mean by tty12 running? do you mean a terminal? I can enter root password but it is very erratic skipping sometimes and not letting me complete password before it asks for the password again before it finally accepts password.
Not sure what the problem is. As I've said this happens each time I install. My method for install is the same that has worked many times. Should I try a different desktop? XFCE??
@ igorka67

By BACKUP I meant whatever/however you create a rollback capability.

(And the "cross your fingers" was merely a comment on human nature, not an expression of any doubt.)
@ jbkeh
:D :D :D
I am not able to create a rollback capability.
I thought this changes just the kernel in use. I'll do some research...
Anyway by me worked the 
# mount -o remount,rw /
system.
Ctrl-Shift F1-F12 gets you to tty1-tty12, so ctrl-shift F12 is tty12

On tty12 you can only login as user, not as root. If you have tty12 active that means the boot part was a success, the transition to root tree (or whatever tree you have as current and enabled) is having an issue. But unless you can copy here what the outputs of very basic commands are like /run/66/.....current and the output of 66-intree I don't think anyone can help you diagnose the problem.
I can enter root password but it is very erratic skipping sometimes and not letting me complete password before it asks for the password again before it finally accepts password.
I'm not sure to understand what you mean...

If you are able to log with root at sulogin prompt, first do: 
# mount -o remount,rw /
this will remount your root partition with read/write permissions
now, check if you have the boot tree 
# 66-intree
if you have it do 
# 66-enable -t boot -F boot
if you don't have it 
# 66-tree -n boot
# 66-enable -t boot boot
with the previous command of 66-intree check if you have the root tree
if not 
# 66-tree -cnE root
# 66-enable tty@ tty1 tty@ tty2
if you have it 
# 66-enable -F -t root tty@ tty1 tty@ tty2
reboot with 
# reboot -f
obviously i don't know what you has inside of your root tree and if you have other tree than the root tree. But you get the point.
lets us know if you get a operational machine or not.
Could this be hw related, where something set to use this delaying hw is taking so long to respond that emergency comes up, meanwhile while you have # emergency prompt the tty1 is kicking in and a return takes you to a password promt. If you see the actual prompt : 
password:
then tty1 is activated.

Is there a remote/external disk, cd/dvd, ssd, part of the system? Either automount or /etc/fstab may have something that is too slow in response to be checked.

How do you do the installation? With a usb stick of cd? Maybe the location of that disk is passed into /etc/fstab and then it is not found which causes the problem?
@ eric

I tried another totally new install on virtualbox with latest "obarun-2020.03.01-x86_64.iso" and get the same result stuck at sulogin. Entries with keyboard still have errors. for instance if I type user name "obarun" it may only see the letters "ob" then it errors out. after several attempts I was able to enter root password and I ran through all commands successfully up to "reboot -f". After reboot it is still stuck at sulogin.

Powered by Obarun