General NAS-Central Forums

Welcome to the NAS community
It is currently Fri Dec 15, 2017 6:37 am

All times are UTC




Post new topic Reply to topic  [ 41 posts ]  Go to page Previous  1, 2, 3  Next
Author Message
PostPosted: Fri Aug 23, 2013 10:39 am 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
knoppix live cd okay to create the whole or do you recommend another?

ps I have to upload as written here?


lacie.nas-central.org/wiki/Installing_firmware_on_fresh_disks_(2Big_2)


I only need one disc?

  I have a western digital 500gb sata 2 32mb cache code WD5000AADS

I also have a sawed barracuda 250 gb


Top
 Profile  
 
PostPosted: Fri Aug 23, 2013 1:02 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Knoppix is fine, and yes, the 2Big2 instructions are a good startpoint as explained in the readme provided with the partition dumps.

Quote:
I only need one disc?
To start with, yes. The box, and especially the firmware , is designed to use 5 disks. So far I don't know how the box, and especially the firmware, will react on a single disk.


Top
 Profile  
 
PostPosted: Fri Aug 23, 2013 1:08 pm 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
ok I burn knoppix and let you know this is the part where I may find difficulty magiore "recreation partitions"

I thank you again for your time and help you're giving me


Top
 Profile  
 
PostPosted: Fri Aug 23, 2013 3:33 pm 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
then started downloaded knoppix 7.2 mdadm, dd and gparted

connected 250gb hd with gparted sawn and I saw how it was called (/ dev / sdb (232.88GiB)

now how I proceed?? to Vevo tried to enter the flat with dd dump:

Code:
root@Microknoppix:/home/knoppix# dd if=/home/knoppix/Desktop/2008221.img of=//dev/sdb
2008221+0 records in
2008221+0 records out
1028209152 bytes (1.0 GB) copied, 59.5491 s, 17.3 MB/s
root@Microknoppix:/home/knoppix#


but gparted sees me sdb 232.88 GiB unallocated

give me the commands to recreate the whole thing?? alone can not sorry


I promise that at the end of it all a lighthouse in-depth guide to the 5 big network





----------------------------------
ps:



after a day where I could not are almost nothing by itself

I noticed that if you have an image of the filesystem you can see a little something to do with the commands that can be serial data ....

Code:
   
FSdel   - del a file from the Flash MV FS
FSdir   - ls the Flash MV FS
FSformat- format the Flash MV FS
FSlef   - Load an exe file to the Flash MV FS
FSlf    - Load a file to the Flash MV FS
FSrun   - Load an exe file from the Flash MV FS and run it
FStftp  - tftp a file to the Flash MV FS
FStftpe - tftp an exe file to the Flash MV FS
FStype  - cat file from the Flash MV FS
base    - print or set address offset
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm   - boot application image from memory
bootp   - boot image via network using BootP/TFTP protocol
bootvx  - Boot vxWorks from an ELF image
bubt    - Burn an image on the Boot Flash.
chpart  - change active partition
cmp     - memory compare
cmpm    - Compare Memory
coninfo - print console devices and information
cp      - memory copy
cpumap - Display CPU memory mapping settings.
crc32   - checksum calculation
date    - get/set/reset date & time
dclk    - Display the MV device CLKs.
dhcp    - invoke DHCP client to obtain IP/boot params
diskboot- boot from IDE device
dma     - Perform DMA
echo    - echo args to console
eeprom  - EEPROM sub-system
erase   - erase FLASH memory
exit    - exit script
fi      - Find value in the memory.
flinfo  - print FLASH memory information
fsinfo  - print information about filesystems
fsload  - load binary file from a filesystem image
g       - start application at cached address 'addr'(default addr 0x40000)
go      - start application at address 'addr'
help    - print online help
icrc32  - checksum calculation
ide     - IDE sub-system
iloop   - infinite loop on address range
imd     - i2c memory display
imm     - i2c memory modify (auto-incrementing)
imw     - memory write (fill)
inm     - memory modify (constant address)
iprobe  - probe to discover valid I2C chip addresses
ir      - reading and changing MV internal register values.
ln      - Load S-Record executable file through the network interface.
loads   - load S-Record file over serial line
loop    - infinite loop on address range
ls      - list files in a directory (default /)
lump    - Wait for a LUMP
map     - Diasplay address decode windows
md      - memory display
me      - PCI master enable
mm      - memory modify (auto-incrementing)
mp      - map PCI BAR
mtdparts- define flash/nand partitions
mtest   - simple RAM test
mw      - memory write (fill)
nm      - memory modify (constant address)
pci     - list and access PCI Configuration Space
phyRead - Read PCI-E Phy register
pciePhyWrite    - Write PCI-E Phy register
phyRead - Read Phy register
phyWrite        - Write Phy register
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
reset   - Perform RESET of the CPU
resetenv        - Return all environment variable to default.
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
se      - PCI Slave enable
setenv  - set environment variables
sg      - scanning the PHYs status
sleep   - delay execution for some time
sp      - Scan PCI bus.
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
version - print monitor version
wol     - Enter Wake On LAN mode


Mijzelf am I wrong?


Last edited by taetae on Sun Aug 25, 2013 7:29 am, edited 1 time in total.

Top
 Profile  
 
PostPosted: Fri Aug 23, 2013 9:32 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
As far as I can see the way you wrote the flat dump is right. Is it possible that gparted works on cached data?

What does
Code:
fdisk -l /dev/sdb
say?

Your listing of commands are the commands of u-boot, the bootloader. This bootloader is in flash memory, and it's task is to load the Linux kernel from sd[abcde]6, and boot it. But as you can see it can do much more.


Top
 Profile  
 
PostPosted: Fri Aug 23, 2013 11:35 pm 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
Code:
root@Microknoppix:/home/knoppix# fdisk -l /dev/sdb

Disk /dev/sdb: 250.1 GB, 250058268160 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488395055 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: 0x00019071

   Device Boot      Start         End      Blocks   Id  System
root@Microknoppix:/home/knoppix#


===============================================
in the night and I thought reviewing the command I did cos = and tabbella [ok I guess right?
Code:
root@Microknoppix:/home/knoppix# dd if=/home/knoppix/Desktop/2008221.img of=//dev/sdb
2008221+0 records in
2008221+0 records out
1028209152 bytes (1.0 GB) copied, 64.5037 s, 15.9 MB/s
root@Microknoppix:/home/knoppix# fdisk -l /dev/sdb
Disk /dev/sdb: 250.1 GB, 250058268160 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488395055 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: 0x000f26c1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63     2008124     1004031    5  Extended
/dev/sdb2         2008125  3907029167  1952510521+  83  Linux
/dev/sdb5             126      257039      128457   82  Linux swap / Solaris
/dev/sdb6          257103      273104        8001   83  Linux
/dev/sdb7          273168      289169        8001   83  Linux
/dev/sdb8          289233      642599      176683+  83  Linux
/dev/sdb9          642663     1992059      674698+  83  Linux
/dev/sdb10        1992123     2008124        8001   83  Linux
root@Microknoppix:/home/knoppix#


Things to do next?? tanks tanks tanks


ps ; known that the start and end are different from the guide (2big2) is normal?


Top
 Profile  
 
PostPosted: Sat Aug 24, 2013 7:59 am 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
under construction under construction

Tutorial 5big networks v1 creazione disco boot Thank Mijzelf that made this possible for your patience, help and time spent

SERIAL JTAG
Attachment:
JTAG.png

J29 POINT



Copy table and Create patitions
Code:
root@Microknoppix:/home/knoppix# dd if=/home/knoppix/Desktop/2008221.img of=//dev/sdb
2008221+0 records in
2008221+0 records out
1028209152 bytes (1.0 GB) copied, 64.5037 s, 15.9 MB/s


Create partitions
Code:
root@Microknoppix:/home/knoppix# fdisk -l /dev/sdb
Disk /dev/sdb: 250.1 GB, 250058268160 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488395055 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: 0x000f26c1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63     2008124     1004031    5  Extended
/dev/sdb2         2008125  3907029167  1952510521+  83  Linux
/dev/sdb5             126      257039      128457   82  Linux swap / Solaris
/dev/sdb6          257103      273104        8001   83  Linux
/dev/sdb7          273168      289169        8001   83  Linux
/dev/sdb8          289233      642599      176683+  83  Linux
/dev/sdb9          642663     1992059      674698+  83  Linux
/dev/sdb10        1992123     2008124        8001   83  Linux
root@Microknoppix:/home/knoppix#


sdb5
Code:
root@Microknoppix:/home/knoppix# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb5 missing --metadata=0.90
mdadm: /dev/sdb5 appears to be part of a raid array:
    level=raid1 devices=5 ctime=Sat Apr 21 15:23:49 2012
Continue creating array? y
mdadm: array /dev/md0 started.
root@Microknoppix:/home/knoppix# mkswap -f /dev/md0
Setting up swapspace version 1, size = 128380 KiB
no label, UUID=3dfbc0d5-7b1e-460d-9551-17c853d39f97
root@Microknoppix:/home/knoppix# mdadm --stop /dev/md0
mdadm: stopped /dev/md0


sdb7
Code:
root@Microknoppix:/home/knoppix# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb7 missing --metadata=0.90
mdadm: /dev/sdb7 appears to contain an ext2fs file system
    size=7936K  mtime=Sat Apr 21 15:28:33 2012
mdadm: /dev/sdb7 appears to be part of a raid array:
    level=raid1 devices=5 ctime=Sat Apr 21 15:26:33 2012
Continue creating array? y
mdadm: array /dev/md0 started.
root@Microknoppix:/home/knoppix# mke2fs -j /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Etichetta del filesystem=
OS type: Linux
Dimensione blocco=1024 (log=0)
Dimensione frammento=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
1984 inodes, 7936 blocks
396 blocks (4.99%) reserved for the super user
Primo blocco dati=1
Maximum filesystem blocks=8126464
1 block group
8192 blocchi per gruppo, 8192 frammenti per gruppo
1984 inode per gruppo

Allocating group tables: fatto                           
Scrittura delle tavole degli inode: fatto                           
Creating journal (1024 blocks): fatto
Scrittura delle informazioni dei superblocchi e dell'accounting del filesystem: fatto

root@Microknoppix:/home/knoppix# mkdir /tmp/md0
root@Microknoppix:/home/knoppix# mount /dev/md0 /tmp/md0
root@Microknoppix:/home/knoppix# cd /tmp/md0
root@Microknoppix:/tmp/md0# tar xjf /home/knoppix/Desktop/Principale/sda7.tar.bz2
root@Microknoppix:/tmp/md0# cd ..
root@Microknoppix:/tmp# umount /tmp/md0
root@Microknoppix:/tmp# mdadm --stop /dev/md0
mdadm: stopped /dev/md0


sdb8
Code:
root@Microknoppix:/tmp# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb8 missing --metadata=0.90
mdadm: /dev/sdb8 appears to contain an ext2fs file system
    size=176576K  mtime=Sat Apr 21 15:35:08 2012
mdadm: /dev/sdb8 appears to be part of a raid array:
    level=raid1 devices=5 ctime=Sat Apr 21 15:34:10 2012
Continue creating array? y
mdadm: array /dev/md0 started.
root@Microknoppix:/tmp# mke2fs -j /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Etichetta del filesystem=
OS type: Linux
Dimensione blocco=1024 (log=0)
Dimensione frammento=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
44176 inodes, 176576 blocks
8828 blocks (5.00%) reserved for the super user
Primo blocco dati=1
Maximum filesystem blocks=67371008
22 gruppi di blocchi
8192 blocchi per gruppo, 8192 frammenti per gruppo
2008 inode per gruppo
Backup del superblocco salvati nei blocchi:
   8193, 24577, 40961, 57345, 73729

Allocating group tables: fatto                           
Scrittura delle tavole degli inode: fatto                           
Creating journal (4096 blocks): fatto
Scrittura delle informazioni dei superblocchi e dell'accounting del filesystem: fatto

root@Microknoppix:/tmp# mount /dev/md0 /tmp/md0
root@Microknoppix:/tmp# cd /tmp/md0
root@Microknoppix:/tmp/md0# tar xjf /home/knoppix/Desktop/Principale/sda8.tar.bz2
root@Microknoppix:/tmp/md0# cd ..
root@Microknoppix:/tmp# umount /tmp/md0
root@Microknoppix:/tmp# mdadm --stop /dev/md0
mdadm: stopped /dev/md0


sdb9
Code:
root@Microknoppix:/tmp# cd ..
root@Microknoppix:/# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb9 missing --metadata=0.90
mdadm: /dev/sdb9 appears to contain an ext2fs file system
    size=674624K  mtime=Thu Jan  1 01:00:00 1970
mdadm: /dev/sdb9 appears to be part of a raid array:
    level=raid1 devices=5 ctime=Sat Apr 21 15:39:09 2012
Continue creating array? y
mdadm: array /dev/md0 started.
root@Microknoppix:/# mke2fs -j /dev/md0
mke2fs 1.42.5 (29-Jul-2012)
Etichetta del filesystem=
OS type: Linux
Dimensione blocco=4096 (log=2)
Dimensione frammento=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
42240 inodes, 168656 blocks
8432 blocks (5.00%) reserved for the super user
Primo blocco dati=0
Maximum filesystem blocks=176160768
6 gruppi di blocchi
32768 blocchi per gruppo, 32768 frammenti per gruppo
7040 inode per gruppo
Backup del superblocco salvati nei blocchi:
   32768, 98304, 163840

Allocating group tables: fatto                           
Scrittura delle tavole degli inode: fatto                           
Creating journal (4096 blocks): fatto
Scrittura delle informazioni dei superblocchi e dell'accounting del filesystem: fatto

root@Microknoppix:/# mdadm --stop /dev/md0
mdadm: stopped /dev/md0


sdb2
Code:
root@Microknoppix:/# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb2 missing --metadata=0.90
mdadm: array /dev/md0 started.
root@Microknoppix:/# mkfs.xfs /dev/md0
mkfs.xfs: /dev/md0 appears to contain an existing filesystem (xfs).
mkfs.xfs: Use the -f option to force overwrite.
root@Microknoppix:/# mkfs.xfs -f /dev/md0
meta-data=/dev/md0               isize=256    agcount=4, agsize=15199584 blks
         =                       sectsz=512   attr=2, projid32bit=0
data     =                       bsize=4096   blocks=60798336, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal log           bsize=4096   blocks=29686, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
root@Microknoppix:/# mdadm --stop /dev/md0
mdadm: stopped /dev/md0

sdb6
Code:
root@Microknoppix:/# gzip -cd /home/knoppix/Desktop/Principale/sda6.gz | dd of=/dev/sdb6
16002+0 record dentro
16002+0 record fuori
8193024 byte (8,2 MB) copiati, 24,764 s, 331 kB/s

sdb10
Code:
root@Microknoppix:/# dd if=/dev/zero of=/dev/sdb10
dd: scrittura di "/dev/sdb10": Spazio esaurito sul device
16003+0 record dentro
16002+0 record fuori
8193024 byte (8,2 MB) copiati, 24,6113 s, 333 kB/s


You do not have the required permissions to view the files attached to this post.


Last edited by taetae on Sun Aug 25, 2013 7:49 am, edited 8 times in total.

Top
 Profile  
 
PostPosted: Sat Aug 24, 2013 8:07 am 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
Marvell U-boot for serial

Code:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ 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


Comand list u-boot

Code:
   
FSdel   - del a file from the Flash MV FS
FSdir   - ls the Flash MV FS
FSformat- format the Flash MV FS
FSlef   - Load an exe file to the Flash MV FS
FSlf    - Load a file to the Flash MV FS
FSrun   - Load an exe file from the Flash MV FS and run it
FStftp  - tftp a file to the Flash MV FS
FStftpe - tftp an exe file to the Flash MV FS
FStype  - cat file from the Flash MV FS
base    - print or set address offset
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm   - boot application image from memory
bootp   - boot image via network using BootP/TFTP protocol
bootvx  - Boot vxWorks from an ELF image
bubt    - Burn an image on the Boot Flash.
chpart  - change active partition
cmp     - memory compare
cmpm    - Compare Memory
coninfo - print console devices and information
cp      - memory copy
cpumap - Display CPU memory mapping settings.
crc32   - checksum calculation
date    - get/set/reset date & time
dclk    - Display the MV device CLKs.
dhcp    - invoke DHCP client to obtain IP/boot params
diskboot- boot from IDE device
dma     - Perform DMA
echo    - echo args to console
eeprom  - EEPROM sub-system
erase   - erase FLASH memory
exit    - exit script
fi      - Find value in the memory.
flinfo  - print FLASH memory information
fsinfo  - print information about filesystems
fsload  - load binary file from a filesystem image
g       - start application at cached address 'addr'(default addr 0x40000)
go      - start application at address 'addr'
help    - print online help
icrc32  - checksum calculation
ide     - IDE sub-system
iloop   - infinite loop on address range
imd     - i2c memory display
imm     - i2c memory modify (auto-incrementing)
imw     - memory write (fill)
inm     - memory modify (constant address)
iprobe  - probe to discover valid I2C chip addresses
ir      - reading and changing MV internal register values.
ln      - Load S-Record executable file through the network interface.
loads   - load S-Record file over serial line
loop    - infinite loop on address range
ls      - list files in a directory (default /)
lump    - Wait for a LUMP
map     - Diasplay address decode windows
md      - memory display
me      - PCI master enable
mm      - memory modify (auto-incrementing)
mp      - map PCI BAR
mtdparts- define flash/nand partitions
mtest   - simple RAM test
mw      - memory write (fill)
nm      - memory modify (constant address)
pci     - list and access PCI Configuration Space
phyRead - Read PCI-E Phy register
pciePhyWrite    - Write PCI-E Phy register
phyRead - Read Phy register
phyWrite        - Write Phy register
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
reset   - Perform RESET of the CPU
resetenv        - Return all environment variable to default.
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
se      - PCI Slave enable
setenv  - set environment variables
sg      - scanning the PHYs status
sleep   - delay execution for some time
sp      - Scan PCI bus.
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
version - print monitor version
wol     - Enter Wake On LAN mode


sdb2 261 gib xfs? I can use it as a storage partition base formated in ext3?


Last edited by taetae on Sun Aug 25, 2013 7:30 am, edited 3 times in total.

Top
 Profile  
 
PostPosted: Sat Aug 24, 2013 10:12 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
First conclusion is the the box is running OK. Disk is recognized, kernel loaded and booted, only the init script is a problem.

Quote:
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:
Code:
do_initramfs_init()
{
    debug_msg "=======================================INITRAMFS================================"

    local l_productRaidUUIDList
    local l_candidateRank

    initFileSystem

    # 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`"
    firstBoot=`isFirstBoot $firstDisk`

    # 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.
        #============================================================
   checkForFirmwareUpdate "$firstDisk"

        # Ok, since we returned, we can now wait for all the devices
        #===========================================================
        waitForDevices
    fi
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.

Quote:
I tried it and actually post the interface part...
Are you saying that you put in 4 disks, and that the booting continued?
Quote:
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:
Code:
echo 5Big | dd of=/dev/sdb seek=3

Quote:
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.
Quote:
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.


Top
 Profile  
 
PostPosted: Sat Aug 24, 2013 10:23 am 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
excellent ....

have managed to get him;-)
interface imagazzina data turned off, and if they are connected 5 5 hd hd otherwise he wants to be in the loop;-) now I've made ​​you want to use the device in such a way as to have dale 10 tb separated from each other which steps should I take to be able to use another system?



given that we can create with the dd command a perfect copy of the primary partitions so that with a simple command (dd) to integrate it on any hd (and the remainder of the disk format it manually) so you can also have hd 3tb that with the dd command clones the ext3 partition and example 2.5 tb ....


so that everyone can usufruir are unfamiliar with your work! I thank you again so much for the advice you give to all of us

with the boot hd is 350 gb .... I can not exploit the remaining part as a share?? or gives me a default for 680 mb ... as a place to set the remaining part?


Top
 Profile  
 
PostPosted: Sat Aug 24, 2013 3:32 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
I'm sorry, don't understand what you are trying to say. Can you rephrase it?


Top
 Profile  
 
PostPosted: Sat Aug 24, 2013 6:01 pm 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
1. hd where I created the boot partition is 250 gb first started I create a shared folder 680 mb, all other gb how can I recover them?

2. if I can create only with lacie os raid (raid 0 raid 1 etc) I'd get the chance to try other systems that allowed me to use all of the 5 tb hard .. example 5x2tb 10TB always

3.with the dd command you can clone hd taking only the partitions that we have created together so that with a single command we have a copy of the partitions ....

example
1 hd: 320 gb
  copy partitions sdb1 2 3 4 6 7 9 ........
in 2tb hd clone and the remaining space partition share

I hope I have written better :-)... tanks


ps : ntfs read only, begins to dislike so much this os

edminiv2 not work

serial:

Code:
Uncompressing Linux......................................................................................................... done, booting the kernel.


stop .....

kernel 5big and partition edminiv2


Starting kernel ...

Code:
Uncompressing Linux......................................................................................................... done, booting the kernel.
Linux version 2.6.22.7 (root@grp-iminea-lnx) (gcc version 4.2.1) #1 Mon Oct 18 13:18:49 UTC 2010
CPU: ARM926EJ-S [41069260] revision 0 (ARMv5TEJ), cr=00053177
Machine: Feroceon
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Built 1 zonelists.  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: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 126464KB available (2804K code, 186K data, 356K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Sys Clk = 166666667, Tclk = 166666667
Orion2 D0 or less. Enable VFP.

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 128MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e0000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
PCI0_MEM ....base e8000000, size 128MB
PCI0_IO ....base f2100000, size   1MB
INTER_REGS ....base f1000000, size   1MB
DEVICE_CS0 ....no such
DEVICE_CS1 ....no such
DEVICE_CS2 ....no such
DEV_BOOCS ....base f4000000, size  16MB

  Marvell Development Board (LSP Version 3.0.5_NAS_GDP_p8)-- DB-88F5281-LaCie  Soc: 88F5281 D0

 Detected Tclk 166666667 and SysClk 166666667
Init Marvell USB port 0 => HOST
Marvell USB EHCI Host controller #0: c0495600
PCI: bus0: Fast back to back transfers enabled
PCI: bus1: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: orion_clocksource clocksource has been installed.
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
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Registering unionfs 2.4 (for 2.6.22.19)
io scheduler noop registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 4) is a 16550A
Marvell Ethernet Driver 'mv_ethernet':
  o Uncached descriptors in DRAM
  o DRAM SW cache-coherency
  o TCP segmentation offload enabled
  o Checksum offload enabled
  o Marvell ethtool proc enabled
  o Rx desc: 128
  o Tx desc: 256
  o Loading network interface 'egiga0'
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi2 : Marvell SCSI to SATA adapter
scsi3 : Marvell SCSI to SATA adapter
scsi4 : Marvell SCSI to SATA adapter
scsi5 : Marvell SCSI to SATA adapter
scsi6 : Marvell SCSI to SATA adapter
scsi7 : Marvell SCSI to SATA adapter
scsi 4:0:0:0: Direct-Access     WDC      WD5000AADS-00S9B 01.0 PQ: 0 ANSI: 5
sd 4:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
sd 4:0:0:0: [sde] Write Protect is off
sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 4:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
sd 4:0:0:0: [sde] Write Protect is off
sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
 sde: sde1 < sde5 sde6 sde7 sde8 sde9 sde10 > sde2
sd 4:0:0:0: [sde] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg0 type 0
cfi_flash_0: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
cfi_flash_0: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
ehci_marvell ehci_marvell.4523: Marvell Orion EHCI
ehci_marvell ehci_marvell.4523: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.4523: irq 17, io base 0xf1050100
ehci_marvell ehci_marvell.4523: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1     28 MB/s
raid6: int32x2     39 MB/s
raid6: int32x4     51 MB/s
raid6: int32x8     44 MB/s
raid6: using algorithm int32x4 (51 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
   arm4regs  :   429.200 MB/sec
   8regs     :   386.400 MB/sec
   32regs    :   428.000 MB/sec
raid5: using function: arm4regs (429.200 MB/sec)
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
Loading I2C based RTC driver device interface.
Found TWSI-I2C with id: 0
Found I2C RTC rs5c372 @ 0x32
Freeing init memory: 356K
===INITRAMFS: =======================================INITRAMFS================================
===INITRAMFS: Initializing filesystem
===INITRAMFS: Mounting /proc
===INITRAMFS: Mounting /sys
===INITRAMFS: Populating /dev
===INITRAMFS: Mounting /dev/pts
===INITRAMFS: Product ID = '5Big'
===INITRAMFS: minRaidDevices=4
===INITRAMFS: maxRaidDevices=5
===INITRAMFS: Waiting for the master disk to spin up
===INITRAMFS: Waiting for 1 to 1 disks to spin up
===INITRAMFS: We finally have 1 disks, updating /dev
===INITRAMFS: Found available BootFS partition: /dev/sde7
===INITRAMFS: Normal boot, starting bootfs system array
mdadm: No md superblock detected on /dev/sde7.
===INITRAMFS: Device '/dev/sde7' is not valid. Select another one.
mdadm: No md superblock detected on /dev/sde7.
===INITRAMFS: Device '/dev/sde7' is not valid too. Select next one.
===INITRAMFS: Warning: No valid device for this product. A claim is necessary...
===INITRAMFS: =========FIND AND CLAIM A COMPATIBLE DEVICE=========
===INITRAMFS: Signature for device '/dev/sde' = '5Big'
mdadm: No md superblock detected on /dev/sde7.
mdadm: No md superblock detected on /dev/sde8.
mdadm: No md superblock detected on /dev/sde9.
mdadm: No md superblock detected on /dev/sde2.
mdadm: No md superblock detected on /dev/sde7.
===INITRAMFS: Device '/dev/sde' has not active boot partition : REJECTED
===INITRAMFS: No valid bootfs found!


BusyBox v1.9.2 (2010-10-18 13:09:24 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.

# help

Built-in commands:
-------------------
        . : [ [[ alias break cd chdir continue echo eval exec exit export
        false hash help let local pwd read readonly return set shift
        source test times trap true type ulimit umask unalias unset wait


# ls
bin   dev   init  lib   proc  root  sbin  sys   usr


Top
 Profile  
 
PostPosted: Sun Aug 25, 2013 1:43 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Quote:
1. hd where I created the boot partition is 250 gb first started I create a shared folder 680 mb, all other gb how can I recover them?
You mean your first disk is only 250 GB, appointing the size of all raid members, while other disks are bigger?
The Lacie OS has no support for that, but I suppose it is possible to create an extra partition on it, and mount it on a share, using some user script. Advanced option.
Quote:
2. if I can create only with lacie os raid (raid 0 raid 1 etc) I'd get the chance to try other systems that allowed me to use all of the 5 tb hard .. example 5x2tb 10TB always
That is a question?
Quote:
3.with the dd command you can clone hd taking only the partitions that we have created together so that with a single command we have a copy of the partitions ....
Yes, you can use dd to create a lowlevel copy of a prepared disk, and then use fdisk to put a partition in the remaining space. With some simple script is should be possible to add that partition to the available space (as a seperate volume).
Quote:
ps : ntfs read only, begins to dislike so much this os
Yeah, this OS is old. Reliable ntfs support for Linux is younger. Fvdw's OS could perform better, here.
Quote:
edminiv2 not work
Seeing the bootlog, I guess the bootscript absolutely wants the rootfs (sdx7) to be a raidmember, which is not the case for the edmini.

BTW, it's a bummer that the edmini kernel doesn't boot. That lowers the chance that fvdw's firmware will run with only minor adjustments.


Top
 Profile  
 
PostPosted: Sun Aug 25, 2013 2:09 pm 
Offline

Joined: Thu Aug 22, 2013 5:55 am
Posts: 24
Mijzelf wrote:
Quote:
1. hd where I created the boot partition is 250 gb first started I create a shared folder 680 mb, all other gb how can I recover them?
You mean your first disk is only 250 GB, appointing the size of all raid members, while other disks are bigger?
The Lacie OS has no support for that, but I suppose it is possible to create an extra partition on it, and mount it on a share, using some user script. Advanced option.
Quote:
2. if I can create only with lacie os raid (raid 0 raid 1 etc) I'd get the chance to try other systems that allowed me to use all of the 5 tb hard .. example 5x2tb 10TB always
That is a question?
Quote:
3.with the dd command you can clone hd taking only the partitions that we have created together so that with a single command we have a copy of the partitions ....
Yes, you can use dd to create a lowlevel copy of a prepared disk, and then use fdisk to put a partition in the remaining space. With some simple script is should be possible to add that partition to the available space (as a seperate volume).
Quote:
ps : ntfs read only, begins to dislike so much this os
Yeah, this OS is old. Reliable ntfs support for Linux is younger. Fvdw's OS could perform better, here.
Quote:
edminiv2 not work
Seeing the bootlog, I guess the bootscript absolutely wants the rootfs (sdx7) to be a raidmember, which is not the case for the edmini.

BTW, it's a bummer that the edmini kernel doesn't boot. That lowers the chance that fvdw's firmware will run with only minor adjustments.


1.at the moment I do not have to boot from drives larger than 250 gb 500gb and a blank one that I'm not using

syul boot disk does not detect gb but only defaul a share from 980 mb, I can take advantage of the remaining portion (example: 200gb)?
1.1 if you can use, how?

2.which operating system I use to have 10 tb without raid?

3. help me to create a clone of HD with the dd command?

4.I can use some other operating system that will let me use all the hd will buy without raid?
and I can use hd 3 tb or there are constraints?


Top
 Profile  
 
PostPosted: Sun Aug 25, 2013 7:06 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Quote:
1.at the moment I do not have to boot from drives larger than 250 gb 500gb and a blank one that I'm not using

syul boot disk does not detect gb but only defaul a share from 980 mb, I can take advantage of the remaining portion (example: 200gb)?
1.1 if you can use, how?
You can use fdisk to create a partition on it. That will be primary partition 3.
Code:
fdisk /dev/sda
Then you can put a filesystem on it: (Assuming the disk is sda)
Code:
mke2fs -j /dev/sda3
, and mount it on a share. At the moment I don't know where the shares are located, but it is something like
Code:
mount /dev/sda3 /path/to/share
A complicating factor is that this mounting has to be done after the data raid array is assembled and mounted. So some script has to be injected to the OS.

Quote:
2.which operating system I use to have 10 tb without raid?
4.I can use some other operating system that will let me use all the hd will buy without raid?
As far as I know there are no off-the-shell OSses for this box, other than the Lacie one.
- Using the GPL kernel it is relatively easy to install Debian Lenny on it, which is a quite mature, but outdated OS. It gives you shell access, but you'll have to configure it from the commandline. There is no GUI. (Although it is possible to install one)
Unfortunately the GPL kernel doesn't support a more modern OS.
- As I said before, there is also fvdw-sl, some home-brown OS, from which you can see a sample here. It supports separate volumes on different disks, and AFAIK support for raid arrays is planned for the near future.
To get this on your NAS, some effort from fvdw is needed, as AFAIK he has no support (yet) for the 5Big.
Quote:
and I can use hd 3 tb or there are constraints?
Using the Lacie OS, no. Using Debian Lenny on the GPL kernel, I'm not sure. Using a new kernel, yes, but with some problems. The bootdisk needs to have an MBR partition table, as the bootloader doesn't support anything else. So the bootdisk has to <=2TB. But the other disks can be as big as the kernel supports. (Which is >3TB)
Quote:
3. help me to create a clone of HD with the dd command?
Code:
dd if=/dev/sda of=/dev/sdb bs=1M
Where sda is the source disk, and sdb the target. Of course these values can be different in your case.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 41 posts ]  Go to page Previous  1, 2, 3  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group