adding internal hard drive causes filesystem check to fail @boot

earthpig · 2009-09-21 22:22:11

hi,

im trying to use s.m.a.r.t. tools on an internal hard drive that certainly has some bad blocks and other issues. using an external USB enclosure does not work for this, as smart has only limited functionality unless the hard drive is connected internally.

when i put the second hard drive in and rebooted, i did indeed set the bios to boot from the current/original hard drive, and it started booting as normal...

...until the filesystem check, which then failed, stopped the boot process, and instructed me to enter my root password for maintenance.

following the directions and reading the manfiles of fsck and e2fsck, i was unable to find the 'superblock' of my / partition. i played around a bit longer, but then gave up.

turned computer off, removed the additional hard drive, booted up again.

booted fine, no problems and no complaints. so, i am pretty sure there is indeed no problems with my primary hard drive...

so,

how do i tell arch "i KNOW the second internal hard drive is jacked up, boot anyways unless you see any problems with something in my fstab or with a hard drive i care about."

dont know if this is needed or relevant, but my fstab does not contain any references to anything except that one primary hard drive:

[chris: ~]$ cat /etc/fstab
# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0

#/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
#/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
#/dev/fd0               /media/fl   auto    user,noauto             0      0

/dev/sda1 / ext4 defaults 0 1
/dev/sda2 /home ext4 defaults 0 1

my /etc/rc.conf is similarly vanilla. i've added a few daemons and whatnot, but nothing that i can fathom would have an effect on this.

Last edited by earthpig (2009-09-21 22:24:08)

neddie_seagoon · 2009-09-22 00:18:21

It's possible that with the 2nd drive in the system is seeing it as the primary (because of device name swapping) and it attempting to treat it as such. Check the following article:
http://wiki.archlinux.org/index.php/Per … ice_naming

chilebiker · 2009-09-22 01:46:10

Remove the filesystem check and it should start fine (1 -> 0 at the end of the line).

/dev/sda1 / ext4 defaults 0 0
/dev/sda2 /home ext4 defaults 0 0

Last edited by chilebiker (2009-09-22 01:46:33)

Chokkan · 2009-09-22 17:03:23

Yup, I had the same problem and removing the check solved it.

Arch Linux

#1 2009-09-21 22:22:11

adding internal hard drive causes filesystem check to fail @boot

#2 2009-09-22 00:18:21

Re: adding internal hard drive causes filesystem check to fail @boot

#3 2009-09-22 01:46:10

Re: adding internal hard drive causes filesystem check to fail @boot

#4 2009-09-22 17:03:23

Re: adding internal hard drive causes filesystem check to fail @boot

Board footer