Forums

Resolved
0 votes
I have purchased HP ML10 Gen 9 server 2 days back and in their manual it has written as " ClearOS is preloaded with Proliant servers or the same can be downloaded from www.hpe.com/servers/clearos when i tried that link its been redirected to clearOS website and i have downloaded the iso file which has mentioned in that url. I have followed the following procedure to make the bootable pendrive but i got an error...

Procedure:(Mentioned on ClearOS Site)

{

Windows
You can use a program like WinDD or dd for Windows to write the file to USB.

Something like this…maybe?

dd if=clearos-professional-x86_64.iso of=\\.\Volume{6f41f4b2-d11a-11de-b318-001d4f88486c}
dd for Windows
Download and extract the dd zip file and then place the executable in your C:\Windows\ directory. Make sure that you insert the USB drive but close any applications that might open up the volume.

Open a command prompt (Start » Run » cmd)

In the command prompt, run the following to get a list of your drives:

dd --list
You should get an output such as this:

C:\Users\Username>dd --list
rawwrite dd for windows version 0.5.
Written by John Newbigin
This program is covered by the GPL. See copying.txt for details
Win32 Available Volume Information
\\.\Volume{19d85149-ddf1-11e2-9904-806e6f6e6963}\
link to \\?\Device\HarddiskVolume4
fixed media
Mounted on \\.\d:

\\.\Volume{4268772a-e552-11e5-868d-e89a8f45233b}\
link to \\?\Device\HarddiskVolume5
removeable media
Mounted on \\.\f:

\\.\Volume{19d85148-ddf1-11e2-9904-806e6f6e6963}\
link to \\?\Device\HarddiskVolume2
fixed media
Mounted on \\.\c:

\\.\Volume{19d85147-ddf1-11e2-9904-806e6f6e6963}\
link to \\?\Device\HarddiskVolume1
fixed media
Not mounted

\\.\Volume{9f0e9e5a-ddea-11e2-9d3a-e89a8f45233b}\
link to \\?\Device\SftVol
fixed media
Mounted on \\.\q:

\\.\Volume{92aa90c6-ddf2-11e2-8556-806e6f6e6963}\
link to \\?\Device\CdRom0
CD-ROM
Mounted on \\.\e:


NT Block Device Objects
\\?\Device\CdRom0

Virtual input devices
/dev/zero (null data)
/dev/random (pseudo-random data)
- (standard input)

Virtual output devices
- (standard output)
In this case, my USB device is 'F' and the volume label is:

\\.\Volume{4268772a-e552-11e5-868d-e89a8f45233b}\
Then run the dd program to image the ISO image to the disk.

dd if=C:\Users\Username\Downloads\ClearOS-DVD-x86_64.iso of=\\.\Volume{4268772a-e552-11e5-868d-e89a8f45233b} bs=1M

}

Error After following this procedure:

After completion of this process the pen drive becomes inaccessible, if i insert the pen drive it is asking to format
Wednesday, May 09 2018, 01:37 PM
Share this post:
Responses (5)
  • Accepted Answer

    Wednesday, September 05 2018, 07:51 PM - #Permalink
    Resolved
    0 votes
    Rufus is good. I've used Win32DiskImager as well.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, September 05 2018, 01:38 PM - #Permalink
    Resolved
    0 votes
    Well, for me the only (!) way to create a fully working iso on a usb-stick was to use rufus 3.1. Other image writing programs, even dd created an image that seemed bootable at first but then stop because of "timeouts" and other weird reasons. I tried at least 4 different programs under win10 64, only rufus 3.1 worked.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, May 12 2018, 12:26 PM - #Permalink
    Resolved
    0 votes
    I don't know why it is happening. I would go for a full installation straight from the ClearOS iso. There is no difference between the versions of the iso. You get to choose Community, Home or Business during the installation.

    You can burn the iso to disc or transfer it to a pen drive. For a pen drive you can use dd, Win32diskimager, Rufus and possibly other USB image writing programs.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, May 12 2018, 11:23 AM - #Permalink
    Resolved
    0 votes
    Yes, i have done that as er instruction replacing with my drive info....
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, May 09 2018, 01:47 PM - #Permalink
    Resolved
    0 votes
    Silly question but in your command did you substitute the "4268772a-e552-11e5-868d-e89a8f45233b" with the UUID relating to your drive found from the "dd --list" command?
    The reply is currently minimized Show
Your Reply