Tell me more ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.
up vote 0 down vote favorite

I've added a new disk in a hurry and now I have several mismatches. Would anyone care to help me to sort them out. Below I'm giving fstab, fdisk -l, df -la (apparently "/" (root) is duplicated ??, etc.). I also enclose relevant sections from /var/log/system and grub

The system works without apparent problems but I do not have a clear correspondence between disks sda, sdb. sdc and directories / , /run/, etc. I would like to establish correspondence (and, e.g., have only sda, sdb, and sdc in fstab, and have only one "/") so as to be able to optimally use the space on the disks and avoid possible duplication of system files. For instance, does the appearance of two "/" mean that systems files are written on both sda and sdb? If so, how can sort that out.

fstab: 

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda1 during installation
UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 /               ext3    errors=remount-ro 0       1
# /home was on /dev/sda3 during installation
UUID=a3cb2cbb-d6db-46e1-a0e7-73f264d255a1 /home           ext3    defaults        0       2
# swap was on /dev/sda2 during installation
UUID=25c7fb6d-47a4-4594-9cfd-20e9680f5e0b none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/sdc3       /windoze        vfat    rw,user,noauto    0       0
/dev/sdc4       /mutant         ext3    defaults,errors=remount-ro 0       1
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

fdisk -l

Disk /dev/sdb: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b1cf4

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048    78125055    39061504   83  Linux
/dev/sdb2        78125056   203124735    62499840   83  Linux
/dev/sdb3       203124736   234440703    15657984   82  Linux swap / Solaris

Disk /dev/sdc: 240.1 GB, 240057409536 bytes
255 heads, 63 sectors/track, 29185 cylinders, total 468862128 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc4c22279

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    7  HPFS/NTFS/exFAT
/dev/sdc2          206848   247676927   123735040    7  HPFS/NTFS/exFAT
/dev/sdc3       247676928   360000000    56161536+   b  W95 FAT32
/dev/sdc4       360000001   468862127    54431063+  83  Linux

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x49382feb

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048    78125055    39061504   83  Linux
/dev/sda2        78125056   203192319    62533632   83  Linux
/dev/sda3       203192320   234440703    15624192   82  Linux swap / Solaris

df -la

Filesystem     1K-blocks     Used Available Use% Mounted on
rootfs          38445384  7493556  28998756  21% /
sysfs                  0        0         0    - /sys
proc                   0        0         0    - /proc
udev               10240        0     10240   0% /dev
devpts                 0        0         0    - /dev/pts
tmpfs            1645524      896   1644628   1% /run
/dev/sda1       38445384  7493556  28998756  21% /
tmpfs               5120        0      5120   0% /run/lock
tmpfs            6415880        0   6415880   0% /run/shm
fusectl                0        0         0    - /sys/fs/fuse/connections
/dev/sda2       61550604  4113240  54310684   8% /home
/dev/sdc4       53575504 32089000  18764952  64% /mutant
rpc_pipefs             0        0         0    - /var/lib/nfs/rpc_pipefs

/var/log/system

Jan 14 14:44:46 BlenderMonster kernel: [    2.602349] scsi 0:0:0:0: Direct-Access     ATA      OCZ-AGILITY3     2.06 PQ: 0 ANSI: 5
Jan 14 14:44:46 BlenderMonster kernel: [    2.605613] scsi 0:0:1:0: CD-ROM            HL-DT-ST DVDRAM GH22NS70  EX00 PQ: 0 ANSI: 5
Jan 14 14:44:46 BlenderMonster kernel: [    2.605979] scsi 1:0:0:0: Direct-Access     ATA      KINGSTON SH100S3 320A PQ: 0 ANSI: 5
Jan 14 14:44:46 BlenderMonster kernel: [    2.606285] scsi 1:0:1:0: Direct-Access     ATA      ADATA SSD S599 2 3.4. PQ: 0 ANSI: 


Jan 14 14:44:46 BlenderMonster kernel: [    2.421387] ata2.00: ATA-8: KINGSTON SH100S3120G, 320ABBF0, max UDMA/133
Jan 14 14:44:46 BlenderMonster kernel: [    2.421392] ata2.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32)
Jan 14 14:44:46 BlenderMonster kernel: [    2.421400] ata2.01: ATA-8: ADATA SSD S599 256GB, 3.4.6, max UDMA/133
Jan 14 14:44:46 BlenderMonster kernel: [    2.421403] ata2.01: 468862128 sectors, multi 16: LBA48 NCQ (depth 0/32)
Jan 14 14:44:46 BlenderMonster kernel: [    2.428910] ata1.00: ATA-9: OCZ-AGILITY3, 2.06, max UDMA/133
Jan 14 14:44:46 BlenderMonster kernel: [    2.428912] ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32)

Jan 14 14:44:46 BlenderMonster kernel: [    2.608483] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
Jan 14 14:44:46 BlenderMonster kernel: [    2.608486] sd 1:0:0:0: [sdb] 234441648 512-byte logical blocks: (120 GB/111 GiB)
Jan 14 14:44:46 BlenderMonster kernel: [    2.608489] sd 1:0:1:0: [sdc] 468862128 512-byte logical blocks: (240 GB/223 GiB)
Jan 14 14:44:46 BlenderMonster kernel: [    2.608544] sd 1:0:0:0: [sdb] Write Protect is off
Jan 14 14:44:46 BlenderMonster kernel: [    2.608546] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jan 14 14:44:46 BlenderMonster kernel: [    2.608555] sd 1:0:1:0: [sdc] Write Protect is off
Jan 14 14:44:46 BlenderMonster kernel: [    2.608558] sd 1:0:1:0: [sdc] Mode Sense: 00 3a 00 00
Jan 14 14:44:46 BlenderMonster kernel: [    2.608567] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 14 14:44:46 BlenderMonster kernel: [    2.608580] sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 14 14:44:46 BlenderMonster kernel: [    2.609127]  sdc: sdc1 sdc2 sdc3 sdc4
Jan 14 14:44:46 BlenderMonster kernel: [    2.609211]  sdb: sdb1 sdb2 sdb3
Jan 14 14:44:46 BlenderMonster kernel: [    2.609423] sd 1:0:0:0: [sdb] Attached SCSI disk
Jan 14 14:44:46 BlenderMonster kernel: [    2.609442] sd 1:0:1:0: [sdc] Attached SCSI disk
Jan 14 14:44:46 BlenderMonster kernel: [    2.617056] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Jan 14 14:44:46 BlenderMonster kernel: [    2.617061] cdrom: Uniform CD-ROM driver Revision: 3.20
Jan 14 14:44:46 BlenderMonster kernel: [    2.617189] sd 0:0:0:0: [sda] Write Protect is off
Jan 14 14:44:46 BlenderMonster kernel: [    2.617192] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jan 14 14:44:46 BlenderMonster kernel: [    2.617205] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

grub.cfg

# 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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
  set locale_dir=($root)/boot/grub/locale
  set lang=en_GB
  insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
insmod png
if background_image /usr/share/images/desktop-base/joy-grub.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 3.2.0-4-amd64 ...'
        linux   /boot/vmlinuz-3.2.0-4-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-3.2.0-4-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 3.2.0-4-amd64 ...'
        linux   /boot/vmlinuz-3.2.0-4-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 ro single
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-3.2.0-4-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.2.0-3-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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 3.2.0-3-amd64 ...'
        linux   /boot/vmlinuz-3.2.0-3-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-3.2.0-3-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.2.0-3-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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 3.2.0-3-amd64 ...'
        linux   /boot/vmlinuz-3.2.0-3-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 ro single
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-3.2.0-3-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.1.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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 3.1.0-1-amd64 ...'
        linux   /boot/vmlinuz-3.1.0-1-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-3.1.0-1-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.1.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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 3.1.0-1-amd64 ...'
        linux   /boot/vmlinuz-3.1.0-1-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 ro single
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-3.1.0-1-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.0.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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 3.0.0-1-amd64 ...'
        linux   /boot/vmlinuz-3.0.0-1-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-3.0.0-1-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.0.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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 3.0.0-1-amd64 ...'
        linux   /boot/vmlinuz-3.0.0-1-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 ro single
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-3.0.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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 2.6.32-5-amd64 ...'
        linux   /boot/vmlinuz-2.6.32-5-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 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 2b4e1ed6-4b09-4c42-a958-9493cffa7f58
        echo    'Loading Linux 2.6.32-5-amd64 ...'
        linux   /boot/vmlinuz-2.6.32-5-amd64 root=UUID=2b4e1ed6-4b09-4c42-a958-9493cffa7f58 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 ###
menuentry "Debian GNU/Linux, with Linux 3.2.0-3-amd64 (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-3.2.0-3-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro quiet
        initrd /boot/initrd.img-3.2.0-3-amd64
}
menuentry "Debian GNU/Linux, with Linux 3.2.0-3-amd64 (recovery mode) (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-3.2.0-3-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro single
        initrd /boot/initrd.img-3.2.0-3-amd64
}
menuentry "Debian GNU/Linux, with Linux 3.2.0-2-amd64 (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-3.2.0-2-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro quiet
        initrd /boot/initrd.img-3.2.0-2-amd64
}
menuentry "Debian GNU/Linux, with Linux 3.2.0-2-amd64 (recovery mode) (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-3.2.0-2-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro single
        initrd /boot/initrd.img-3.2.0-2-amd64
}
menuentry "Debian GNU/Linux, with Linux 3.2.0-1-amd64 (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-3.2.0-1-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro quiet
        initrd /boot/initrd.img-3.2.0-1-amd64
}
menuentry "Debian GNU/Linux, with Linux 3.2.0-1-amd64 (recovery mode) (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-3.2.0-1-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro single
        initrd /boot/initrd.img-3.2.0-1-amd64
}
menuentry "Debian GNU/Linux, with Linux 3.1.0-1-amd64 (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-3.1.0-1-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro quiet
        initrd /boot/initrd.img-3.1.0-1-amd64
}
menuentry "Debian GNU/Linux, with Linux 3.1.0-1-amd64 (recovery mode) (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-3.1.0-1-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro single
        initrd /boot/initrd.img-3.1.0-1-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-5-amd64 (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro quiet
        initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode) (on /dev/sdb1)" --class gnu-linux --class gnu --class os {
        insmod part_msdos
        insmod ext2
        set root='(/dev/sdb,msdos1)'
        search --no-floppy --fs-uuid --set=root 6b3258c6-e97a-4ffc-aa42-2aa04dbccf16
        linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=6b3258c6-e97a-4ffc-aa42-2aa04dbccf16 ro single
        initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry "Windows 7 (loader) (on /dev/sdc1)" --class windows --class os {
        insmod part_msdos
        insmod ntfs
        set root='(/dev/sdc,msdos1)'
        search --no-floppy --fs-uuid --set=root 1E8AE46D8AE442BF
        chainloader +1
}
### 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 ###
share|improve this question
Where do you see sdb as root? sdb is mounted nowhere according to your df output. So put a filesystem on it, mount it and everything will be fine. – scai Jan 14 at 15:03
Ugh! My question is much more involved than that. – erwin Jan 14 at 15:36
I can mount sdb but than I would have everthing duplicated "/"/home" etc. Perhaps, I should be more detailed. sdb is an old disk with an old debian sid on it. But nevertheless is bootable. And I don't know how to sort that out. If I simply reformat sdb than I'm afraid the whole installation would fall appart. If I just erase "/" and "/home" etc. (which become visible when I mount sdb1 and sdb2) than I'm afraid the system might be affected. Most probably not, but I would be grateful for someone's opinion on that. I erased them, the next question would be how to sort out the fstab – erwin Jan 14 at 15:47
Actually, how should I find out from which disk the systems boots sdb or sdc? They both have boot labels. And how can find out whether the system boots from a boot sector outside of the partions or from the beginning of the first partion of the disk. – erwin Jan 14 at 16:47
I could open the box and take sdb out but then sdc would become sdb and it would be a mess. – erwin Jan 14 at 17:07
show 1 more comment

closed as too localized by uther, jasonwryan, Renan, rahmu, warl0ck Jan 15 at 4:00

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.