Ubuntu
subiquity package

How does the storage devices available for installation get populated and can that be re-ran manually?

Asked by Nick Nabb

Because of our certain circumstances, I have to do some work to make the iSCSI volume available to the OS. Even with a connected session and the volumes mounted, the installer doesn't see these new drives. Is there a way to restart the installer (without a server restart) and/or trigger a drive rescan so that it will bit up the new volumes and be available for installation?

Additional Notes:

I have a HPE BL460c Gen9 blade server using HP FlexFabric 10Gb 2-port 554FLB Network Cards with QLogic 57840S Network Interfaces to connect to a SAN via iSCSI that we're trying to install Ubuntu 18.04 on (specific hardware notes in case anyone else has this issue). I've asked roughly this question as well on askubuntu.com to hopefully help me and anyone else running into this:

https://askubuntu.com/questions/1177868/how-to-trigger-a-rescan-of-available-disks-for-installation-during-ubuntu-18-04

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu subiquity Edit question
Assignee:
No assignee Edit question
Solved by:
Nick Nabb
Solved:
Last query:
Last reply:
Revision history for this message
Nick Nabb (nnabb) said : 		#1

For this specific question, I've found my answer. I found just running 'sudo subiquity' in my second tty will run the installer again (so obvious now!). Getting to the filesystem step, the volumes show. I had a new issue during the installation with curtin, however I'll investigate that and ask a new question if needed. Thank you for taking time on this!

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#2

Great share. Hopefully this will help others :-)

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

I'd have gone with:

sudo rescan-scsi-bus

Should do it

Revision history for this message
Nick Nabb (nnabb) said : 		#4

Thanks for the suggestion actionparsnip! I didn't find that command in the installer unfortunately. However, I found doing the above had issues with curtin once the installation began. But, killing the original process does allow the full installation to complete successfully:

kill -9 "$(ps aux | grep subiquity | grep -v 'grep' | awk '{print $2}')"