Discussion:
[PVE-User] sbin/unconfigured.sh
Steve
2017-05-18 17:55:38 UTC
Permalink
In version 3.2 ISO there was this script to start an install.
This file is not in recent versions.
Is there an equivalent way to start an install with v4.4 or any other
recent version?
Thanks
Steve
Uwe Sauter
2017-05-18 18:04:30 UTC
Permalink
Don't know what your situation is but there is a wiki page [1] that describes the installation of Proxmox on top of an
existing Debian.

[1] https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie
Post by Steve
In version 3.2 ISO there was this script to start an install.
This file is not in recent versions.
Is there an equivalent way to start an install with v4.4 or any other
recent version?
Thanks
Steve
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Steve
2017-05-18 18:08:36 UTC
Permalink
Thanks for the quick reply.
I am booting from the ISO file itself which is on a multiboot USB drive.
In previous versions, you could boot to the shell, mount the ISO as /mnt
and then start the install by running unconfigured.sh.

So basically, if I boot to the shell, how can I start the install from the
contents of the CD/ISO.
Post by Uwe Sauter
Don't know what your situation is but there is a wiki page [1] that
describes the installation of Proxmox on top of an
existing Debian.
[1] https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie
Post by Steve
In version 3.2 ISO there was this script to start an install.
This file is not in recent versions.
Is there an equivalent way to start an install with v4.4 or any other
recent version?
Thanks
Steve
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Uwe Sauter
2017-05-18 18:09:46 UTC
Permalink
Sorry, never did that. No idea…
Post by Steve
Thanks for the quick reply.
I am booting from the ISO file itself which is on a multiboot USB drive.
In previous versions, you could boot to the shell, mount the ISO as /mnt and then start the install by running
unconfigured.sh.
So basically, if I boot to the shell, how can I start the install from the contents of the CD/ISO.
Don't know what your situation is but there is a wiki page [1] that describes the installation of Proxmox on top of an
existing Debian.
[1] https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie
<https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie>
Post by Steve
In version 3.2 ISO there was this script to start an install.
This file is not in recent versions.
Is there an equivalent way to start an install with v4.4 or any other
recent version?
Thanks
Steve
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user <https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user>
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user <https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user>
Fabian Grünbichler
2017-05-19 06:34:47 UTC
Permalink
Post by Steve
Thanks for the quick reply.
I am booting from the ISO file itself which is on a multiboot USB drive.
In previous versions, you could boot to the shell, mount the ISO as /mnt
and then start the install by running unconfigured.sh.
So basically, if I boot to the shell, how can I start the install from the
contents of the CD/ISO.
you need to mount the contained squashfs files in the right order on the
right places, make an overlayfs and then bind mount the iso into that.
then you can chroot and run the unconfigured.sh script. basically do all
the steps that the initrd contained on the iso does ;)
Steve
2017-05-19 07:28:17 UTC
Permalink
Thanks
I tried that.
I made a new .sh from the portion of the initrd that mounts all the
squashfs files and runs unconfigured.sh.
It seems to almost work, but it gets to Detecting network settings... done
and then says
\nInstallation aborted - unable to continue

any ideas why?
Post by Fabian Grünbichler
Post by Steve
Thanks for the quick reply.
I am booting from the ISO file itself which is on a multiboot USB drive.
In previous versions, you could boot to the shell, mount the ISO as /mnt
and then start the install by running unconfigured.sh.
So basically, if I boot to the shell, how can I start the install from
the
Post by Steve
contents of the CD/ISO.
you need to mount the contained squashfs files in the right order on the
right places, make an overlayfs and then bind mount the iso into that.
then you can chroot and run the unconfigured.sh script. basically do all
the steps that the initrd contained on the iso does ;)
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Fabian Grünbichler
2017-05-19 08:12:05 UTC
Permalink
Post by Steve
Thanks
I tried that.
I made a new .sh from the portion of the initrd that mounts all the
squashfs files and runs unconfigured.sh.
It seems to almost work, but it gets to Detecting network settings... done
and then says
\nInstallation aborted - unable to continue
any ideas why?
boot it with "proxdebug" as part of the kernel cmdline and examine the
logs. you can also manually run "xinit" in the debug shell to restart
the installer from the debug shell.
Steve
2017-05-19 08:40:54 UTC
Permalink
I tried proxdebug. No extra messages are generated after the network has
initialised.
There is no log in /tmp folder ? Has the log moved?

How do I run xinit? Where is it?
Do you mean init? If I run this it says must be run as PID 1 - how can I
fix this (sorry, I am not a linux guru!)
Post by Fabian Grünbichler
Post by Steve
Thanks
I tried that.
I made a new .sh from the portion of the initrd that mounts all the
squashfs files and runs unconfigured.sh.
It seems to almost work, but it gets to Detecting network settings...
done
Post by Steve
and then says
\nInstallation aborted - unable to continue
any ideas why?
boot it with "proxdebug" as part of the kernel cmdline and examine the
logs. you can also manually run "xinit" in the debug shell to restart
the installer from the debug shell.
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Fabian Grünbichler
2017-05-19 09:04:57 UTC
Permalink
Post by Steve
I tried proxdebug. No extra messages are generated after the network has
initialised.
There is no log in /tmp folder ? Has the log moved?
How do I run xinit? Where is it?
Do you mean init? If I run this it says must be run as PID 1 - how can I
fix this (sorry, I am not a linux guru!)
just type "xinit" in the debug shell. but if you are not comfortable
with this kind of debugging, you might be better off just (temporarily)
"sacrificing" a thumb drive for the PVE installer instead of trying to
get this non-standard way to boot it to work ;)

I hope to fix the initrd during the 5.x release cycleto to allow booting
in some kind of loopback mode, but it's a low priority item on my todo
list..
Steve
2017-05-19 09:27:20 UTC
Permalink
If I type xinit it says /bin/sh: xinit: not found

I am the author of easy2boot which is a USB multiboot tool to allow people
to boot from 100's of different ISOs (or images) all from one USB stick.
I have been asked by a user to get proxmox 4 working.
3.2 works because I can run the unconfigured.sh from the command line

http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-easy2boot.html
http://www.easy2boot.com

I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to get
it to mount the FAT32 partition to /mnt. I do not need to manually use any
mount commands, it just automatically runs init but this causes an early
error message of
mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
but if I use the mount command I can see that /mnt is present as a vfat
/dev/sdb1
If I press CTRL+D to continue, it fails in the exact same place with
Installation aborted - unable to continue.
Note that this is not using my script at all, just the original init script
- I have not broken into the boot process because it picks up the lvm2root
parameter.

I am so *near*, yet I just cannot get the unconfigured.sh script to run in
this way...

thanks for your help.
Steve
Post by Fabian Grünbichler
Post by Steve
I tried proxdebug. No extra messages are generated after the network has
initialised.
There is no log in /tmp folder ? Has the log moved?
How do I run xinit? Where is it?
Do you mean init? If I run this it says must be run as PID 1 - how can I
fix this (sorry, I am not a linux guru!)
just type "xinit" in the debug shell. but if you are not comfortable
with this kind of debugging, you might be better off just (temporarily)
"sacrificing" a thumb drive for the PVE installer instead of trying to
get this non-standard way to boot it to work ;)
I hope to fix the initrd during the 5.x release cycleto to allow booting
in some kind of loopback mode, but it's a low priority item on my todo
list..
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Fabian Grünbichler
2017-05-19 11:46:38 UTC
Permalink
Post by Steve
If I type xinit it says /bin/sh: xinit: not found
I am the author of easy2boot which is a USB multiboot tool to allow people
to boot from 100's of different ISOs (or images) all from one USB stick.
I have been asked by a user to get proxmox 4 working.
3.2 works because I can run the unconfigured.sh from the command line
http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-easy2boot.html
http://www.easy2boot.com
I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to get
it to mount the FAT32 partition to /mnt. I do not need to manually use any
mount commands, it just automatically runs init but this causes an early
error message of
mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
but if I use the mount command I can see that /mnt is present as a vfat
/dev/sdb1
If I press CTRL+D to continue, it fails in the exact same place with
Installation aborted - unable to continue.
Note that this is not using my script at all, just the original init script
- I have not broken into the boot process because it picks up the lvm2root
parameter.
I am so *near*, yet I just cannot get the unconfigured.sh script to run in
this way...
thanks for your help.
Steve
I just did a quick test run using Grub:

loopback test PATHTOISO
linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
initrd (test)/boot/initrd.img
boot

drops me into the initrd debug shell

if I do the following (major/minor depend on your disk configuration,
check /sys/class/block/XXX/dev where XXX is your usb partition where
the iso is)

mknod /tmp/usbdev b MAJOR MINOR
mkdir /tmp/usbmnt
mount /tmp/usbdev /tmp/usbmnt
mount /tmp/usbmnt/PATHTOISO /mnt

followed by lines 294ff of the init script launch the graphical
installer (although the resolution is messed up - probably because I did
not bother to change any of the graphic stuff in Grub), and I am able to
complete the installation..

so I think it must be something in your environment / setup.

(note that there are TWO debug shells, one in the initrd with very
limited commands, and one in the installer environment with access to a
lot more tools - a quick test is to run something like "lsblk", since
that only exists in the latter environment ;). maybe your switch to the
installer environment did not work, and you are still in the initrd
shell? that would explain why you can't execute "xinit")
Steve
2017-05-19 11:51:02 UTC
Permalink
I just found a way to get it to work by modifying the grub menu and add
lvm2root=/dev/sdX4

where sdX4 is a partition on the USB drive which points directly to the ISO
file.
So I am booting from the ISO (mapped to the BIOS device (0xff) in grub4dos)
which boots to the grub2 menu and then I add the lvm2root parameter.

The strange thing is that if I boot from a FAT32 flat-file system and have
the ISO mapped to a partition in exactly the same way, the init script
fails.
Post by Steve
Post by Steve
If I type xinit it says /bin/sh: xinit: not found
I am the author of easy2boot which is a USB multiboot tool to allow
people
Post by Steve
to boot from 100's of different ISOs (or images) all from one USB stick.
I have been asked by a user to get proxmox 4 working.
3.2 works because I can run the unconfigured.sh from the command line
http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-
to-easy2boot.html
Post by Steve
http://www.easy2boot.com
I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to
get
Post by Steve
it to mount the FAT32 partition to /mnt. I do not need to manually use
any
Post by Steve
mount commands, it just automatically runs init but this causes an early
error message of
mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
but if I use the mount command I can see that /mnt is present as a vfat
/dev/sdb1
If I press CTRL+D to continue, it fails in the exact same place with
Installation aborted - unable to continue.
Note that this is not using my script at all, just the original init
script
Post by Steve
- I have not broken into the boot process because it picks up the
lvm2root
Post by Steve
parameter.
I am so *near*, yet I just cannot get the unconfigured.sh script to run
in
Post by Steve
this way...
thanks for your help.
Steve
loopback test PATHTOISO
linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
initrd (test)/boot/initrd.img
boot
drops me into the initrd debug shell
if I do the following (major/minor depend on your disk configuration,
check /sys/class/block/XXX/dev where XXX is your usb partition where
the iso is)
mknod /tmp/usbdev b MAJOR MINOR
mkdir /tmp/usbmnt
mount /tmp/usbdev /tmp/usbmnt
mount /tmp/usbmnt/PATHTOISO /mnt
followed by lines 294ff of the init script launch the graphical
installer (although the resolution is messed up - probably because I did
not bother to change any of the graphic stuff in Grub), and I am able to
complete the installation..
so I think it must be something in your environment / setup.
(note that there are TWO debug shells, one in the initrd with very
limited commands, and one in the installer environment with access to a
lot more tools - a quick test is to run something like "lsblk", since
that only exists in the latter environment ;). maybe your switch to the
installer environment did not work, and you are still in the initrd
shell? that would explain why you can't execute "xinit")
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Steve
2017-05-19 11:52:03 UTC
Permalink
See the blog post (end of page)
http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-easy2boot.html
Post by Steve
I just found a way to get it to work by modifying the grub menu and add
lvm2root=/dev/sdX4
where sdX4 is a partition on the USB drive which points directly to the
ISO file.
So I am booting from the ISO (mapped to the BIOS device (0xff) in
grub4dos) which boots to the grub2 menu and then I add the lvm2root
parameter.
The strange thing is that if I boot from a FAT32 flat-file system and have
the ISO mapped to a partition in exactly the same way, the init script
fails.
Post by Steve
Post by Steve
If I type xinit it says /bin/sh: xinit: not found
I am the author of easy2boot which is a USB multiboot tool to allow
people
Post by Steve
to boot from 100's of different ISOs (or images) all from one USB stick.
I have been asked by a user to get proxmox 4 working.
3.2 works because I can run the unconfigured.sh from the command line
http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-
easy2boot.html
Post by Steve
http://www.easy2boot.com
I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to
get
Post by Steve
it to mount the FAT32 partition to /mnt. I do not need to manually use
any
Post by Steve
mount commands, it just automatically runs init but this causes an early
error message of
mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
but if I use the mount command I can see that /mnt is present as a vfat
/dev/sdb1
If I press CTRL+D to continue, it fails in the exact same place with
Installation aborted - unable to continue.
Note that this is not using my script at all, just the original init
script
Post by Steve
- I have not broken into the boot process because it picks up the
lvm2root
Post by Steve
parameter.
I am so *near*, yet I just cannot get the unconfigured.sh script to run
in
Post by Steve
this way...
thanks for your help.
Steve
loopback test PATHTOISO
linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
initrd (test)/boot/initrd.img
boot
drops me into the initrd debug shell
if I do the following (major/minor depend on your disk configuration,
check /sys/class/block/XXX/dev where XXX is your usb partition where
the iso is)
mknod /tmp/usbdev b MAJOR MINOR
mkdir /tmp/usbmnt
mount /tmp/usbdev /tmp/usbmnt
mount /tmp/usbmnt/PATHTOISO /mnt
followed by lines 294ff of the init script launch the graphical
installer (although the resolution is messed up - probably because I did
not bother to change any of the graphic stuff in Grub), and I am able to
complete the installation..
so I think it must be something in your environment / setup.
(note that there are TWO debug shells, one in the initrd with very
limited commands, and one in the installer environment with access to a
lot more tools - a quick test is to run something like "lsblk", since
that only exists in the latter environment ;). maybe your switch to the
installer environment did not work, and you are still in the initrd
shell? that would explain why you can't execute "xinit")
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Steve
2017-05-19 12:51:06 UTC
Permalink
I think the problem is with grub4dos.

If I use this menu from a FAT32 USB drive

title ProxMox lvm2root=sda1
kernel /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/sda1 rw quiet
splash=silent
initrd /boot/initrd.img

then it does not work and I get the Installation aborted message

but if I use the same menu in grub2 from the same drive,

menuentry 'Install Proxmox VE sda1' --class debian --class gnu-linux
--class gnu --class os {
linux /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/sda1 rw quiet
splash=silent
initrd /boot/initrd.img
}

then it works and loads the installer GUI.

I also note that it does not change to 1024x768 when booting via grub4dos,
so I added

vga=791

and now it works!!!
Post by Steve
Post by Steve
If I type xinit it says /bin/sh: xinit: not found
I am the author of easy2boot which is a USB multiboot tool to allow
people
Post by Steve
to boot from 100's of different ISOs (or images) all from one USB stick.
I have been asked by a user to get proxmox 4 working.
3.2 works because I can run the unconfigured.sh from the command line
http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-
to-easy2boot.html
Post by Steve
http://www.easy2boot.com
I tried setting proxdebug and root=/dev/sdb1 or lvm2root=/dev/sdb1 to
get
Post by Steve
it to mount the FAT32 partition to /mnt. I do not need to manually use
any
Post by Steve
mount commands, it just automatically runs init but this causes an early
error message of
mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
but if I use the mount command I can see that /mnt is present as a vfat
/dev/sdb1
If I press CTRL+D to continue, it fails in the exact same place with
Installation aborted - unable to continue.
Note that this is not using my script at all, just the original init
script
Post by Steve
- I have not broken into the boot process because it picks up the
lvm2root
Post by Steve
parameter.
I am so *near*, yet I just cannot get the unconfigured.sh script to run
in
Post by Steve
this way...
thanks for your help.
Steve
loopback test PATHTOISO
linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
initrd (test)/boot/initrd.img
boot
drops me into the initrd debug shell
if I do the following (major/minor depend on your disk configuration,
check /sys/class/block/XXX/dev where XXX is your usb partition where
the iso is)
mknod /tmp/usbdev b MAJOR MINOR
mkdir /tmp/usbmnt
mount /tmp/usbdev /tmp/usbmnt
mount /tmp/usbmnt/PATHTOISO /mnt
followed by lines 294ff of the init script launch the graphical
installer (although the resolution is messed up - probably because I did
not bother to change any of the graphic stuff in Grub), and I am able to
complete the installation..
so I think it must be something in your environment / setup.
(note that there are TWO debug shells, one in the initrd with very
limited commands, and one in the installer environment with access to a
lot more tools - a quick test is to run something like "lsblk", since
that only exists in the latter environment ;). maybe your switch to the
installer environment did not work, and you are still in the initrd
shell? that would explain why you can't execute "xinit")
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Steve
2017-05-19 22:58:26 UTC
Permalink
​​
Here is final grub4dos menu for use with Easy2Boot which works

iftitle [if exist $HOME$/proxmox-ve_4.4-eb2d6f1e-2.iso] proxmox 4.4\n You
must enter the correct USB name.
set ISO=proxmox-ve_4.4-eb2d6f1e-2.iso

set ldisk=
errorcheck off
if not exist ldisk geometry (hd9) > nul && set ldisk=sdj4
if not exist ldisk geometry (hd8) > nul && set ldisk=sdi4
if not exist ldisk geometry (hd7) > nul && set ldisk=sdh4
if not exist ldisk geometry (hd6) > nul && set ldisk=sdg4
if not exist ldisk geometry (hd5) > nul && set ldisk=sdf4
if not exist ldisk geometry (hd4) > nul && set ldisk=sde4
if not exist ldisk geometry (hd3) > nul && set ldisk=sdd4
if not exist ldisk geometry (hd2) > nul && set ldisk=sdc4
if not exist ldisk geometry (hd1) > nul && set ldisk=sdb4

echo
echo -e $[0104] I guess partition 4 of the USB drive will be %ldisk%
echo
set /p ldisk=Enter linux device name for USB drive (ptn4), e.g. sdb4 or
sdc4 (ESC=%ldisk%) :
echo
pause --wait=3 Will use /dev/%ldisk%
set NOSUG=1
set redir=> nul
/%grub%/QRUN.g4b $HOME$/%ISO%
kernel /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/%ldisk% vga=791
rw
initrd /boot/initrd.img
boot

Thanks for your help
​.​

Steve
2017-05-19 13:04:37 UTC
Permalink
One last hurdle!

instead of /dev/sda1 I want to use /dev/disk/by-uuid/XXXXXXX because I
don't know how many disks there are in the system

but it does not work - I presume that /dev/disk/by-uuid does not yet exist
at the time the init script is running?

Is there any other way to reference the partition? I am guessing that
by-label will not work either?...

Steve
Post by Fabian Grünbichler
Post by Steve
I tried proxdebug. No extra messages are generated after the network has
initialised.
There is no log in /tmp folder ? Has the log moved?
How do I run xinit? Where is it?
Do you mean init? If I run this it says must be run as PID 1 - how can I
fix this (sorry, I am not a linux guru!)
just type "xinit" in the debug shell. but if you are not comfortable
with this kind of debugging, you might be better off just (temporarily)
"sacrificing" a thumb drive for the PVE installer instead of trying to
get this non-standard way to boot it to work ;)
I hope to fix the initrd during the 5.x release cycleto to allow booting
in some kind of loopback mode, but it's a low priority item on my todo
list..
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Steve
2017-05-19 07:36:46 UTC
Permalink
P.S.
As an experiment, I even inserted a dd'd flash drive containing the proxmox
ISO (which works if I boot to it) and then booted from my multiboot USB
drive to the shell and then mounted /mnt as the flash drive
mount /dev/sdc /mnt

then I ran the modified script.
I gave the same fail message.
So that seems to indicate that something is wrong with the script or
environment when I run the script?

The script I run starts with
if [ -f /mnt/pve-installer.squashfs ]; then
echo this is a Proxmox VE installation CD

if ! mount -t squashfs -o ro,loop /mnt/pve-base.squashfs
/mnt/.pve-base; then
debugsh_err_reboot "mount pve-base.squashfs failed"
fi

any ideas what is not set up before this?

Steve
Post by Fabian Grünbichler
Post by Steve
Thanks for the quick reply.
I am booting from the ISO file itself which is on a multiboot USB drive.
In previous versions, you could boot to the shell, mount the ISO as /mnt
and then start the install by running unconfigured.sh.
So basically, if I boot to the shell, how can I start the install from
the
Post by Steve
contents of the CD/ISO.
you need to mount the contained squashfs files in the right order on the
right places, make an overlayfs and then bind mount the iso into that.
then you can chroot and run the unconfigured.sh script. basically do all
the steps that the initrd contained on the iso does ;)
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Loading...