[SOLVED] Upgraded from squeeze to wheezy. Hard disk list is backwards.
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Some more google'ing I found some people talking about drive letters are assigned on a first come, first serve basis. I booted back into the previous kernel, 2.6.32 and did a lsmod. Here are the last 20 or so lines.
MD software raid has its own metadata for recognizing raid members and building groups, this should work without your intervention.
Grub and Lilo require a little help, you should be using either labels or UUID strings in the grub configuration and in fstab ot make sure the correct drive partitions mount as you need them. The device order is really irrelevant if you have everything else set up properly.
Device migration/shifting has been a problem since udev was new, and all of the problems have been functionally resolved. Alas, that does NOT mean resolved by letting the operator decide how to allocate the device names, rather by making the device names less relevant.
Ok, Only reason I was concerned with this was I was running CentOS prior to switching back to Debian. I had the same issue as I have here. Every time I would add a drive to expand my array, It would throw off the drive letters and break the raid. Then I would have to rebuild the raid prior to adding in the new drive. It was very time consuming to say the least.
If this wont be a problem here, I'll just leave it.
Here are my mdadm.conf,fstab and grub files. Do they look set up properly as to not cause an issue?
mdadm.conf
Code:
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR ***********@gmail.com
# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 UUID=58ad9cae:e1e82031:fcfde786:ba99b399 name=Mega-Nas:0
# This file was auto-generated on Sun, 22 Jan 2012 13:12:36 -0500
# by mkconf 3.1.4-1+8efb9d1
fstab
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=624d1796-f87e-4a09-a6b5-9fd36c8cc117 / ext3 errors=remount-ro 0 1
/dev/scd1 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd0 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/scd1 /media/floppy0 auto rw,user,noauto 0 0
UUID=56ffd1ad-fd59-458e-9a69-c6a42aa126c0 /mnt/home ext4 defaults 0 0
grub.cfg
Code:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 624d1796-f87e-4a09-a6b5-9fd36c8cc117
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 624d1796-f87e-4a09-a6b5-9fd36c8cc117
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.2.0-1-amd64' --class debian --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 624d1796-f87e-4a09-a6b5-9fd36c8cc117
echo 'Loading Linux 3.2.0-1-amd64 ...'
linux /boot/vmlinuz-3.2.0-1-amd64 root=UUID=624d1796-f87e-4a09-a6b5-9fd36c8cc117 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-1-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.2.0-1-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 624d1796-f87e-4a09-a6b5-9fd36c8cc117
echo 'Loading Linux 3.2.0-1-amd64 ...'
linux /boot/vmlinuz-3.2.0-1-amd64 root=UUID=624d1796-f87e-4a09-a6b5-9fd36c8cc117 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-1-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 624d1796-f87e-4a09-a6b5-9fd36c8cc117
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=624d1796-f87e-4a09-a6b5-9fd36c8cc117 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 624d1796-f87e-4a09-a6b5-9fd36c8cc117
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=624d1796-f87e-4a09-a6b5-9fd36c8cc117 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
I just wanted to add that I installed a new 2tb disk today. Everything worked fine and the raid didn't break. Added the new drive to the array and its reshaping fine. Thanks!
Lesson learned. As long as You use the UUID's in those 3 files, drive lettering, as previously mentioned, is irrelevant.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
