FYI; I just ran the latest image update to my box yesterday without any 
problems; and md5sum does seem to match yours so problem must be somewhere else.
I wrote the image dd-ed from my Mac.
>>>>>>>>>>>>>>>>leow$ fdisk smartos-latest-USB.imgDisk: smartos-latest-USB.img  
>>>>>>>>>>>>>>>>geometry: 968/64/63 [3906250 sectors]Signature: 0xAA55         
>>>>>>>>>>>>>>>>Starting       Ending #: id  cyl  hd sec -  cyl  hd sec [     
>>>>>>>>>>>>>>>>start -       
>>>>>>>>>>>>>>>>size]------------------------------------------------------------------------*1:
>>>>>>>>>>>>>>>> 0C    0   9  34 -  243  34  63 [       600 -    3905400] Win95 
>>>>>>>>>>>>>>>>FAT32L 2: 00    0   0   0 -    0   0   0 [         0 -          
>>>>>>>>>>>>>>>>0] unused       3: 00    0   0   0 -    0   0   0 [         0 - 
>>>>>>>>>>>>>>>>         0] unused       4: 00    0   0   0 -    0   0   0 [    
>>>>>>>>>>>>>>>>     0 -          0] unused      
leow$ md5 smartos-latest-USB.imgMD5 (smartos-latest-USB.img) = 
10f5aa470e52ca1becbd0cf664729296
leow$ md5  smartos-latest-USB.img.bz2 MD5 (smartos-latest-USB.img.bz2) = 
a80cee18a2bc492bf7d9c3224a466484
>>>>>>>>>>>>
I just followed the instruction on SmartOS blog; set the first partition to 
active and boot as per normal.  No problem.
Regards,Michael Leow
From: [email protected]
To: [email protected]; [email protected]
Subject: RE: [smartos-discuss] Re: Trouble creating USB boot drive.
Date: Fri, 26 Dec 2014 20:27:29 -0800

Thank you for the reply.

on my machine,
$ md5sum smartos-20141225T170427Z-USB.img.bz2

returns:

a80cee18a2bc492bf7d9c3224a466484  smartos-20141225T170427Z-USB.img.bz2

which matches 
https://us-east.manta.joyent.com/Joyent_Dev/public/builds/smartos/release-20141225-20141225T170427Z/smartos//md5sums.txt

-----------------
I would like to verify the bunzip2 .img file but there is no md5sum in that txt 
file.

$ md5sum smartos-20141225T170427Z-USB.img

gives me:

10f5aa470e52ca1becbd0cf664729296  smartos-20141225T170427Z-USB.img

-----------------

when I try
$ fdisk -l smartos-20141225T170427Z-USB.img 

    Disk smartos-20141225T170427Z-USB.img: 2000 MB, 2000000000 bytes
    35 heads, 63 sectors/track, 1771 cylinders, total 3906250 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000

                               Device Boot      Start         End      Blocks   
Id  System
    smartos-20141225T170427Z-USB.img1   *         600     3905999     1952700   
 c  W95 FAT32 (LBA)
 
which is matching what was written and what I think may be an error.

-----------------------------

I am trying to mount the .img and then I would copy the contents, but I am 
failing that attempt:

    $ sudo mount -o loop smartos-20141225T170427Z-USB.img smartos_test

    mount: you must specify the filesystem type

    $ sudo mount -o loop -t auto smartos-20141225T170427Z-USB.img smartos_test

    mount: you must specify the filesystem type

    $ sudo mount -o loop -t vfat smartos-20141225T170427Z-USB.img smartos_test

    mount: wrong fs type, bad option, bad superblock on /dev/loop0,
           missing codepage or helper program, or other error
           In some cases useful info is found in syslog - try
           dmesg | tail  or so

    $ dmesg | tail

    [14171.859012] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
    [14171.859249] FAT-fs (loop0): invalid media value (0xc0)
    [14171.859259] FAT-fs (loop0): Can't find a valid FAT filesystem
    [14181.899940] FAT-fs (loop0): invalid media value (0xc0)
    [14181.899948] FAT-fs (loop0): Can't find a valid FAT filesystem
    [14191.095027] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
    [14191.095083] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
    [14191.095108] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
    [14191.095158] FAT-fs (loop0): invalid media value (0xc0)
    [14191.095161] FAT-fs (loop0): Can't find a valid FAT filesystem    
    
---------------------

So, to me, I will agree that something is corrupt: however my md5 is 
matching... so I suspect there was an issue when the img file was created.

---------------------

Thanks for the answer on , bss=0x0 . But I am still going to suggest that this 
cryptic message be changed into something that we can rather enjoy.

---------------------

Another: what is up with the .img file taking 2000000000 bytes when there is 
1.7 GB of free space on the resultant drive? Why not just have the .img file 
take up 300MB?



- [email protected]
- http://www.jjsland.com/

Subject: Re: [smartos-discuss] Re: Trouble creating USB boot drive.
From: [email protected]
Date: Fri, 26 Dec 2014 21:03:22 -0600
To: [email protected]; [email protected]

It sounds like you're copying a bad image.  Re-download it and make sure the 
hash matches.  The ,bss=0x0 is just kernel output to the console.  You see 
similar things booting a FreeBSD or OpenBSD system while the kernel is loading.

On December 26, 2014 7:20:53 PM CST, JJ Stiff via smartos-discuss 
<[email protected]> wrote:Somehow I am having trouble creating 
a USB boot drive with the new images via ubuntu 14.04:

smartos-20141225T170427Z-USB.img
smartos-20141212T064606Z-USB.img

I do:
$ sudo dd if=smartos-20141225T170427Z-USB.img of=/dev/sdd bs=1024
$ sudo dd if=smartos-20141225T170427Z-USB.img of=/dev/sdd bs=1024k
$ sudo dd if=smartos-20141225T170427Z-USB.img of=/dev/sdd bs=1M
$ sudo dd if=smartos-20141225T170427Z-USB.img of=/dev/sdd bs=4M

all with the same result, that the device is recognized as USB-ZIP and is not 
bootable; as opposed to a USB Device:

'sudo fdisk -l' gives:
/dev/sdd1   *         600     3905999     1952700    c  W95 FAT32 (LBA)

From an older image I was getting:
/dev/sdd1   *         
63     3903794     1951866    c  W95 FAT32 (LBA)

I have a feeling the 600 Start block rather than 63 is giving me the headache.

Another note: The volume name is NONAME as opposed to HEADNODE as in the 
working version. Also I was able to successfully copy my old usb drive:

$ sudo dd if=/dev/sde of=/dev/sdd bs=4M

but, of course, I would like to use the current version.

I even tried to use the iso, without success.
$ sudo dd if=smartos-20141225T170427Z.iso of=/dev/sdd bs=1M
 
---------------

Aside: what is the purpose of the 
, bss=0x0 

It would be nice to see 'loading SmartOS verison: 20141225T170427Z' or 
something to that effect...

-----


- [email protected]
- http://www.jjsland.com/            
      smartos-discuss | Archives

 | Modify
 Your Subscription


-- 

Sent from my Android device with K-9 Mail. Please excuse my brevity.
      smartos-discuss | Archives

 | Modify
 Your Subscription
                                          


-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to