Server suddenly lost mount - /dev/sda doesn't contain a valid partitio




can You please give me an advice why my named dont want to start suddenly?

Please check this kindly:

[root@serv ~]# service named restart
Stopping named: [ OK ]
Locating /var/named/chroot//etc/named.conf failed:

[root@serv ~]# locate named.conf
[root@serv ~]# cp /usr/share/doc/bind-9.3.6/sample/etc/named.conf /var/named/chroot/etc
cp: cannot create regular file `/var/named/chroot/etc/named.conf': Read-only file system

[root@serv ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
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

[root@serv ~]# blkid
/dev/mapper/VolGroup00-LogVol01: TYPE="swap"
/dev/mapper/VolGroup00-LogVol00: UUID="9a2e6ab0-00b5-46c0-bbc6-e0bcc41f1315" TYPE="ext3"
/dev/sda1: LABEL="/boot" UUID="722940e7-59fd-417f-8b31-fbf574090120" TYPE="ext3" SEC_TYPE="ext2"
/dev/VolGroup00/LogVol00: UUID="9a2e6ab0-00b5-46c0-bbc6-e0bcc41f1315" TYPE="ext3"
/dev/VolGroup00/LogVol01: TYPE="swap"

How can i try to fix this please?

upstart is looking for a file in
which cannot possibly exist due to the double //.

And is this a chroot environment? That could explain a few things.
Thank you,
it was some filesystem / partition table related issue, i failed to fix it. After reset, it failed to start and the man who looked on the server somehow made partitions unreadable, so it was not able to recover it by fsck utility. Someone also recommended "testdisk utility". I ended up loosing data and hoping next time i will remember to use these two tools before panicking. I alas did not discovered what was the cause of this. smartctl was ok. server expiring in 6 days around.

Members online