Hi,
<< System description: >>
I have a server with 3 partitions (but it reports 4 with sda1 with 1mb in size).
sda2 is / <-- has OS files
sda3 is /home <-- has virtual servers, webhosts, files, etc
sda4 is swap
fdisk -l shows "Partition 1 does not start on physical sector boundary." along with this warning: "GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted."
parted -l shows: Number Start End Size File system Name Flags 1 20.5kB 1049kB 1029kB primary bios_grub 2 2097kB 26.2GB 26.2GB ext4 primary 3 26.2GB 1992GB 1966GB ext4 primary 4 1992GB 2000GB 8589MB linux-swap(v1) primary
<< The issue: >>
When I reboot the server, /home is not mounted and I have to manually do: mount -t ext4 /dev/sda3 /home
<< Question: >>
Is there a way to have /home mount on boot?
Your help is much appreciated.
Howdy,
Can you post your /etc/fstab file? It's possible that may need tweaked in order to make /home mount automatically.
-Eric
Hi Eric, Thanks for the quick reply!
Here is the content of /etc/fstab:
Bump : )
Any one cares to help?
Your fstab file looks pretty normal.
Do you see any errors during bootup that might explain why it's having trouble mounting that automatically?
-Eric
Hi Eric,
I get this from Webmin Edit Mount page:
Failed to save mount : Mount failed :
mount: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
under the same page, in option "New Linux Native Filesystem" I tried both:
But again, if I manually do "mount -t ext4 /dev/sda3 /home" in ssh, then all is good.
Hmm, so after rebooting, what output do you receive if you just run this command:
mount /home
Same as above (sorry I thought I mentioned it)
mount: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
I'm not quite sure what the issue you're seeing is, but you may want to try tinkering with the options being used in the /etc/fstab file for that mount point.
A few of them aren't default options, and it's possible one of the ones being used is causing a problem.
You could try removing "barrier=1" and "data=ordered", for example, and then try rebooting again.
-Eric
I resolved the issue by removing the option seclabel from /etc/fstab
Great, thanks for letting us know how you fixed it!