Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install.vbs does not produce a bootable USB? #299

Open
rushowr opened this issue Sep 23, 2023 · 6 comments
Open

install.vbs does not produce a bootable USB? #299

rushowr opened this issue Sep 23, 2023 · 6 comments

Comments

@rushowr
Copy link

rushowr commented Sep 23, 2023

Issue

The script install.vbs runs without error but the resulting USB drive is not bootable and shows RAW partition in Windows 10 64bit (up to date).

Steps to reproduce

On a Windows 10 22H2 64-Bit installation that is up to date, perform the following steps:

  1. Download esos-4.19 from ESOS website
  2. Extract downloaded archive to a location on your system that does not have spaces in the path to it
  3. Run install.vbs as per documentation.
  4. Attempt to boot a system from the USB used when running install.vbs (I booted from BIOS, not UEFI).
@rushowr
Copy link
Author

rushowr commented Sep 27, 2023

Anybody?

@msmith626
Copy link
Contributor

Can you provide all of the output from the console window where 'install.vbs' ran (copy/paste). I assume there is some issue when it's doing it's thing and the error condition is not handled, etc.

@rushowr
Copy link
Author

rushowr commented Oct 4, 2023

Sure, here's what I got from the script:

*** Enterprise Storage OS Install Script ***

### Verifying checksums...
esos-4.1.9_z.img.tar.bz2: OK

esos-4.1.9_z.img.tar.bz2: OK


### Here is a list of disks on this machine:

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: MIYAMOTO

DISKPART>
  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          931 GB      0 B        *
  Disk 1    Online          931 GB  2048 KB        *
  Disk 2    Online         3726 GB      0 B        *
  Disk 3    Online         3726 GB  1024 KB        *
  Disk 4    Online          931 GB  1024 KB        *
  Disk 5    Online         3726 GB  1024 KB        *
  Disk 6    Online         3726 GB      0 B        *
  Disk 7    Online           29 GB    28 GB
  Disk 8    No Media           0 B      0 B
  Disk 9    No Media           0 B      0 B
  Disk 10   No Media           0 B      0 B
  Disk 11   No Media           0 B      0 B
  Disk 12   No Media           0 B      0 B

DISKPART>


### Please type the disk number of your USB flash drive:
7


### Proceeding will completely wipe disk 7. Are you sure?
yes

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: MIYAMOTO

DISKPART>
Disk 7 is now the selected disk.

DISKPART>
DiskPart succeeded in cleaning the disk.

DISKPART>


### Extracting the image file...

7-Zip 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18

Processing archive: F:\esos-4.1.9_z\esos-4.1.9_z.img.tar.bz2

Extracting  esos-4.1.9_z.img.tar

Everything is Ok

Size:       689428480
Compressed: 519003624



### Writing F:\esos-4.1.9_z\esos-4.1.9_z.img.tar to \\?\device\harddisk7\partition0; this may take a while...
rawwrite dd for windows version 0.6beta3.
Written by John Newbigin <[email protected]>
This program is covered by terms of the GPL Version 2.

657+1 records in
657+1 records out


### It appears the image was successfully written to disk (check for error messages)!


*** RAID controller management utilities are now installed using the 'raid_tools.py' script in a running ESOS instance. ***

### ESOS USB drive installation complete!
### You may now remove and use your ESOS USB drive.

Press the ENTER key to exit...

@rushowr
Copy link
Author

rushowr commented Oct 9, 2023

The resulting USB thumbdrive is inserted into the server, which is powered on and posts (BIOS and uEFI methods were both tested) but then when the boot process should start the user is presented with a blank screen and no activity on either the USB drive or hard drives (by watching for LED lights, which do work)

@msmith626
Copy link
Contributor

msmith626 commented Oct 17, 2023 via email

@GrimDemon
Copy link

The problem is that IMG images from the new v4 branch are double bzipped and the Windows VBS script calls dd on image.img.tar. This causes the TAR file to be sent to the flash drive instead of the actual image. The result is a single RAW partition that is unbootable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants