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 18:51] – formatting 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 78: Line 79:
   [ snip ]   [ snip ]
  
-======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}
  
-  * Fix machine ID:+  * Edit U-Boot env variables (don't do this if you use the fix_id kernel):
  
   Marvell>> setenv arcNumber 2342   Marvell>> setenv arcNumber 2342
Line 109: 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 115: 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 180: Line 181:
   [ snip ]   [ snip ]
  
-  * Log into the installer:+====Log into the installer====
  
 First, you need to guess the installer address IP (delivred by a DHCP server). You could use tools like **dhcpdump**. Example: First, you need to guess the installer address IP (delivred by a DHCP server). You could use tools like **dhcpdump**. Example:
Line 208: 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 ===
  
Line 238: Line 242:
 Providing that an internet connection is available, installation of the kernel is as simple as: Providing that an internet connection is available, installation of the kernel is as simple as:
  
-====== 2Big Network 2 ======+==== 2Big Network 2 ====
  
   wget ftp://lacie-nas.org/kernel/kirkwood/uImage_2.6.38-rc4_kirkwood_lacie_miniroot -O /dev/sda6   wget ftp://lacie-nas.org/kernel/kirkwood/uImage_2.6.38-rc4_kirkwood_lacie_miniroot -O /dev/sda6
   wget ftp://lacie-nas.org/kernel/kirkwood/uImage_2.6.38-rc4_kirkwood_lacie_miniroot -O /dev/sdb6   wget ftp://lacie-nas.org/kernel/kirkwood/uImage_2.6.38-rc4_kirkwood_lacie_miniroot -O /dev/sdb6
  
-====== 2Big Network ======+==== 2Big Network ====
  
   * If using the regular kernel   * If using the regular kernel
Line 487: Line 491:
  
   * Depending the LaCie U-Boot version, the **savenv** command could fail: as a solution you can use a [[ftp://lacie-nas.org/kernel/uImage-arm-orion-lacie-net2big-fix-id-2.6.38-rc4-miniroot|a dedicated net2big kernel image]] with machine ID set to 526 (Marvell LSP unique number for all the customer boards).   * Depending the LaCie U-Boot version, the **savenv** command could fail: as a solution you can use a [[ftp://lacie-nas.org/kernel/uImage-arm-orion-lacie-net2big-fix-id-2.6.38-rc4-miniroot|a dedicated net2big kernel image]] with machine ID set to 526 (Marvell LSP unique number for all the customer boards).
 +  * If you are having problems with fix ID or made a mistake in the environment run
 +  resetenv
installdebian2big.1304700668.txt.gz · Last modified: 2011/05/06 18:51 by 199.208.239.141