>
> > Thinking this would be simple, I removed
> BE_disk2_slice4 and rebooted.
> > I did get messages that update_archive couldn't be
> written to BE_disk1_slice0 on going down.
> > Perhaps that is why on the reboot, I find I am in
> the same spot?
>
> When you say reboot, I presume you mean init
> Thinking this would be simple, I removed BE_disk2_slice4 and rebooted.
> I did get messages that update_archive couldn't be written to BE_disk1_slice0
> on going down.
> Perhaps that is why on the reboot, I find I am in the same spot?
When you say reboot, I presume you mean init 0 or init 6 an
Bob,
thanks for your reply.
>
> > In this state, I cannot lumount disk2_slice4. It is
> busy. That also makes sense based on the
> > lustatus output but how do I get this straightened
> out?
> >
> Did you luactivate the boot environment or just add a
> grub menu entry for
> it ?
I used luac
In this state, I cannot lumount disk2_slice4. It is busy. That also makes sense
based on the
lustatus output but how do I get this straightened out?
Did you luactivate the boot environment or just add a grub menu entry for
it ?
I'm reasonably sure the problem is caused by my grub menu, bu
I have two disk drives. The original 250G drive is "disk2", because it
installed as c2d0. I have a build 79 lu on slice4 and older builds on slices 0
and 3. I have build 101 on disk1.
disk2 is a 250G drive
disk1 is a 500G drive
I select the lu on the 500G drive disk1 from my grub menu and
