User Tools

Site Tools


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:20] – fixed links 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 [[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. 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.
Line 13: Line 14:
   $ ./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 87: Line 88:
   $ ./clunc -i ${NAS_IP}   $ ./clunc -i ${NAS_IP}
  
-  * mainlineLinux support: +  * Edit U-Boot env variables (don'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 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.1304702409.txt.gz · Last modified: 2011/05/06 19:20 by 199.208.239.141