LaCie NAS wiki

User Tools

Site Tools

Trace:
installdebian2big

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
installdebian2big [2011/05/06 19:11] – resetenv 199.208.239.141installdebian2big [2012/02/21 15:03] (current) – 93.104.155.24
Line 4: Line 4:
  
 ===== Boot custom installer ===== ===== Boot custom installer =====
-In the following process, you should replace ${NAS_IP} and ${SERVER_IP} with correct IPs regarding your network configuration.+In the following process, you should replace ${NAS_IP} with correct IP regarding your network configuration. 
 +${ipaddr} and ${serverip} are automatically set by clunc.
  
 ====2Big Network 2==== ====2Big Network 2====
-* Connect to U-Boot using network console with [[CLUNC|clunc]]:+  * Connect to U-Boot using network console with [[CLUNC|clunc]]:
  
-As a preliminary step, you must export the installer [[http://lacie-nas.org/kernel/uImage-arm-orion-lacie-2.6.38-rc4-miniroot|image]] via a **tftp** server. U-Boot will use this way to load the installer image into RAM.+As a preliminary step, you must export the installer [[ftp://lacie-nas.org/kernel/kirkwood/uImage_2.6.38-rc4_kirkwood_lacie_miniroot|image]] via a **tftp** server. U-Boot will use this way to load the installer image into RAM.
  
   $ ./clunc -i ${NAS_IP}   $ ./clunc -i ${NAS_IP}
  
-  Marvell>> setenv ipaddr ${NAS_IP}; setenv serverip ${SERVER_IP}; tftpboot 0x800000 uImage +  Marvell>> setenv ipaddr ${ipaddr}; setenv serverip ${serverip}; tftpboot 0x800000 uImage 
-  setenv ipaddr ${NAS_IP}; setenv serverip ${SERVER_IP}; tftpboot 0x800000 uImage+  setenv ipaddr ${ipaddr}; setenv serverip ${serverip}; tftpboot 0x800000 uImage
   Using egiga0 device   Using egiga0 device
-  TFTP from server ${SERVER_IP}; our IP address is ${NAS_IP}+  TFTP from server ${serverip}; our IP address is ${ipaddr}
   Filename 'uImage'.   Filename 'uImage'.
   Load address: 0x800000   Load address: 0x800000
Line 29: Line 30:
   Bytes transferred = 2031132 (1efe1c hex)   Bytes transferred = 2031132 (1efe1c hex)
  
-* Boot installer:+  * Boot installer:
  
   Marvell>> setenv bootargs ip=dhcp console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/   Marvell>> setenv bootargs ip=dhcp console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/
Line 79: Line 80:
  
 ====2Big Network==== ====2Big Network====
-A minimal system can be used to prepare disks and to install Debian distribution. A such sytem (kernel+initramfs) is available [[http://lacie-nas.org/kernel/uImage-arm-orion-lacie-2.6.38-rc4-miniroot|here]]. The initramfs only embed enssential software: busybox, mdadm and mke2fs. Note that the total image size (kernel+initramfs) must not exceed 2MB. The LaCie stock U-Boot is not able to load images largest than 2MB.+A minimal system can be used to prepare disks and to install Debian distribution. A such sytem (kernel+initramfs) is available [[ftp://lacie-nas.org/kernel/orion/uImage_2.6.38-rc4_orion_lacie_miniroot|standard image]] or [[ftp://lacie-nas.org/kernel/orion/uImage_2.6.38-rc4_orion_lacie_net2big_fix_id_miniroot|Fixed ID image]]. The initramfs only embed enssential software: busybox, mdadm and mke2fs. Note that the total image size (kernel+initramfs) must not exceed 2MB. The LaCie stock U-Boot is not able to load images largest than 2MB.
  
  
Line 87: Line 88:
   $ ./clunc -i ${NAS_IP}   $ ./clunc -i ${NAS_IP}
  
-  * mainlineLinux support: +  * Edit U-Boot env variables (don't do this if you use the fix_id kernel):
- +
-  Marvell>> setenv mainlineLinux yes +
-  setenv mainlineLinux yes +
-  Marvell>> saveenv +
-  saveenv +
-  Saving Environment to Flash... +
-  . +
-  Un-Protected 1 sectors +
-  Erasing Flash... +
-  . done +
-  Erased 1 sectors +
-  Writing to Flash... done +
-  . +
-  Protected 1 sectors +
-  Marvell>> reset +
-  reset +
- +
-  * Fix machine ID: +
-Only do this if you are using the fixed ID kernel+
  
   Marvell>> setenv arcNumber 2342   Marvell>> setenv arcNumber 2342
Line 128: Line 110:
   * Load installer image:   * Load installer image:
  
-As a preliminary step, you must export the installer [[http://lacie-nas.org/kernel/uImage-arm-orion-lacie-2.6.38-rc4-miniroot|image]] via a **tftp** server. U-Boot will use this way to load the installer image into RAM.+As a preliminary step, you must export the installer [[ftp://lacie-nas.org/kernel/orion/uImage_2.6.38-rc4_orion_lacie_miniroot|standard image]] or [[ftp://lacie-nas.org/kernel/orion/uImage_2.6.38-rc4_orion_lacie_net2big_fix_id_miniroot|Fixed ID image]]  via a **tftp** server. U-Boot will use this way to load the installer image into RAM.
  
   $ ./clunc -i ${NAS_IP}   $ ./clunc -i ${NAS_IP}
Line 134: Line 116:
   Waiting for LUMP (0)   Waiting for LUMP (0)
   no lump receive; continuing   no lump receive; continuing
-  Marvell>> setenv ipaddr ${NAS_IP}; setenv serverip ${SERVER_IP}; tftpboot 0x400000 uImage +  Marvell>> setenv ipaddr ${ipaddr}; setenv serverip ${serverip}; tftpboot 0x400000 uImage 
-  setenv ipaddr ${NAS_IP}; setenv serverip ${SERVER_IP}; tftpboot 0x400000 uImage+  setenv ipaddr ${ipaddr}; setenv serverip ${serverip}; tftpboot 0x400000 uImage
   Using egiga0 device   Using egiga0 device
-  TFTP from server ${SERVER_IP}; our IP address is ${NAS_IP}+  TFTP from server ${serverip}; our IP address is ${ipaddr}
   Filename 'uImage'.   Filename 'uImage'.
   Load address: 0x400000   Load address: 0x400000
Line 227: Line 209:
 ===== Partition Disks ===== ===== Partition Disks =====
 Using a custom debian installation on the 2BigNetwork allows great flexibility with the partition structure.  The only caveat is that the kernel _must_ be on partition 6 of one or both of the drives, usually both to make the drives swappable.  The startup of the initial ram fs will search for a root filesystem on all RAID and regular disk partitions, and if one is found, will switch to it and complete the boot sequence from there. Using a custom debian installation on the 2BigNetwork allows great flexibility with the partition structure.  The only caveat is that the kernel _must_ be on partition 6 of one or both of the drives, usually both to make the drives swappable.  The startup of the initial ram fs will search for a root filesystem on all RAID and regular disk partitions, and if one is found, will switch to it and complete the boot sequence from there.
 +
 +If you didn't change the //bootargs// variable in U-Boot, the rootfs must be on partition 7.
  
 Use the supplied **fdisk** to partition the disk.  An example scheme is below Use the supplied **fdisk** to partition the disk.  An example scheme is below
 +
 ==== Running on a single 500GB disk with no RAID === ==== Running on a single 500GB disk with no RAID ===
  
installdebian2big.1304701872.txt.gz · Last modified: by 199.208.239.141

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
GNU Free Documentation License 1.3 Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki