Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
sanboot:debian_and_ubuntu [2007/10/24 19:30] curs0r |
sanboot:debian_and_ubuntu [2007/12/12 03:02] bengen added some details about troubleshooting |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Debian or Ubuntu ====== | ====== Debian or Ubuntu ====== | ||
- | |||
- | |||
- | |||
- | |||
- | |||
===== Preparing an existing installation for AoE ===== | ===== Preparing an existing installation for AoE ===== | ||
Line 150: | Line 145: | ||
Note that this setup still requires the scripts provided on this page, the creation of /etc/fstab, and the creation of /boot/grub/menu.lst. Some users may have difficulty using Gnome unless they add '' iface lo inet loopback'' and ''auto lo'' to /etc/network/interfaces. Always make certain to run ''update-initramfs -c -k all -v'' after any changes to keep your system booting happily. When you are finished creating/customizing /etc/fstab, /boot/grub/menu.lst and /etc/network/interfaces you will have a basic bootable image suitable for reuse. Setting up a new client is as simple as: copy the image, use vblade to make the new image available, mount the image, edit the specifics (ie: /boot/grub/menu.lst, /etc/hosts, etc) then boot from your new client. Once you have booted this basic image, making it a full system is as simple as apt-get install ubuntu-desktop, ubuntu-server, xubuntu-desktop, kubuntu-desktop, or whichever you choose. | Note that this setup still requires the scripts provided on this page, the creation of /etc/fstab, and the creation of /boot/grub/menu.lst. Some users may have difficulty using Gnome unless they add '' iface lo inet loopback'' and ''auto lo'' to /etc/network/interfaces. Always make certain to run ''update-initramfs -c -k all -v'' after any changes to keep your system booting happily. When you are finished creating/customizing /etc/fstab, /boot/grub/menu.lst and /etc/network/interfaces you will have a basic bootable image suitable for reuse. Setting up a new client is as simple as: copy the image, use vblade to make the new image available, mount the image, edit the specifics (ie: /boot/grub/menu.lst, /etc/hosts, etc) then boot from your new client. Once you have booted this basic image, making it a full system is as simple as apt-get install ubuntu-desktop, ubuntu-server, xubuntu-desktop, kubuntu-desktop, or whichever you choose. | ||
+ | ==== Troubleshooting ==== | ||
- | ==== Hint ==== | + | It is possible to get a shell in Debian's and Ubuntu's initial |
- | * If the system hangs before the root device has been mounted, passing ''break=mount'' on the command line will spawn a shell before ''scripts/local-top/aoetools'' is run. This should allow for further debugging. | + | ramdisks at various stages by passing ''debug=<WHEN>'' to the kernel. |
+ | For debugging issues related to a boot device not being found, | ||
+ | ''debug=mount'' is probably most useful. | ||
+ | See ''initramfs-tools(8)'' for further details. | ||
+ | Things to look out for include: | ||
+ | |||
+ | * Has the driver for the NIC been loaded? | ||
+ | * Is the interface "up"? | ||
+ | * Has the ''aoe'' kernel module ben loaded? | ||
+ | * Does ''/dev/aoe/'' exist, does it contain the necessary entries? | ||
==== Scripts ==== | ==== Scripts ==== | ||
Line 217: | Line 222: | ||
esac | esac | ||
</code> | </code> | ||
- | |||
- | ===== Preparing an existing installation for iSCSI ===== | ||
- | TBD | ||