No boot (same!)

[Cubytus]

Hello there,

as I wanted to compare performance on really low-powered systems, I wrote an SD card with fvdw for the raspberry with command

Code: Select all

dd if=./fvdw-sl-raspb2-SD-install-11-june-14.img of=/dev/disk3 bs=4m && sync

Waited 20 minutes to be ready, then plugged it in a RPi, but it doesn't boot. No IP is assigned by the DHCP server, and the ACTIVITY led just doesn't even blink.

Any idea what's happening?

[fvdw]

are you sure that your SD card is comptible with the raspberry, and what type of raspberry do you have ?

[Cubytus]

A regular B model, and yes, the SD card is compatible. I used it previously with another distro. Sorry I have very few information on what may be ongoing.

[fvdw]

:scratch difficult , I always write the image on pc running windows. Do you have a PC running windows to try the described process.

If that doesn't work either we need to check the content of the sd card after using the dd command
can you post the partition table of the sd card after writing it using the dd command

Code: Select all

fdisk -l /dev/disk3

[Cubytus]

I get:

Code: Select all

/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *16.0 GB    disk3
   1:             Windows_FAT_32                         98.7 MB    disk3s1
   2:                 Linux_Swap                         263.2 MB   disk3s3
   3:                      Linux                         2.6 GB     disk3s4
   4:                      Linux                         74.0 MB    disk3s5
   5:                      Linux                         394.8 MB   disk3s6
   6:                      Linux                         271.4 MB   disk3s7
   7:                      Linux                         279.6 MB   disk3s8

And with GDisk, using the same syntax as fdisk:

Code: Select all

GPT fdisk (gdisk) version 1.0.0

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************

Disk /dev/disk3: 31275008 sectors, 14.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 7D0FCBD5-2CAF-4FBC-B3DD-CBE5864563C2
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31274974
Partitions will be aligned on 1-sector boundaries
Total free space is 23564056 sectors (11.2 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              63          192779   94.1 MiB    0700  Microsoft basic data
   3         2184840         2698919   251.0 MiB   8200  Linux swap
   4         2698920         7711199   2.4 GiB     8300  Linux filesystem
   5          192843          337364   70.6 MiB    8300  Linux filesystem
   6          337428         1108484   376.5 MiB   8300  Linux filesystem
   7         1108548         1638629   258.8 MiB   8300  Linux filesystem
   8         1638693         2184839   266.7 MiB   8300  Linux filesystem

The Windows running PC currently has a corrupted partition table, and thus can't boot either.

[fvdw]

the output of fdisk is strange, the image is setup with msdos partition table.
That extended partition contains partition 5 to 8
I your fdisk output I don't see partition 2 and the numbering of partitions is wrong 3 has become 2 etc
Also why are the start and end sectors or blocks not shown ?

Funny is that your gdisk output shows a more recognizable output although.

Anyhow if the bootloader uses the partition scheme as your fdisk is outputting then it won't be able to boot, it tries to load a kernel from partition 1 en then a root file system from partition 5 which will load the firmware from either partition 7 or 8 dependent from boot script settings. If the partition numbering is wrong then it will fail

ps in our linux system the sd card should be identified as mmcblk0 as that id is used in the boot scripts

This is what the partiton table should look like (I used a 8 GB flash card)

Code: Select all

Disk /dev/mmcblk0: 7969 MB, 7969177600 bytes
255 heads, 63 sectors/track, 968 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes



        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk0p1               1          12       96358+  c Win95 FAT32 (LBA)
/dev/mmcblk0p2              13         136      994731+  5 Extended
/dev/mmcblk0p3             137         168      257040  82 Linux swap
/dev/mmcblk0p4             169         480     2506140  83 Linux
/dev/mmcblk0p5              13          21       70962+ 83 Linux
/dev/mmcblk0p6              22          69      385528+ 83 Linux
/dev/mmcblk0p7              70         102      265041  83 Linux
/dev/mmcblk0p8             103         136      273073+ 83 Linux

Something must be wrong with your dd command line
To reproduce your problem I need to find my usb card reader so I can connect it to one of my NAS devices and try the dd command

I checked the image file itself, it looks ok :scratch

Code: Select all

root@fvdwsl-5big2:/share/1000/public # fdisk -l fvdw-sl-raspb2-SD-install-11-june-14.img

Disk fvdw-sl-raspb2-SD-install-11-june-14.img: 4007 MB, 4007657472 bytes
255 heads, 63 sectors/track, 487 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

                                   Device Boot      Start         End      Blocks  Id System
fvdw-sl-raspb2-SD-install-11-june-14.img1               1          12       96358+  c Win95 FAT32 (LBA)
fvdw-sl-raspb2-SD-install-11-june-14.img2              13         136      996030   5 Extended
fvdw-sl-raspb2-SD-install-11-june-14.img3             137         168      257040  82 Linux swap
fvdw-sl-raspb2-SD-install-11-june-14.img4             169         480     2506140  83 Linux
fvdw-sl-raspb2-SD-install-11-june-14.img5              13          21       72261  83 Linux
fvdw-sl-raspb2-SD-install-11-june-14.img6              22          69      385528+ 83 Linux
fvdw-sl-raspb2-SD-install-11-june-14.img7              70         102      265041  83 Linux
fvdw-sl-raspb2-SD-install-11-june-14.img8             103         136      273073+ 83 Linux
root@fvdwsl-5big2:/share/1000/public #


what happens if you use (skipping the block size parameter)

Code: Select all

dd if=./fvdw-sl-raspb2-SD-install-11-june-14.img of=/dev/disk3

last request desribe what the leds on the raspberry board do when power it up

[Cubytus]

fdisk on Mac OS X doesn't display sectors, and doesn't support the -l flag. Linux is not available, since a corrupted partition table on the hard drive blocks booting. And I don't have any USB SD card reader.

Speaking of which, if anyone here knows how to use TestDisk, I'll take an advice :( The wiki isn't enough.

I re-wrote fvdw without the bs option (took 41 minutes, probably because I didn't specify the optimal block size.), and it finally booted, as I could see on the connected TV. What is strange is the ACT LED didn't blink. So far I don't get why it failed to boot in the first place.

As I could see on TV, after boot the user is dumped to a root command prompt, without even asking for a login. It doesn't make a difference on a LaCie, but is a very serious security risk on a Raspberry Pi, where USB ports are readily available. On the upside, its web interface seems to be much more reactive than OpenMediaVault's one. OMV has more functions and wider support. The new firmware doesn't appear, although I activated the automatic update. Another malfunction: it doesn't update the time from the internet, with error message
could not update field :__FILE__, hwclock -w -u, err= 1
This is probably because the RPi doesn't have any hardware clock. Why not preset fvdw so as to automatically update time from the internet? Raspbian already does it, although I understand that fvdw seems to be built from Arch Linux. As such, the easy-to-use raspi-config script isn't available.

From fdisk, I get:

Code: Select all

fdisk -l

Disk /dev/mmcblk0: 16.0 GB, 16012804096 bytes
255 heads, 63 sectors/track, 1946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk0p1               1          12       96358+  c Win95 FAT32 (LBA)
/dev/mmcblk0p2              13         136      996030   5 Extended
/dev/mmcblk0p3             137         168      257040  82 Linux swap
/dev/mmcblk0p4             169         480     2506140  83 Linux
/dev/mmcblk0p5              13          21       72261  83 Linux
/dev/mmcblk0p6              22          69      385528+ 83 Linux
/dev/mmcblk0p7              70         102      265041  83 Linux
/dev/mmcblk0p8             103         136      273073+ 83 Linux


[fvdw]

the hwclock error will go away if you upgrade to 16-0 using the webinterface of fvdw-sl firmware

And in the web interface you set to let the time be set via internet

Raspbian already does it, although I understand that fvdw seems to be built from Arch Linux. As such, the easy-to-use raspi-config script isn't available.

This choice is by purpose, Raspbian linux doesn't contain the right libraries and binaries to run the firmware.
Basically we only use the kernel from Arch Linux and out own root file system.
To make it 100% compatible with Rasbian will take quite some effort en compiling of severla packages to solve all dependency issues. Until now I did not find the time for that, maybe later this year

[Cubytus]

So still no automatic update to the 16 firmware version?

[fvdw]

You need to download the upgrade file and start the upgrade via the web interface, thats all ;)