[Voyage-linux] 0.7.0 boot problem

Bjorn Pehrson (spam-protected)
Thu Mar 10 17:15:45 HKT 2011


Hi, thank you for your response! answers to your questions inline below

On 03/10/2011 10:02 AM, Kim-man 'Punky' TSE wrote:
> Hi Bjorn,
>
> 1. did you use voyage 0.7.0 official build or daily build?

I used the "current"-build which probably is the daily? Was that a 
mistake? It worked well with 0.6.5 but I see your point... I will try 
the official version

> 2. did you format the CF using format-cf.sh or label the CF as ROOT_FS?

Well, I am not sure, when would that happen?  The sequence I used is the 
following

bjorn at bp:~$*sudo fdisk /dev/sdc*

Command (m for help): d**<CR>

Command (m for help): *n *<CR>

e extended

p primary partition (1-4)

p**<CR>

Partition number (1-4): *1*

First cylinder (1-621, default 1):<CR>

Last cylinder or +size or +sizeM or +sizeK (1-973, default 973):<CR>

Command (m for help): a

Partition number (1-4): 1

Command (m for help): p

Disk /dev/sdc: 4017 MB, 4017807360 bytes

128 heads, 63 sectors/track, 973 cylinders

Units = cylinders of 8064 * 512 = 4128768 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

/dev/sdc1 * 1 973 3923104+ 83 Linux

Command (m for help): w

bjorn at bp:~$ umount /dev/sdc1

bjorn at bp:~$ sudo mkfs.ext2 /dev/sdc1

mke2fs 1.41.11 (14-Mar-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

245280 inodes, 980776 blocks

49038 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=1006632960

30 block groups

32768 blocks per group, 32768 fragments per group

8176 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912, 819200, 884736

Writing inode tables: done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 26 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

bjorn at bp:~$*sudo tune2fs -c 0 /dev/sdc1*

tune2fs 1.41.11 (14-Mar-2010)

Setting maximal mount count to -1

bjorn at bp:~$*sudo tar --numeric-owner -jxvf voyage-current.tar.bz2*

bjorn at bp:~$*cd voyage-current*

bjorn at bp:~$*sudo ./usr/local/sbin/voyage.update*

voyage.update scripts will ask you a couple of questions to complete the 
installation:

1 - Create new Voyage Linux disk

2 - Update existing Voyage configuration

3 - Exit

Press 1 to install voyage to disk device. You will be prompted tohrough 
installation menu. Go through the menu item 1 - 6 in sequence.

1 - Specify Distribution Directory

2 - Select Target Profile

3 - Select Target Disk

4 - Select Target Bootstrap Loader

5 - Configure Target Console

6 - Copy Distribution to Target

7 - Exit

It will take a short while (~1 min) to copy all files from software 
package to disk device. The above configuration will be saved to 
.voyage.config. If you run voyage.update next time, it will use same 
configuration as default.


> Regards,
> Punky
>
> On 3/10/2011 4:42 PM, Bjorn Pehrson wrote:
>> Although I am a voyage/Alix 6 newbie, I had no problems installing 
>> 0.6.5 a couple of months ago.
>>
>> However, when I try to install 0.7.0 from scratch, I cannot get it to 
>> boot after moving the flash disk to the Alix board.
>> No indications of problems when creating the disk according to the 
>> same procedure as for 0.6.5.
>>
>> Everthing seems OK when I start booting until I get the messages below.
>>
>> I got a lot of hits when I googled for the key words but it seems as 
>> if these messages can be caused by many different sorts of problems.
>>
>> It seems as if the boot program cannot find the file system.
>> I tried to start all over for times but got exactly the same behaviour.
>>
>> Anything obvious that I miss?
>>
>> [    1.320673] Root-NFS: No NFS server available, giving up.
>> [    1.336959] VFS: Unable to mount root fs via NFS, trying floppy.
>> [    1.355355] VFS: Cannot open root device "LABEL=ROOT_FS" or 
>> unknown-block(2,0)
>> [    1.377111] Please append a correct "root=" boot option; here are 
>> the available partitions:
>> [    1.402229] Kernel panic - not syncing: VFS: Unable to mount root 
>> fs on unknown-block(2,0)
>> [    1.583419] Clocksource tsc unstable (delta = 244680813 ns)
>>
>>
>> Bjorn
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux at list.voyage.hk
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20110310/707a7dd2/attachment-0002.html>


More information about the Voyage-linux mailing list