Installing stock Debian with debootstrap

Elite_Gamer04 · 03-10-2010, 05:34 AM

Good afternoon,

Hoping this is the correct forum to be posting in, this is my current dillema:

I have a dedicated server with 2xSSD and 2xSATA drives currently installed - I've made both into Raid0 - MD1 = SSD /Boot, MD2 = SSD /, MD0 is simply the SATA.

I'm wanting to install my OS (and main programs) onto my SSD drives and use SATA for Storage/Data - however my provider only provides modified and crippled (in my opinion) versions of OS's and as such want to install 'Stock' Debian.

I've read into this and over the last few days played around with 'debootstrap' - however having some difficulties. I found a helpful script at:

http://rimuhosting.com/knowledgebase...ng-debootstrap

I found out the hard way that I can't install debian onto a running parition (in my case my SSDs) so I've setup a parition (single SATA drive - SDC1) to install Stock Debian to, then boot off that and install BACK onto the SSD (messy but think its the only way no?).

However after entering all the commands I wish (release, chroot path etc) I am recieving the following errors towards the end of the script:

Code:

Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-amd64
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
mdadm: cannot open /dev/md1: No such file or directory
mdadm: cannot open /dev/md2: No such file or directory
mdadm: cannot open /dev/md0: No such file or directory
W: mdadm: You appear to be missing µe from /etc/mdadm/mdadm.conf !
W: mdadm: If this array is required to boot, you must add the following line:
W: mdadm: ARRAY µe UUID=b1fac491:316c1eed:bb011a32:4c9f007f
W: mdadm: You appear to be missing /dev/.tmp.md2 from /etc/mdadm/mdadm.conf !
W: mdadm: If this array is required to boot, you must add the following line:
W: mdadm: ARRAY /dev/.tmp.md2 UUID=f57ffe90:89e07b93:a4d2adc2:26fd5302
W: mdadm: You appear to be missing /dev/.tmp.md1 from /etc/mdadm/mdadm.conf !
W: mdadm: If this array is required to boot, you must add the following line:
W: mdadm: ARRAY /dev/.tmp.md1 UUID=3b8333c1:72855bae:a4d2adc2:26fd5302
mv: cannot stat `/etc/apt/sources.list.dt': No such file or directory
Setting the password on the chroot distro
debootstrap.sh: line 379: cd: /raid/boot: No such file or directory
ls: cannot access /boot/vmlinuz*-bigmem: No such file or directory
ls: cannot access /boot/vmlinuz*-server: No such file or directory
ls: cannot access /boot/vmlinuz*-amd64: No such file or directory
* Unable to find kernel version. Set one manually.
debootstrap.sh: line 404: /usr/bin/replace: No such file or directory
debootstrap.sh: line 405: /usr/bin/replace: No such file or directory
debootstrap.sh: line 406: /usr/bin/replace: No such file or directory
debootstrap.sh: line 407: /usr/bin/replace: No such file or directory
debootstrap.sh: line 408: /usr/bin/replace: No such file or directory
grep: /etc/modprobe.conf: No such file or directory
* Install complete. Check the output below before rebooting.
Configured network interfaces:
auto lo
  iface lo inet loopback

auto eth0
  iface eth0 inet static
  address xxx.xxx.xxx.xxx
  netmask xxx.xxx.xxx.xxx
# broadcast
  gateway xxx.xxx.xxx.xxx
GRUB:
cat: /boot/grub/grub.conf: No such file or directory
/etc/fstab:
/dev/md1        /boot   ext4    errors=remount-ro       0       1
/dev/sdc1       /       ext3            defaults        1 1
/dev/sdb3 swap swap defaults 0 0
/dev/sda3 swap swap defaults 0 0
* Warning: No eth0 found in /mnt/etc/modprobe.d/aliases /mnt/etc/modprobe.conf /mnt/etc/modules. Make sure you add one before rebooting.

The first time round I figured that the crappy 'custom' kernel my provider provides is crippled without modular support (which it was), so I rebuilt with latest 2.6.33 kernel, module support enabled - but STILL returned the above error.

To me it seems things are getting mixed with MD1 (my SSD) and my SDC1 etc - ideas?

Cheers