First conclusion is the the box is running OK. Disk is recognized, kernel loaded and booted, only the init script is a problem.
from what he says I should connect 4 hd .....
Yes. I took the /init script, and put it next to your bootlog. This part is executed:
# We need the first disk to know if this is the first boot
debug_msg "Waiting for the master disk to spin up"
waitForDevices 1 1
# Check the first disk to see if we are in the first boot
firstDisk="`getAvailableDisks | head -n 1`"
# If we are in the first boot, we wait for all devices to spin up
if [ $firstBoot -eq $TRUE ] ; then
# But before doing any new actions, check if the lowlevel
# firmware (i.e. U-Boot) has to be updated
# N.B.: If an update is needed, the function will not return.
# Ok, since we returned, we can now wait for all the devices
It seems it will wait forever in waitForDevices. I hoped it would timeout, and go on with only one disk, but that seems not to happen. BTW, you can find this script in the initramfs tarball in the partition directory. This initramfs is a ramdrive, which is encapsulated inside
the kernel, and from which /init is executed first. This script is responsible (among other stuff) for finding the firmware on the disk, and booting that.
I tried it and actually post the interface part...
Are you saying that you put in 4 disks, and that the booting continued?
but how can I use a single hd temporarily in place of 4??
It seems the 'new disk' script will only run if 4 disks are available. You could remove the 'new disk' label to get past this point. In that case it will fail on building the raid arrays, but I *think* it will drop you in a shell.
The 'new disk' label is removed this way:
echo 5Big | dd of=/dev/sdb seek=3
if I want to then incrementere capacity until I get there? as I understand enough that hd with the system remains always the others are interchangeable?
On the Lacie OS all disks are equal. You can pull one randomly, and the system will go on. If it's the disk from which it originally booted, well, on next boot it will just use a different disk. The bootloader is programmed to search for a kernel on sda10, sdb10, .., sde10, sda6, ..., sde6. The first kernel found is used.
The Lacie OS is not designed to increment capacity. It has only been sold with 5 disks inside, and with the OS already installed. The only designed user action is to exchange a single broken disk by a new one.
but especially if you do not want to create raid there is a way to have 5 hd 1 tb as if they were in a cascade sepa
You should find a user manual, but I think the Lacie OS doesn't support anything else than raid5.
If you want a seperate volume on each disk, you'll need an other OS. You could ask fvdw for help. He has designed an alternate OS for Lacie boxes, which has this capabilities. AFAIK he has no OS for the 5Big, but the Edmini_v2 is supported, which has the same processor, and the 5Big2 is also supported, which has 5 disks. So I *think* it's just a matter of some minor additions to the kernel. But I can be wrong.