lacie 5 big network v.1 please support for fvdw

[taetae]

my 5 big.JPG

left labeled as one




the partition used for os lacie is the sdb7,

the partition table used is that of the os lacie and the dd command created by you has been put sdb6 like you said

hd 500gb used was empty and to act as a test for you

excuse for English use google translate

[fvdw]

I see

normally a disk inserted in slot 1 is recognized as sda vy u-boot, the one in slot 2 as sdb and so on.
The fact that u-boot finds a disk as device 4 indicates that you inserted the test dik in slot 5. You should use for the moment slot 1.

Attached a new trial kernel, this one should support the pci-sata of the 5big1. Interesting will be the serial console output.
In addition


Tonight I will also compile a standalone kernel that will run from RAM. this could be used with the fvdw-sl console running under windows and connecting to the 5big1 using telnet. If that works and the kernel runs ok and recognizes the dik(s) then we can proceed to install the fvdw-sl firmware using the fvdw-sl console and auto install script.
The kernel has support for net console so we can also load it with u-boot and enabling netconsole output. Then you will get same output in u-boot console as you get now on the serial console ;)

[taetae]

16 settembre coming soon ;-)

[taetae]

September 16 is approaching: -) I can not wait to try

;)

[fvdw]

:tapfoot ...we are waiting

[taetae]

here I am and here is the result of the console ......

loading only the kernel sdb 6
give you a yes to the question?

I'm here to other passages ;) _ _

Code: Select all

        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** LOADER **
 ** MARVELL BOARD: RD-88F5281-LaCie LE

U-Boot 1.1.4 (Jun 26 2008 - 16:55:41) Marvell version: 2.4.9

U-Boot code: 00200000 -> 0026FFF0  BSS: -> 00283280

Soc: 88F5281 D0 (DDR2)
CPU running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  32bit width
[4096kB@ffc00000] Flash:  4 MB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done
*** Warning - bad CRC, using default environment


CPU : ARM926 (Rev 0)
Streaming disabled
VFP initialized to Run Fast Mode.

USB 0: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: PCI-X, speed = 66000000
CPU: Write allocate Disabled
Net:   egiga0 [PRIME]
POWER ON
Hit any key to stop autoboot:  0
Waiting for LUMP (5)
no lump receive; continuing

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
  Device 4: OK
Model: WDC WD5000AADS-00S9B0                    Firm: 01.00A01 Ser#:      WD-WCAV90478832
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)


** Device 0 not available

** Device 1 not available

** Device 2 not available

** Device 3 not available

Loading from IDE device 4, partition 10: Name: hde10
  Type: U-Boot

** Bad Magic Number **

** Device 0 not available

** Device 1 not available

** Device 2 not available

** Device 3 not available

Loading from IDE device 4, partition 6: Name: hde6
  Type: U-Boot
   Image Name:   Linux-2.6.39.4
   Created:      2013-08-28  21:39:43 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1864076 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2013-08-28  21:39:43 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1864076 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.39.4 (root@fvdwsl-5big2.local) (gcc version 4.5.4 (GCC) ) #8 PREEMPT Wed Aug 28 22:39:19 GMT+1 2013
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: LaCie 5Big1 Network
Clearing invalid memory bank 0KB@0x00000000
Clearing invalid memory bank 0KB@0x00000000
Clearing invalid memory bank 0KB@0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro boardType=mv88F5281 productType=5Big reset=0
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 126000k/126000k available, 5072k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xc8800000 - 0xfd800000   ( 848 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0028000   ( 128 kB)
      .text : 0xc0028000 - 0xc03a3000   (3564 kB)
      .data : 0xc03a4000 - 0xc03bf9e0   ( 111 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:64
sched_clock: 32 bits at 166MHz, resolution 5ns, wraps every 25769ms
Calibrating delay loop... 498.89 BogoMIPS (lpj=2494464)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Orion ID: MV88F5281-D0. TCLK=166666667.
Orion: Applying 5281 D0 WFI workaround.
net5big: powering up SATA drives
net5big: turning off power-off control GPIO
net5big: Flash writing is not yet supported.
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
pci 0000:01:07.0: BAR 0: assigned [mem 0xe8000000-0xe80fffff 64bit]
pci 0000:01:07.0: BAR 0: set to [mem 0xe8000000-0xe80fffff 64bit] (PCI address [0xe8000000-0xe80fffff])
pci 0000:01:07.0: BAR 2: assigned [io  0x100000-0x1000ff]
pci 0000:01:07.0: BAR 2: set to [io  0x100000-0x1000ff] (PCI address [0x100000-0x1000ff])
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
Switched to NOHz mode on CPU #0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 246
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
loop: module loaded
Uniform Multi-Platform E-IDE driver
ide-gd driver 1.18
sata_mv 0000:01:07.0: version 1.28
sata_mv 0000:01:07.0: Gen-II 32 slots 8 ports SCSI mode IRQ via INTx
scsi0 : sata_mv
scsi1 : sata_mv
scsi2 : sata_mv
scsi3 : sata_mv
scsi4 : sata_mv
scsi5 : sata_mv
scsi6 : sata_mv
scsi7 : sata_mv
ata1: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8022000 irq 52
ata2: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8024000 irq 52
ata3: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8026000 irq 52
ata4: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8028000 irq 52
ata5: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8032000 irq 52
ata6: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8034000 irq 52
ata7: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8036000 irq 52
ata8: SATA max UDMA/133 mmio m1048576@0xe8000000 port 0xe8038000 irq 52
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 5
scsi8 : sata_mv
scsi9 : sata_mv
scsi10 : sata_mv
scsi11 : sata_mv
scsi12 : sata_mv
ata9: SATA max UDMA/133 irq 29
ata10: SATA max UDMA/133 irq 29
ata11: SATA max UDMA/133 irq 29
ata12: SATA max UDMA/133 irq 29
ata13: SATA max UDMA/133 irq 29
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address 00:d0:4b:8b:60:2b
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
usbcore: registered new interface driver ipheth
console [netcon0] enabled
netconsole: network logging started
aoe: AoE v47 initialised.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
input: gpio-keys as /devices/platform/gpio-keys/input/input0
i2c /dev entries driver
rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.6
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
at24 0-0050: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor mv_xor.0: Self-test copy failed compare, disabling
mv_xor mv_xor.1: Self-test copy failed compare, disabling
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1968 buckets, 7872 max)
IPv4 over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 5
ata1: SATA link down (SStatus 0 SControl 300)
NET: Registered protocol family 37
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
rtc-rs5c372 0-0032: setting system clock to 2013-09-17 08:55:33 UTC (1379408133)
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata9: failed to resume link (SControl 0)
ata9: SATA link down (SStatus 0 SControl 0)
ata4: SATA link down (SStatus 0 SControl 300)
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
ata5.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/133
scsi 4:0:0:0: Direct-Access     ATA      WDC WD5000AADS-0 01.0 PQ: 0 ANSI: 5
sd 4:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 > sda2
sda: p2 size 3905021043 extends beyond EOD, enabling native capacity
 sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 > sda2
sda: p2 size 3905021043 extends beyond EOD, truncated
sd 4:0:0:0: [sda] Attached SCSI disk
ata6: SATA link down (SStatus 0 SControl 300)
ata7: SATA link down (SStatus 0 SControl 300)
ata8: SATA link down (SStatus 0 SControl 300)
ata10: failed to resume link (SControl 0)
ata10: SATA link down (SStatus 0 SControl 0)
ata11: failed to resume link (SControl 0)
ata11: SATA link down (SStatus 0 SControl 0)
ata12: failed to resume link (SControl 0)
ata12: SATA link down (SStatus 0 SControl 0)
ata13: failed to resume link (SControl 0)
ata13: SATA link down (SStatus 0 SControl 0)
EXT3-fs: barriers not enabled
EXT3-fs (sda7): mounted filesystem with ordered data mode
kjournald starting.  Commit interval 5 seconds
VFS: Mounted root (ext3 filesystem) readonly on device 8:7.
Freeing init memory: 128K
/sbin/init: /sbin/init: 187: cannot create /dev/console: Read-only file system
/sbin/init: /sbin/init: 187: cannot create /dev/console: Read-only file system
/sbin/init: /sbin/init: 187: cannot create /dev/console: Read-only file system
mount: /etc/mtab: Read-only file system
/sbin/init: /sbin/init: 187: cannot create /dev/console: Read-only file system
mount: /etc/mtab: Read-only file system
/sbin/init: /sbin/init: 187: cannot create /dev/console: Read-only file system
===BOOTFS: Mounting /dev/pts
mount: /etc/mtab: Read-only file system
===BOOTFS: Mounting /dev/shm
mount: /etc/mtab: Read-only file system
sed: /proc/edmini: No such file or directory
===BOOTFS: Verifying MAC address
ifconfig: egiga0: error fetching interface information: Device not found
===BOOTFS: Could not determine MAC address
===BOOTFS: FAILED verifyMacAddress
sed: /proc/edmini: No such file or directory
sed: /proc/edmini: No such file or directory
===BOOTFS: Preparing swap partition /dev/sda5
sed: /proc/edmini: No such file or directory
===BOOTFS: Preparing snapshot partition /dev/sda9
EXT3-fs: barriers not enabled
EXT3-fs (sda8): mounted filesystem with ordered data mode
kjournald starting.  Commit interval 5 seconds
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda9): using internal journal
EXT3-fs (sda9): mounted filesystem with ordered data mode
sed: /proc/edmini: No such file or directory
===BOOTFS: Preparing userdata partition /dev/sda2
EXT3-fs: barriers not enabled
EXT3-fs (sda8): mounted filesystem with ordered data mode
kjournald starting.  Commit interval 5 seconds
===BOOTFS: Failure: Module /var/original/lib/modules/2.6.39.4/kernel/fs/xfs/xfs.ko not found
===BOOTFS: FAILED prepareUserDataPartition
===BOOTFS: ####### Writing first_boot signature in /dev/sda #######
sed: /proc/edmini: No such file or directory
===BOOTFS: ####### signing all devices with unknown  #######
sed: /proc/edmini: No such file or directory
===BOOTFS: #### Running File System Check on Snapshot Partition (/dev/sda9) ###
e2fsck 1.37 (21-Mar-2005)
/dev/sda9: clean, 46/84480 files, 6801/168674 blocks
#### Starting PatchManager using /dev/sda8 and /dev/sda9  ####
mount: Mounting /dev/sda8 on /var/original failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda8
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda9): using internal journal
EXT3-fs (sda9): mounted filesystem with ordered data mode
===BOOTFS: Creating base union /var/base from /var/original
mount: Mounting unionfs on /var/base failed: No such device
===BOOTFS: Loading snapshots from /snapshots/snaps
mount: Mounting none on /var/base failed: Invalid argument
mkdir: Cannot create directory `oldroot': Read-only file system
pivot_root: pivot_root: No such file or directory
===BOOTFS: =======================================BOOTFS=================================
===BOOTFS: Initializing filesystem
===BOOTFS: Mounting /proc
mount: Mounting none on /proc failed: Device or resource busy
===BOOTFS: Unable to mount /proc
===BOOTFS: Mounting /sys
mount: Mounting none on /sys failed: Device or resource busy
===BOOTFS: Unable to mount /sys
===BOOTFS: Populating /dev
===BOOTFS: Mounting /dev/pts
mount: /etc/mtab: Read-only file system
===BOOTFS: Mounting /dev/shm
mount: /etc/mtab: Read-only file system
sed: /proc/edmini: No such file or directory
sed: /proc/edmini: No such file or directory
===BOOTFS: #### Running File System Check on Snapshot Partition (/dev/sda9) ###
e2fsck 1.37 (21-Mar-2005)
/dev/sda9 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)?

for loop question y / n

Code: Select all


WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? y
yes

/dev/sda9: recovering journal
/dev/sda9: clean, 46/84480 files, 6801/168674 blocks
#### Starting PatchManager using /dev/sda8 and /dev/sda9  ####
mount: Mounting /dev/sda8 on /var/original failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda8
mount: Mounting /dev/sda9 on /snapshots failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda9
===BOOTFS: Creating base union /var/base from /var/original
mount: Mounting unionfs on /var/base failed: No such device
===BOOTFS: Loading snapshots from /snapshots/snaps
mount: Mounting none on /var/base failed: Invalid argument
mkdir: Cannot create directory `oldroot': Read-only file system
pivot_root: pivot_root: No such file or directory
===BOOTFS: =======================================BOOTFS=================================
===BOOTFS: Initializing filesystem
===BOOTFS: Mounting /proc
mount: Mounting none on /proc failed: Device or resource busy
===BOOTFS: Unable to mount /proc
===BOOTFS: Mounting /sys
mount: Mounting none on /sys failed: Device or resource busy
===BOOTFS: Unable to mount /sys
===BOOTFS: Populating /dev
===BOOTFS: Mounting /dev/pts
mount: /etc/mtab: Read-only file system
===BOOTFS: Mounting /dev/shm
mount: /etc/mtab: Read-only file system
sed: /proc/edmini: No such file or directory
sed: /proc/edmini: No such file or directory
===BOOTFS: #### Running File System Check on Snapshot Partition (/dev/sda9) ###
e2fsck 1.37 (21-Mar-2005)
/dev/sda9 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? y
yes

/dev/sda9: clean, 46/84480 files, 6801/168674 blocks
#### Starting PatchManager using /dev/sda8 and /dev/sda9  ####
mount: Mounting /dev/sda8 on /var/original failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda8
mount: Mounting /dev/sda9 on /snapshots failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda9
===BOOTFS: Creating base union /var/base from /var/original
mount: Mounting unionfs on /var/base failed: No such device
===BOOTFS: Loading snapshots from /snapshots/snaps
mount: Mounting none on /var/base failed: Invalid argument
mkdir: Cannot create directory `oldroot': Read-only file system
pivot_root: pivot_root: No such file or directory
===BOOTFS: =======================================BOOTFS=================================
===BOOTFS: Initializing filesystem
===BOOTFS: Mounting /proc
mount: Mounting none on /proc failed: Device or resource busy
===BOOTFS: Unable to mount /proc
===BOOTFS: Mounting /sys
mount: Mounting none on /sys failed: Device or resource busy
===BOOTFS: Unable to mount /sys
===BOOTFS: Populating /dev
===BOOTFS: Mounting /dev/pts
mount: /etc/mtab: Read-only file system
===BOOTFS: Mounting /dev/shm
mount: /etc/mtab: Read-only file system
sed: /proc/edmini: No such file or directory
sed: /proc/edmini: No such file or directory
===BOOTFS: #### Running File System Check on Snapshot Partition (/dev/sda9) ###
e2fsck 1.37 (21-Mar-2005)
/dev/sda9 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? y
yes

/dev/sda9: clean, 46/84480 files, 6801/168674 blocks
#### Starting PatchManager using /dev/sda8 and /dev/sda9  ####
mount: Mounting /dev/sda8 on /var/original failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda8
mount: Mounting /dev/sda9 on /snapshots failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda9
===BOOTFS: Creating base union /var/base from /var/original
mount: Mounting unionfs on /var/base failed: No such device
===BOOTFS: Loading snapshots from /snapshots/snaps
mount: Mounting none on /var/base failed: Invalid argument
mkdir: Cannot create directory `oldroot': Read-only file system
pivot_root: pivot_root: No such file or directory
===BOOTFS: =======================================BOOTFS=================================
===BOOTFS: Initializing filesystem
===BOOTFS: Mounting /proc
mount: Mounting none on /proc failed: Device or resource busy
===BOOTFS: Unable to mount /proc
===BOOTFS: Mounting /sys
mount: Mounting none on /sys failed: Device or resource busy
===BOOTFS: Unable to mount /sys
===BOOTFS: Populating /dev
===BOOTFS: Mounting /dev/pts
mount: /etc/mtab: Read-only file system
===BOOTFS: Mounting /dev/shm
mount: /etc/mtab: Read-only file system
sed: /proc/edmini: No such file or directory
sed: /proc/edmini: No such file or directory
===BOOTFS: #### Running File System Check on Snapshot Partition (/dev/sda9) ###
e2fsck 1.37 (21-Mar-2005)
/dev/sda9 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? y
yes

/dev/sda9: clean, 46/84480 files, 6801/168674 blocks
#### Starting PatchManager using /dev/sda8 and /dev/sda9  ####
mount: Mounting /dev/sda8 on /var/original failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda8
mount: Mounting /dev/sda9 on /snapshots failed: Device or resource busy
===BOOTFS: systemInitialize: Failed to mount /dev/sda9
===BOOTFS: Creating base union /var/base from /var/original
mount: Mounting unionfs on /var/base failed: No such device
===BOOTFS: Loading snapshots from /snapshots/snaps
mount: Mounting none on /var/base failed: Invalid argument
mkdir: Cannot create directory `oldroot': Read-only file system
pivot_root: pivot_root: No such file or directory
===BOOTFS: =======================================BOOTFS=================================
===BOOTFS: Initializing filesystem
===BOOTFS: Mounting /proc
mount: Mounting none on /proc failed: Device or resource busy
===BOOTFS: Unable to mount /proc
===BOOTFS: Mounting /sys
mount: Mounting none on /sys failed: Device or resource busy
===BOOTFS: Unable to mount /sys
===BOOTFS: Populating /dev
===BOOTFS: Mounting /dev/pts
mount: /etc/mtab: Read-only file system
===BOOTFS: Mounting /dev/shm
mount: /etc/mtab: Read-only file system
sed: /proc/edmini: No such file or directory
sed: /proc/edmini: No such file or directory
===BOOTFS: #### Running File System Check on Snapshot Partition (/dev/sda9) ###
e2fsck 1.37 (21-Mar-2005)
/dev/sda9 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)?


[fvdw]

:bananadance well the kernel seems to be loaded without a problem, it detects now the hard disk and tries to load the Lacie firmware.
The loading of the lacie firmware is now the problem, it seems to fail because our kernel is so to see not suitable for the Lacie firmware, so to see it needs dedicated process build into kernel like /proc/edmini

Code: Select all

<snip>
kjournald starting.  Commit interval 5 seconds
VFS: Mounted root (ext3 filesystem) readonly on device 8:7.
Freeing init memory: 128K
/sbin/init: /sbin/init: 187: cannot create /dev/console: Read-only file system

<snip>


The freeing int message indactes that loading of the kernel is completed.

The lacie firmware seems to have mounted the the rootfs as readonly, then of course some problems will arise when trying to executed the commands in the init script...

To be analyzed in more detail this evening, I am now ar work


I would not say yes on the question to perform the e2fsck because the file sysem is mounted . If you want to do that umount it first.

Further why do you still try to load the lacie firmware ? Think you should go now for the fvdw-sl firmware :whistle
That means preapare a disk with our paration structure and firmware.
Then probably evrything will be up and running.

ps How many disks were in the box when booting the kernel ?

[taetae]

only one disk 500gb


for the preparation dedicated to your firmware then you will give me advice ..... step to step

[fvdw]

ok now that this seems to work I will compile a standalone kernel so we can use the fvdw-sl console to do the preparation of the disk
However I have an internet connection issue right now, I hope this will be sorted soon, this message is sent via mobile phone

If you cannot wiat then you could follow the manualy first time install guide for the isp1 (and edmini_v2). The only thing you will need to change iin this procedure and package is writing the kernel I have sent you to sda6 instead of the kernel for the isp1 as present in the package.
For this manual install you need to take out the disk and connect it via usb/sata interface to a PC running linux.

[fvdw]

check you pm box, the trial standalone kernel for 5big1 is posted there

Unpack it the tftp folder of the fvdw-sl console (were also the one for the nwsp2 is).
Switch off you 5big1. Put a disk in slot 1 of the 5big1 that you want to prepare, start the fvdw-sl console on your windows PC. Choose as action load standalone kernel. Pick in the window that pops the standalone kernel for 5big1, switch on the 5big1. The console should detect it and interrupt boot, upload the kernel and it will start a telnet client.Wait until you can log on with the telnet client. I Don't know how long it takes to load the standalone kernel, if it takes longer then 12 seconds the telnet client may not be able to connect, so if it fails to connect wait a little longer and try agin to connect (use menu in telnet client). If can connect perform a dmesg and post output here.

If everything is ok than switch off the 5big1 (you can use poweroff -f in the telnet client). Close the telnet client and choose in the fvdw-sl console now install fvdw-sl firmware, it will ask for a standalone kernel, pick the the one for the 5big1 and for the rest pretend you have a nwsp2. It will upload and start some command windows, answer the questions. When it is done with installing do not reboot as now the wrong kernel is present in sda6. Replace it by uploading the 5big1 kernel I have sent you two weeks ago. To do this put it in the tftp folder of the fvdw-sl console.
And type in the telnet windo the command (replace in this command ip-pc by the actual ip address of your pc running the fvdw-sl console, it is displayed in the fvdw-sl console window)

Code: Select all

tftp -r UIMAGE-26394-5BIG1-5-TRIAL -l /UIMAGE-26394-5BIG1-5-TRIAL -g ip-pc

(The tfp server of the fvdw-sl console should be still running)
If the kernel is uploaded write it to sda6

Code: Select all

dd if=/UIMAGE-26394-5BIG1-5-TRIAL of=/dev/sda6

After this you are ready, reboot (use reboot -f in the telnet client) and see if it comes up, after a while you should be able to find it in the LAN