i have install 3-4 dell PE server withn cenots 5, on the server there is only the OS, i have reboot the server and it work fine, after 4-5 days the system was unstable rebooting it i have note that can mount the partition, i have check the /etc/fstab and i have found that the fstab was corrupt, there are a lot of entry for /dev/shm, why happend this? how can i recove the fstab?
View 3 Replies
i have a strange issue on my centos 5, the fstab get corrupt, we have reinstall the OS and with the server empty it get corrupt again, the same problem on a second server, seem that is add /dev/shm line, like this one:
LABEL=/ / ext3 tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0,usrquota 1 1
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0 0 0
LABEL=/home1 /home ext3 tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0,usrquota 1 2
proc /proc proc tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0 0 0
sysfs /sys sysfs tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0 0 0
LABEL=/tmp1 /tmp ext3 rw,noexec,nosuid,nodev 1 2
LABEL=/usr /usr ext3 tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0,usrquota 1 2
LABEL=/var /var ext3 tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0,usrquota 1 2
LABEL=SWAP-sda5 swap swap tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0 0 0
/tmp /var/tmp ext3 /tmp /var/tmp ext3 rw,noexec,nosuid,nodev,bind 0 0 0 0
I edited the /etc/fstab with pico to include the noatime to some partitions.
LABEL=/ / ext3 defaults,usrquota 1 1
LABEL=/boot1 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs noexec,nosuid 0 0
LABEL=/home /home ext3 defaults,noatime,usrquota 1 2
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
LABEL=/tmp1 /tmp ext3 defaults,noatime 1 2
LABEL=/usr1 /usr ext3 defaults,noatime,usrquota 1 2
LABEL=/var1 /var ext3 defaults,noatime,usrquota 1 2
LABEL=SWAP-sda5 swap swap pri=0,defaults 0 0
/dev/sdb1 /hdd1 ext3 defaults,noatime,usrquota 0 0
/dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
How do I make the changes take into effect without a restart?
I tried to restart the server the other day (Linux Red Hat 9) and was told there were error messages with /etc/rc.d/rc.sysinit and fstab. The server was booted with Livecd Gentoo and I'm not sure where to begin since my knowledge of Linux is fairly limited.
View 4 Replies View RelatedThe Details:
XP Home, Verizon DSL, AVG, ZoneAlarm, CoffeeCup FTP, FileZilla FTP
So this all started about 5 days ago and I cannot think of anything that I did to associate this issue with. I'm very computer savvy and no one else uses this computer except for me (to help move things along faster). Essentially what happens when I start CoffeeCup FTP or FileZilla FTP (testing to make sure it wasn't just a problem with CoffeeCup FTP) and try to upload image files it fails, not the upload itself.. but somehow the image files are corrupt (no they're not CMYK, they're RGB). So it shows the file on my server, correct size, no error messages. However, when I go to the image URL it just shows the image URL where the image should be. I then restart CoffeeCup FTP and everything uploads properly. I've checked the lines on DSLReports.com, I've checked ZoneAlarm to make sure that I didn't somehow accidentally click no to something (which is unlikely). I keep my computer very clean and very organized and very up to date so it would be more helpful to me if someone could share some ideas of something that could happen that's not of my control. Could this possibly have anything to do with SP3 (the only thing I can recall being a change on my computer).
I have two partitions on my hard drive, each have an installation of windows XP, the old partition got corrupt and I can no longer boot windows from it, however I am able to see the files when on the other partition, the problem is I am unable to access the files.
Is there anyway I can get permissions to delete/move those files?
I created a 4GB disk image for a virtual machine in Xen. (I have root on the physical box, so please don't tell me to contact my VPS provider!)
The disk was filling up, so I took the advice online and created a 6GB file with dd (zero-filled), cat'ed it to the end of my disk file, and then...
[matt@babe centos]$ sudo resize2fs -f ./cent.img
resize2fs 1.39 (29-May-2006)
resize2fs: Bad magic number in super-block while trying to open ./cent.img
Couldn't find valid filesystem superblock.
Of course, fsck won't take a disk image, only an actual partition. And I can't mount it, since I get the same error about a bad superblock.
The VM actually boots up fine, but it only sees 4GB of what's now a 10GB file.
I can use losetup to mount it on a /dev, but still get fsck errors:
[matt@babe centos]$ sudo fsck.ext3 -b 8193 /dev/loop3
e2fsck 1.39 (29-May-2006)
fsck.ext3: Bad magic number in super-block while trying to open /dev/loop3
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I don't know what blocksize was used, so I don't know where to look for a superblock... (I'm out of my league on fsck'ing virtual disks.)
The thing boots fine and is non-mission-critical right now, so worst-case, I can just mount it, rsync the data to the host, and then set up a new machine and rsync that in... I'd just rather not go through that hassle if I don't have to.
O/S was corrupt so I had to do a reload on a new drive. I'm trying to mount original drive (already connected as 2nd) but it is not showing up in df -h
Code:
root@server080 [~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 145G 2.5G 135G 2% /
/dev/sda1 99M 12M 83M 12% /boot
none 252M 0 252M 0% /dev/shm
/usr/tmpDSK 485M 11M 449M 3% /tmp
/tmp 485M 11M 449M 3% /var/tmp
/dev/sdb1 99M 12M 83M 12% /backup
root@server080 [~]# e2label /dev/sdb1
/boot1
root@server080 [~]# dumpe2fs /dev/sdb1 | grep -i superblock
dumpe2fs 1.35 (28-Feb-2004)
Primary superblock at 1, Group descriptors at 2-2
Backup superblock at 8193, Group descriptors at 8194-8194
Backup superblock at 24577, Group descriptors at 24578-24578
Backup superblock at 40961, Group descriptors at 40962-40962
Backup superblock at 57345, Group descriptors at 57346-57346
Backup superblock at 73729, Group descriptors at 73730-73730
/etc/fstab shows
Code:
# This file is edited by fstab-sync - see 'man fstab-sync' for details
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /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
LABEL=SWAP-sda2 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
Our server with raid 10 has had a failed hdd (which was replaced) and a
corrupt ext3 filesystem.
The server is now booted with Knoppix but drives will not mount. All we are trying to at this point is salvage as much data as we can.
Primary drive (centos/cpanel) is corrupt
The server is displaying these errors when I tried to do an FSCK:
Bad inode IO
ext3-fs error (device(8,3)) IO Failure
I am having a new primary installed and old primary set as 2nd drive. I need to recover the cpanel domain accounts from this 2nd drive after I mount it with the method below:
mkdir /backup
mount /dev/sdb1 /backup
However, how do I actually recover these accounts in an automated process via whm? I've done this before with the same matter (corrupt primary drive, mount as 2nd, etc) but cannot exactly remember the proper steps.
I have a dedicated box and I started getting Input/output errors today.
I tried:
# fsck
fsck 1.40-WIP (14-Nov-2006)
e2fsck 1.40-WIP (14-Nov-2006)
/dev/hda2: recovering journal
fsck.ext3: unable to set superblock flags on /dev/hda2
then I tried:
# fsck -a -t ext3 /dev/hda2
fsck 1.40-WIP (14-Nov-2006)
/dev/hda2: recovering journal
fsck.ext3: unable to set superblock flags on /dev/hda2
My data is backed up, so was going to ask for a reimage, but is this an indication of bad hardware? Should I ask for a replacement drive? Is there anything else I should try on my own before going to the host?
