System goes into rootfs when I add a forth hard drive [SOLVED]

anarcho · 2014-10-11 21:41:28

I have a dual boot setup with Windows 7 as you can see below I can add a third disk fine, but when I try to add a forth disk I get stuck in rootfs as though the forth disk has taken over sdb1

#lsblk -f
NAME   FSTYPE LABEL           UUID                                 MOUNTPOINT
sda                                                                
├─sda1 ntfs   System Reserved 4E08192308190C19                     
└─sda2 ntfs                   CED025F1D025E107                     
sdb                                                                
├─sdb1 ext4                   ef5f655f-3e02-482b-b80e-5676264f4665 /
└─sdb2 ext4                   9b99e3a5-dc67-45fc-ae20-654377044f2b /home
sdc                                                                
├─sdc1                                                             
└─sdc5 ext4   backup          ba7e6049-b53d-4284-affd-c39e976f5b15 /mnt/backup

# blkid
/dev/sdc5: LABEL="backup" UUID="ba7e6049-b53d-4284-affd-c39e976f5b15" TYPE="ext4" PARTUUID="000cb714-05" 
/dev/sda1: LABEL="System Reserved" UUID="4E08192308190C19" TYPE="ntfs" PARTUUID="893af806-01" 
/dev/sda2: UUID="CED025F1D025E107" TYPE="ntfs" PARTUUID="893af806-02" 
/dev/sdb1: UUID="ef5f655f-3e02-482b-b80e-5676264f4665" TYPE="ext4" PARTUUID="fce8c725-01" 
/dev/sdb2: UUID="9b99e3a5-dc67-45fc-ae20-654377044f2b" TYPE="ext4" PARTUUID="fce8c725-02"

This is my /etc/fstab I have comment out the forth drive otherwise the system wouldn't load, I know it has nothing to do with the fact that its ntfs as I switched them around and then backup wouldn't load

#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sdb1
UUID=ef5f655f-3e02-482b-b80e-5676264f4665       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sdb2
UUID=9b99e3a5-dc67-45fc-ae20-654377044f2b       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sdc5
UUID=ba7e6049-b53d-4284-affd-c39e976f5b15       /mnt/backup     ext4            rw,relatime,data=ordered        0 2

# /dev/sdh1
#UUID=A878C84378C811CC                          /mnt/share      ntfs            rw,relatime,data=ordered        0 2

# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Oct 11 21:10 4E08192308190C19 -> ../../sda1
lrwxrwxrwx 1 root root 10 Oct 11 21:10 9b99e3a5-dc67-45fc-ae20-654377044f2b -> ../../sdb2
lrwxrwxrwx 1 root root 10 Oct 11 21:10 ba7e6049-b53d-4284-affd-c39e976f5b15 -> ../../sdc5
lrwxrwxrwx 1 root root 10 Oct 11 21:10 CED025F1D025E107 -> ../../sda2
lrwxrwxrwx 1 root root 10 Oct 11 21:10 ef5f655f-3e02-482b-b80e-5676264f4665 -> ../../sdb1

I have even tried hot plugging the drive while the machine is still running adding the drive, but it still fails when I restart.

Any help would be appreciated

Last edited by anarcho (2014-10-11 22:33:52)

WorMzy · 2014-10-11 21:54:56

I think your bootloader is probably at fault here. What do you use? Please post it's configuration file here in-between code tags.

anarcho · 2014-10-11 22:02:22

Syslinux

# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
#
# Comboot modules:
#   * menu.c32 - provides a text menu
#   * vesamenu.c32 - provides a graphical menu
#   * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
#   * hdt.c32 - hardware detection tool
#   * reboot.c32 - reboots the system
#
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
#
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
#
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples

DEFAULT arch
PROMPT 0        # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl

# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32

# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std

# boot sections follow
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sdb1 rw
    INITRD ../initramfs-linux.img

LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sdb1 rw
    INITRD ../initramfs-linux-fallback.img

LABEL windows
        MENU LABEL Windows
        COM32 chain.c32
        APPEND mbr:0x893af806

LABEL hdt
        MENU LABEL HDT (Hardware Detection Tool)
        COM32 hdt.c32

LABEL reboot
        MENU LABEL Reboot
        COM32 reboot.c32

LABEL poweroff
        MENU LABEL Poweroff
        COM32 poweroff.c32

WorMzy · 2014-10-11 22:13:33

Well, there's the problem:

APPEND root=/dev/sdb1 rw

You might want to try changing this to

APPEND root=/dev/disk/by-uuid/ef5f655f-3e02-482b-b80e-5676264f4665 rw

or

APPEND root=UUID=ef5f655f-3e02-482b-b80e-5676264f4665 rw

I'm not too sure whether syslinux will handle the latter correctly, but the former should work.

EDIT: make sure to update your fallback entries too, once you're sure it's working.

Last edited by WorMzy (2014-10-11 22:14:07)

anarcho · 2014-10-11 22:36:51

Thanks that worked with

APPEND root=/dev/disk/by-uuid/ef5f655f-3e02-482b-b80e-5676264f4665 rw

in /boot/syslinux/syslinux.cfg as well as adjusting fstab to the correct devices.

WorMzy · 2014-10-11 22:43:32

Your fstab looked to be fine. The comments were out of date, but they're mostly useless anyway.

anarcho · 2014-10-11 23:01:44

WorMzy wrote:

Your fstab looked to be fine. The comments were out of date, but they're mostly useless anyway.

It changed around the /dev/sd** on some.

#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sdc1
UUID=ef5f655f-3e02-482b-b80e-5676264f4665       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sdc2
UUID=9b99e3a5-dc67-45fc-ae20-654377044f2b       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sdd5
UUID=ba7e6049-b53d-4284-affd-c39e976f5b15       /mnt/backup     ext4            rw,relatime,data=ordered        0 2

# /dev/sdb1
UUID=A878C84378C811CC                          /mnt/share      ntfs            rw,relatime,data=ordered        0 2

WorMzy · 2014-10-11 23:33:34

The lines with /dev/sd** on them are all comments (they begin with a #), they have no effect on the system. If keeping them up to date makes you feel better, then that's fine.

Arch Linux

#1 2014-10-11 21:41:28

System goes into rootfs when I add a forth hard drive [SOLVED]

#2 2014-10-11 21:54:56

Re: System goes into rootfs when I add a forth hard drive [SOLVED]

#3 2014-10-11 22:02:22

Re: System goes into rootfs when I add a forth hard drive [SOLVED]

#4 2014-10-11 22:13:33

Re: System goes into rootfs when I add a forth hard drive [SOLVED]

#5 2014-10-11 22:36:51

Re: System goes into rootfs when I add a forth hard drive [SOLVED]

#6 2014-10-11 22:43:32

Re: System goes into rootfs when I add a forth hard drive [SOLVED]

#7 2014-10-11 23:01:44

Re: System goes into rootfs when I add a forth hard drive [SOLVED]

#8 2014-10-11 23:33:34

Re: System goes into rootfs when I add a forth hard drive [SOLVED]

Board footer