https://bugzilla.novell.com/show_bug.cgi?id=829834
https://bugzilla.novell.com/show_bug.cgi?id=829834#c15
Scott Couston changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|secure@aphofis.com |
--- Comment #15 from Scott Couston 2013-11-09 08:29:53 EST ---
The following may help. I never ever perform automated installations. I go
though every single part of every installation step by step so install is not
calling the next phase.
I can tell you in my sleep every single part of an unattended installation as I
never ever use it and your correct about the usual second online update that is
most always required.
No point in debugging the whole of install without looking at each step in
isolation. I would suggest that up until beta that auto call next stage should
be inhibited. I would hope this requires little testing as the only time you
are going to see faults with the progression of each module is if unattended
install is off.
I may have stumbled across the answer and you supplying details of log
information has helped a great deal. What's not traditional here are two
things. Its X_64 and the BIOS is UEFI active.
During the install of 12.3 if the existing disk format is modified or imported
there is no warning of the need for a boot partition to exist on FAT
/boot/uefi.
If I create a completely new disk partitioning, on exit and without a FAT
/boot/eufi mount point, the partitioner issues a huge warnings regarding boot
failure but only If I start off afresh and don’t simply modify or accept
pre-existing or system generated formatting, mount point suggestions. This
really stuffs up update installation that I have not tested.
I have a completely successful useful and boot/suspend of a 12.3 system on X_64
with UEFI BIOS using 12.3 when I set a boot partition of FAT and a mount point
of /boot/uefi as the partitioner sternly warns only if I create a completely
new Disk Partitioning system.
I most often use a RAID5 mount point to hold data I don’t want to loose due
disk failure using some obtuse mount point but never /home or /root or /boot
mount points.
To tell you the truth I have no damn idea why we suddenly have decided that a
UEFI BIOS in X_64 has complications with our kernel; probably as we have
refined the Kernel to where my mind has absolutely no idea where...Sure I have
a few thoughts.
Provisional finding is I have a working system on 12.3 on X_64 UEFI
Hardware/BIOS only when I have a FAT /boot/uefi disk partition. I don’t know if
this is by accident or in keeping with log data showing errors...that I have to
leave to you to talk to the kernel and Hardware guys about...Leaving status for
now.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.