Bug #13703
openHipster 2021.04 RC1 testing
0%
Description
Text installer will not install into a freshly created pool. It displays the install progress screen, but nothing happens after that.
I invoked /usr/bin/text-install using truss. Truss output is attached. Command was "truss -f -o truss.ouput-3".
Screen shot shows that size of truss file has not changed for 5 minutes. F9_Quit does not work. The only option is to kill the terminal.
Files
Updated by Reginald Beardsley over 2 years ago
This disk was faulted out by a Solaris 10 u8 system and had two pools, a 100 GB mirrored root pool and a 1.8 TB RAIDZ1 export pool. A subsequent disk scan reported that the disk was OK. "zpool labelclear -f c4d0s1" appears to have resolved the issue.
As I only wanted to install to a freshly created pool in the s0 slice, I don't think that the existence of a corrupted pool label in the s1 slice should affect the installation process.
Install appeared to complete normally.
Updated by Reginald Beardsley over 2 years ago
- File IMG_1772.JPG IMG_1772.JPG added
- File IMG_1773.JPG IMG_1773.JPG added
The BIOS IDE boot install booted normally. But it was unable to boot after changing the BIOS to AHCI mode.
A reinstall with the BIOS already in AHCI mode booted the ISO properly and appeared to complete, but would not boot from disk with the same error message.
It would be nice if the first case worked, but not essential. The 2nd case where the user has installed with the BIOS in AHCI mode should boot properly after installing.
I'll take a look at the text-installer script to see if I can sort out a proper way to allow the user to install onto a disk with multiple slices and an existing pool more gracefully.
Changing to the nVidia driver did not go well. See screen photo.
Updated by Reginald Beardsley over 2 years ago
NB: system is an HP Z400 w/ BIOS version 3.61 and a Quadro FX 1800 graphics card.
As I've been at this for almost 4 hours I'm going to stop for now. More tomorrow.
Updated by Marcel Telka 4 months ago
- Status changed from New to Feedback
Please try again with OpenIndiana 2023.05 and report back.