Topic: Drive will not mount on boot up

[tviles]

Anyone see anything wrong with my fstab file?
Drive does not mount on boot up but will mount using mount -a command
Error on boot is cannot find file or directory message. I have to pound out last line in fstab file and reboot. Then take out the # on last line in fstab file then save and then issue mount -a command. I can find the file sdg1 in dev and I have directory of tracy under directory of mnt.
This sdg1 sata drive is connected to a promise card in a pci slot.
Dell poweredge 2500 with 6 scsi drives / raid 5 config with spare.



# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/main/root          /                       ext3    usrquota,grpquota        1 1
/dev/md1                /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/main/swap          swap                    swap    defaults        0 0
/dev/hda                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0
/dev/sdg1               /mnt/tracy              ext3    usrquota,grpquota       1 2


[root@shpdserver ~]# df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/mapper/main-root
              ext3   137530456  27106544 103437776  21% /
/dev/md1      ext3      101018     20652     75150  22% /boot
none         tmpfs     1037444         0   1037444   0% /dev/shm
/dev/sdg1     ext3   961432072  20057100 892536972   3% /mnt/tracy

[tviles]

I don't use quotas for users or groups on this system. Does that matter?

[tviles]

/dev/sdg1               /mnt/tracy              ext3    usrquota,grpquota       1 2

What if I change this line to:

 /dev/sdg1               mnt/tracy              ext3   

?
           

[CharlieBrady]

/dev/sdg1               /mnt/tracy              ext3    usrquota,grpquota       1 2

What if I change this line to:

 /dev/sdg1               mnt/tracy              ext3   

?
           

If you do that, you will have a format error in /etc/fstab. You could try:

/dev/sdg1 /mnt/tracy ext3 defaults 1 2

[tviles]

You just hit the space bar and not the tab to enter this into the fstab file?

[mmccarn]

I suspect your drive is connected using hardware that has not yet been activated when the system mounts things.

Why not modify the 'local' event to execute 'mount -a'?

Here are some instructions for creating a mount command to run during each reboot: http://wiki.contribs.org/USBDisks#Mount_your_disk_automatically_at_boot-up  (Just replace mount LABEL=MyLabel with mount -a)

Watch out if you create fstab entries for network shares and mount them - your system will freeze up at each shutdown unless you start the "netfs" service (which just seems to set a flag to cause network shares to be disconnected before the network cards are disabled).  Read more here: http://wiki.contribs.org/Mount_Network_Shares

[tviles]

I will try the script when I can. This is a production server and I am currently copying all the shared network folder files over to a USB drive. I did notice that I am seeing a error of fsck.ext3 not found in /dev/sdg1 on boot up. Yes the pci card bios shows up first on boot up and sees the drive, the I get the Dell screens then I get the SME boot up screens.

[tviles]

I am not seeing that problem. System does do a reboot. I really need to buy a cheap server and try this stuff out at home first. But that is how I roll, learning the hard way.

Watch out if you create fstab entries for network shares and mount them - your system will freeze up at each shutdown unless you start the "netfs" service (which just seems to set a flag to cause network shares to be disconnected before the network cards are disabled).  Read more here: http://wiki.contribs.org/Mount_Network_Shares

[tviles]

I need to tell you something else. One day I installed the hard drive and the controller card into the pci slot on the server and only had time to boot the server back up and leave. I then came home and did the rest of the howto for adding extra hard drive. I never did this command: telinit 1 because I was on a VPN connection from home.

[tviles]

[root@shpdserver ~]# cat /proc/mdstat
Personalities : [raid1] [raid5]
md2 : active raid5 sdb2[0] sda2[1] sde2[4] sdd2[3] sdc2[2]
      141820928 blocks level 5, 256k chunk, algorithm 2 [5/5] [UUUUU]

md1 : active raid1 sdb1[0] sda1[1] sde1[4] sdd1[3] sdc1[2]
      104320 blocks [5/5] [UUUUU]

unused devices: <none>
[root@shpdserver ~]# fdisk -l | more
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/sda: 36.4 GB, 36420075008 bytes
255 heads, 63 sectors/track, 4427 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
/dev/sda2              14        4427    35455455   fd  Linux raid autodetect

Disk /dev/sdb: 36.4 GB, 36420075008 bytes
255 heads, 63 sectors/track, 4427 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdb2              14        4427    35455455   fd  Linux raid autodetect

Disk /dev/sdc: 36.4 GB, 36420075008 bytes
255 heads, 63 sectors/track, 4427 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdc2              14        4427    35455455   fd  Linux raid autodetect

Disk /dev/sdd: 36.4 GB, 36420075008 bytes
255 heads, 63 sectors/track, 4427 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdd2              14        4427    35455455   fd  Linux raid autodetect

Disk /dev/sde: 73.5 GB, 73543163904 bytes
255 heads, 63 sectors/track, 8941 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1   *           1          13      104391   fd  Linux raid autodetect
/dev/sde2              14        8941    71714160   fd  Linux raid autodetect

Disk /dev/sdf: 73.4 GB, 73407820800 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1               1        8924    71681998+  83  Linux

Disk /dev/md1: 106 MB, 106823680 bytes
2 heads, 4 sectors/track, 26080 cylinders
Units = cylinders of 8 * 512 = 4096 bytes


Disk /dev/md2: 145.2 GB, 145224630272 bytes
2 heads, 4 sectors/track, 35455232 cylinders
Units = cylinders of 8 * 512 = 4096 bytes


Disk /dev/dm-0: 143.0 GB, 143076098048 bytes
2 heads, 4 sectors/track, 34930688 cylinders
Units = cylinders of 8 * 512 = 4096 bytes


Disk /dev/dm-1: 2080 MB, 2080374784 bytes
2 heads, 4 sectors/track, 507904 cylinders
Units = cylinders of 8 * 512 = 4096 bytes


Disk /dev/sdg: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1               1      121601   976760001   83  Linux
[root@shpdserver ~]#

So how do you get the * under Boot for drive sdg1?

What would happen if I tried to add sdf1 to md1 and md2?

[tviles]

Check this out. After updates and a few reboots my fstab file is looking like this:


#------------------------------------------------------------
# BE CAREFUL WHEN MODIFYING THIS FILE! It is updated automatically
# by the SME server software. A few entries are updated during
# the template processing of the file and white space is removed,
# but otherwise changes to the file are preserved.
# For more information, see http://www.e-smith.org/custom/ and
# the template fragments in /etc/e-smith/templates/etc/fstab/.
#
# copyright (C) 2002 Mitel Networks Corporation
#------------------------------------------------------------
#-----------------------------------------------------------
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/main/root          /                       ext3    usrquota,grpquota        1 1
/dev/md1                /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/main/swap          swap                    swap    defaults        0 0
/dev/sdg1               /mnt/tracy              ext3    defaults        1 2
/dev/sdf1               /mnt/jeremy             ext3    defaults        1 2
/dev/hda                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0



When I have time I will go to this location and watch a reboot without # in front of my sdf and sdg drive lines.

[tviles]

sdf1 was my raid5 spare but I decided to make it a ibay / backup drive. DAR2 works well with it. Formatted as ext3. Much faster than sending it to a USB external drive attached to a desktop sitting next to the server.
Faster backups I mean.
I have extra drives in the desk drawer in case of drive failure. I did fail the raid5 system a few days back by pulling out one of the drives. It did NOT activate the spare and put it into play. Probably a setup error on my part.