Server suddenly lost mount - /dev/sda doesn't contain a valid partitio
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[root@serv ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
1866322480 554196528 1215792948 32% /
/dev/sda1 101086 38675 57192 41% /boot
tmpfs 12312444 0 12312444 0% /dev/shm
[root@serv ~]# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
It's possible that information reported by mount(8) is not
up to date. For actual information about system mount points
check the /proc/mounts file.
*
[root@serv ~]# fdisk -l
*
Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
*
Disk /dev/sda doesn't contain a valid partition table
*
maybe the double slashes are wrong?
have you checked whether the file /var/named/chroot/etc/named.conf actually exists?
shouldn't it be /etc/named.conf?
you saying the root filesystem is read-only? that usually means something went haywire very early in the boot process...
yes, it appears there misteriously happend some filesystem based error, like empty partition table or something that way. Alas i did that mistake to reset server because someone told me that filesystem should be recovered automatically at boot. it was not, and i ended up on IPMI console with messages:
Quote:
Reboot and select proper boot device or insert boot media in selected boot device
No DHCP or proxyDHCP offers were received
Media test failure, check cable
Exitting intel boot agent
im now stuck not knowing how to proceed, hosting provider suggests that i "boot a rescue ISO through the IPMI, connect to the internet from that live CD and back up anything you need (If it's still available)" and also says "Your initial replies showed that the partition table was missing, we don't know what caused this. But until you can restore that, recovering anything might be impossible.". I really dont know how i can somehow simply (im super noob) make it boot, i cant spend two weeks of reading and trying and renewing this server hoping i will recover it. Thats why im asking there if anyone know the steps to do, can suggest or help? Thank You
DESCRIPTION
fsck is used to check and optionally repair one or more Linux filesystems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a mount point
(e.g. /, /usr, /home), or an ext2 label or UUID specifier (e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). Normally, the fsck pro-
gram will try to handle filesystems on different physical disk drives in parallel to reduce the total amount of time needed to check all of them.
If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking filesystems in /etc/fstab
serially. This is equivalent to the -As options.
The exit code returned by fsck is the sum of the following conditions:
0 No errors
1 Filesystem errors corrected
2 System should be rebooted
4 Filesystem errors left uncorrected
8 Operational error
16 Usage or syntax error
32 Fsck canceled by user request
128 Shared-library error
The exit code returned when multiple filesystems are checked is the bit-wise OR of the exit codes for each filesystem that is checked.
In actuality, fsck is simply a front-end for the various filesystem checkers (fsck.fstype) available under Linux. The filesystem-specific checker is
searched for in /sbin first, then in /etc/fs and /etc, and finally in the directories listed in the PATH environment variable. Please see the
filesystem-specific checker manual pages for further details.
By using 'single user mode' you are insuring no other activity on the system when performing the file system check/repair.
Hope this helps.
Have fun & enjoy!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
