When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
Hm, that's not good.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
Is /boot mounted? Please show as the output of 'mount'.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
First, to check the filesystem you have to unmount it. And then to check, you usually give the device name, not it's label (I'm not sure it work by naming with the label). Usually something like
fsck.ext3 /dev/sda1
Simon
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Here is the output of mount:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc1 on /boot type ext3 (rw) none 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)
Does not appear to be mounted...correct?
Todd
On 3/8/2011 3:08 PM, Simon Matter wrote:
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
Hm, that's not good.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
Is /boot mounted? Please show as the output of 'mount'.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
First, to check the filesystem you have to unmount it. And then to check, you usually give the device name, not it's label (I'm not sure it work by naming with the label). Usually something like
fsck.ext3 /dev/sda1
Simon
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 03/08/11 3:17 PM, Todd Cary wrote:
Here is the output of mount:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc1 on /boot type ext3 (rw)
**************************
none 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)
Does not appear to be mounted...correct?
yes, it does. from /dev/hdc1 ... which seems quite unusual that its on your third IDE device
your / is LVM, so you can't tell from above what disk its on, you'll need to dig into LVM to find out.
Here is the output of mount:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc1 on /boot type ext3 (rw)
^^^^^ It's mounted here, the device is /dev/hdc1.
But now, also show us 'df' and 'ls -la /boot'
How did you boot if /boot was empty?
Simon
none 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)
Does not appear to be mounted...correct?
Todd
On 3/8/2011 3:08 PM, Simon Matter wrote:
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
Hm, that's not good.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
Is /boot mounted? Please show as the output of 'mount'.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
First, to check the filesystem you have to unmount it. And then to check, you usually give the device name, not it's label (I'm not sure it work by naming with the label). Usually something like
fsck.ext3 /dev/sda1
Simon
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Simon -
Did I screw up? I deleted what was in /boot!
Todd
On 3/8/2011 3:31 PM, Simon Matter wrote:
Here is the output of mount:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc1 on /boot type ext3 (rw)
^^^^^ It's mounted here, the device is /dev/hdc1.
But now, also show us 'df' and 'ls -la /boot'
How did you boot if /boot was empty?
Simon
none 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)
Does not appear to be mounted...correct?
Todd
On 3/8/2011 3:08 PM, Simon Matter wrote:
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
Hm, that's not good.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
Is /boot mounted? Please show as the output of 'mount'.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
First, to check the filesystem you have to unmount it. And then to check, you usually give the device name, not it's label (I'm not sure it work by naming with the label). Usually something like
fsck.ext3 /dev/sda1
Simon
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Simon -
Did I screw up? I deleted what was in /boot!
Yes :(
Now don't reboot!
Wait for the next mail...
Simon
Todd
On 3/8/2011 3:31 PM, Simon Matter wrote:
Here is the output of mount:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc1 on /boot type ext3 (rw)
^^^^^ It's mounted here, the device is /dev/hdc1.
But now, also show us 'df' and 'ls -la /boot'
How did you boot if /boot was empty?
Simon
none 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)
Does not appear to be mounted...correct?
Todd
On 3/8/2011 3:08 PM, Simon Matter wrote:
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
Hm, that's not good.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
Is /boot mounted? Please show as the output of 'mount'.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
First, to check the filesystem you have to unmount it. And then to check, you usually give the device name, not it's label (I'm not sure it work by naming with the label). Usually something like
fsck.ext3 /dev/sda1
Simon
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
There are 135 items in trash...hopefully that can save me.
Todd
On 3/8/2011 3:42 PM, Simon Matter wrote:
Simon -
Did I screw up? I deleted what was in /boot!
Yes :(
Now don't reboot!
Wait for the next mail...
Simon
Todd
On 3/8/2011 3:31 PM, Simon Matter wrote:
Here is the output of mount:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc1 on /boot type ext3 (rw)
^^^^^ It's mounted here, the device is /dev/hdc1.
But now, also show us 'df' and 'ls -la /boot'
How did you boot if /boot was empty?
Simon
none 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)
Does not appear to be mounted...correct?
Todd
On 3/8/2011 3:08 PM, Simon Matter wrote:
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
Hm, that's not good.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
Is /boot mounted? Please show as the output of 'mount'.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
First, to check the filesystem you have to unmount it. And then to check, you usually give the device name, not it's label (I'm not sure it work by naming with the label). Usually something like
fsck.ext3 /dev/sda1
Simon
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
If the necessary files are in trash, how do I get copy them back to /boot properly e.g. put them in the crorrect place and how do I know which ones are necessary?
Sorry to have created such a problem!
Todd
On 3/8/2011 3:42 PM, Simon Matter wrote:
Simon -
Did I screw up? I deleted what was in /boot!
Yes :(
Now don't reboot!
Wait for the next mail...
Simon
Todd
On 3/8/2011 3:31 PM, Simon Matter wrote:
Here is the output of mount:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc1 on /boot type ext3 (rw)
^^^^^ It's mounted here, the device is /dev/hdc1.
But now, also show us 'df' and 'ls -la /boot'
How did you boot if /boot was empty?
Simon
none 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)
Does not appear to be mounted...correct?
Todd
On 3/8/2011 3:08 PM, Simon Matter wrote:
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
Hm, that's not good.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
Is /boot mounted? Please show as the output of 'mount'.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
First, to check the filesystem you have to unmount it. And then to check, you usually give the device name, not it's label (I'm not sure it work by naming with the label). Usually something like
fsck.ext3 /dev/sda1
Simon
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
If the necessary files are in trash, how do I get copy them back to /boot properly e.g. put them in the crorrect place and how do I know which ones are necessary?
There are several files in /boot all containing a kernel version in the name, like:
config-2.6.18-194.17.4.el5 initrd-2.6.18-194.17.4.el5.centos.plus.img symvers-2.6.18-194.17.4.el5.centos.plus.gz vmlinuz-2.6.18-194.17.4.el5
etc.
There is also an important folder named 'grub', and one additional file named 'message'
First, thank you for the assistance.
What files should be in grub?
Thanks...
Todd
On 3/8/2011 5:11 PM, compdoc wrote:
If the necessary files are in trash, how do I get copy them back to /boot properly e.g. put them in the crorrect place and how do I know which ones are necessary?
There are several files in /boot all containing a kernel version in the name, like:
config-2.6.18-194.17.4.el5 initrd-2.6.18-194.17.4.el5.centos.plus.img symvers-2.6.18-194.17.4.el5.centos.plus.gz vmlinuz-2.6.18-194.17.4.el5
etc.
There is also an important folder named 'grub', and one additional file named 'message'
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Oh yes...where are the files in the Trash? I used the GUI to determjine that I have them.
Thanks...
Todd
On 3/8/2011 5:11 PM, compdoc wrote:
If the necessary files are in trash, how do I get copy them back to /boot properly e.g. put them in the crorrect place and how do I know which ones are necessary?
There are several files in /boot all containing a kernel version in the name, like:
config-2.6.18-194.17.4.el5 initrd-2.6.18-194.17.4.el5.centos.plus.img symvers-2.6.18-194.17.4.el5.centos.plus.gz vmlinuz-2.6.18-194.17.4.el5
etc.
There is also an important folder named 'grub', and one additional file named 'message'
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Oh yes...where are the files in the Trash? I used the GUI to determjine that I have them.
for what it's worth, here's a dump of my /boot:
[steve@mail ~]$ ls -l /boot/* -rw-r--r-- 1 root root 66892 Sep 30 03:18 /boot/config-2.6.18-194.17.1.el5 -rw-r--r-- 1 root root 66892 Nov 10 05:24 /boot/config-2.6.18-194.26.1.el5 -rw-r--r-- 1 root root 66892 Jan 6 10:31 /boot/config-2.6.18-194.32.1.el5 -rw------- 1 root root 2674607 Oct 1 13:13 /boot/initrd-2.6.18-194.17.1.el5.img -rw------- 1 root root 2674287 Nov 20 18:28 /boot/initrd-2.6.18-194.26.1.el5.img -rw------- 1 root root 2674772 Jan 8 16:45 /boot/initrd-2.6.18-194.32.1.el5.img -rw------- 1 root root 2663289 Jul 25 2010 /boot/initrd-2.6.34.1.img -rw-r--r-- 1 root root 80032 Mar 17 2009 /boot/message -rw-r--r-- 1 root root 112729 Sep 30 03:20 /boot/symvers-2.6.18-194.17.1.el5.gz -rw-r--r-- 1 root root 112729 Nov 10 05:25 /boot/symvers-2.6.18-194.26.1.el5.gz -rw-r--r-- 1 root root 112807 Jan 6 10:32 /boot/symvers-2.6.18-194.32.1.el5.gz lrwxrwxrwx 1 root root 25 Jul 25 2010 /boot/System.map -> /boot/System.map-2.6.34.1 -rw-r--r-- 1 root root 1243411 Sep 30 03:18 /boot/System.map-2.6.18-194.17.1.el5 -rw-r--r-- 1 root root 1243713 Nov 10 05:24 /boot/System.map-2.6.18-194.26.1.el5 -rw-r--r-- 1 root root 1244821 Jan 6 10:31 /boot/System.map-2.6.18-194.32.1.el5 -rw-r--r-- 1 root root 1649164 Jul 25 2010 /boot/System.map-2.6.34.1 -rw-r--r-- 1 root root 1638957 Jul 25 2010 /boot/System.map-2.6.34.1.old lrwxrwxrwx 1 root root 22 Jul 25 2010 /boot/vmlinuz -> /boot/vmlinuz-2.6.34.1 -rw-r--r-- 1 root root 1955036 Sep 30 03:18 /boot/vmlinuz-2.6.18-194.17.1.el5 -rw-r--r-- 1 root root 1955356 Nov 10 05:24 /boot/vmlinuz-2.6.18-194.26.1.el5 -rw-r--r-- 1 root root 1955804 Jan 6 10:31 /boot/vmlinuz-2.6.18-194.32.1.el5 -rw-r--r-- 1 root root 2547888 Jul 25 2010 /boot/vmlinuz-2.6.34.1 -rw-r--r-- 1 root root 2536336 Jul 25 2010 /boot/vmlinuz-2.6.34.1.old
/boot/grub: total 332 -rw-r--r-- 1 root root 82 Jan 26 2010 device.map -rw-r--r-- 1 root root 7584 Jan 26 2010 e2fs_stage1_5 -rw-r--r-- 1 root root 7456 Jan 26 2010 fat_stage1_5 -rw-r--r-- 1 root root 6720 Jan 26 2010 ffs_stage1_5 -rw------- 1 root root 1030 Jan 8 16:47 grub.conf -rw-r--r-- 1 root root 6720 Jan 26 2010 iso9660_stage1_5 -rw-r--r-- 1 root root 8224 Jan 26 2010 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Jan 26 2010 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 6880 Jan 26 2010 minix_stage1_5 -rw-r--r-- 1 root root 9248 Jan 26 2010 reiserfs_stage1_5 -rw-r--r-- 1 root root 55808 Mar 17 2009 splash.xpm.gz -rw-r--r-- 1 root root 512 Jan 26 2010 stage1 -rw-r--r-- 1 root root 104988 Jan 26 2010 stage2 -rw-r--r-- 1 root root 7072 Jan 26 2010 ufs2_stage1_5 -rw-r--r-- 1 root root 6272 Jan 26 2010 vstafs_stage1_5 -rw-r--r-- 1 root root 8872 Jan 26 2010 xfs_stage1_5
Steve -
That dump should be VERY useful. I found the files in /boot/.Trash-root/
If you or anyone has additional info, please pass it on...
Thank you...
On 3/8/2011 5:21 PM, Steve Barnes wrote:
Oh yes...where are the files in the Trash? I used the GUI to determjine that I have them.
for what it's worth, here's a dump of my /boot:
[steve@mail ~]$ ls -l /boot/* -rw-r--r-- 1 root root 66892 Sep 30 03:18 /boot/config-2.6.18-194.17.1.el5 -rw-r--r-- 1 root root 66892 Nov 10 05:24 /boot/config-2.6.18-194.26.1.el5 -rw-r--r-- 1 root root 66892 Jan 6 10:31 /boot/config-2.6.18-194.32.1.el5 -rw------- 1 root root 2674607 Oct 1 13:13 /boot/initrd-2.6.18-194.17.1.el5.img -rw------- 1 root root 2674287 Nov 20 18:28 /boot/initrd-2.6.18-194.26.1.el5.img -rw------- 1 root root 2674772 Jan 8 16:45 /boot/initrd-2.6.18-194.32.1.el5.img -rw------- 1 root root 2663289 Jul 25 2010 /boot/initrd-2.6.34.1.img -rw-r--r-- 1 root root 80032 Mar 17 2009 /boot/message -rw-r--r-- 1 root root 112729 Sep 30 03:20 /boot/symvers-2.6.18-194.17.1.el5.gz -rw-r--r-- 1 root root 112729 Nov 10 05:25 /boot/symvers-2.6.18-194.26.1.el5.gz -rw-r--r-- 1 root root 112807 Jan 6 10:32 /boot/symvers-2.6.18-194.32.1.el5.gz lrwxrwxrwx 1 root root 25 Jul 25 2010 /boot/System.map -> /boot/System.map-2.6.34.1 -rw-r--r-- 1 root root 1243411 Sep 30 03:18 /boot/System.map-2.6.18-194.17.1.el5 -rw-r--r-- 1 root root 1243713 Nov 10 05:24 /boot/System.map-2.6.18-194.26.1.el5 -rw-r--r-- 1 root root 1244821 Jan 6 10:31 /boot/System.map-2.6.18-194.32.1.el5 -rw-r--r-- 1 root root 1649164 Jul 25 2010 /boot/System.map-2.6.34.1 -rw-r--r-- 1 root root 1638957 Jul 25 2010 /boot/System.map-2.6.34.1.old lrwxrwxrwx 1 root root 22 Jul 25 2010 /boot/vmlinuz -> /boot/vmlinuz-2.6.34.1 -rw-r--r-- 1 root root 1955036 Sep 30 03:18 /boot/vmlinuz-2.6.18-194.17.1.el5 -rw-r--r-- 1 root root 1955356 Nov 10 05:24 /boot/vmlinuz-2.6.18-194.26.1.el5 -rw-r--r-- 1 root root 1955804 Jan 6 10:31 /boot/vmlinuz-2.6.18-194.32.1.el5 -rw-r--r-- 1 root root 2547888 Jul 25 2010 /boot/vmlinuz-2.6.34.1 -rw-r--r-- 1 root root 2536336 Jul 25 2010 /boot/vmlinuz-2.6.34.1.old
/boot/grub: total 332 -rw-r--r-- 1 root root 82 Jan 26 2010 device.map -rw-r--r-- 1 root root 7584 Jan 26 2010 e2fs_stage1_5 -rw-r--r-- 1 root root 7456 Jan 26 2010 fat_stage1_5 -rw-r--r-- 1 root root 6720 Jan 26 2010 ffs_stage1_5 -rw------- 1 root root 1030 Jan 8 16:47 grub.conf -rw-r--r-- 1 root root 6720 Jan 26 2010 iso9660_stage1_5 -rw-r--r-- 1 root root 8224 Jan 26 2010 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Jan 26 2010 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 6880 Jan 26 2010 minix_stage1_5 -rw-r--r-- 1 root root 9248 Jan 26 2010 reiserfs_stage1_5 -rw-r--r-- 1 root root 55808 Mar 17 2009 splash.xpm.gz -rw-r--r-- 1 root root 512 Jan 26 2010 stage1 -rw-r--r-- 1 root root 104988 Jan 26 2010 stage2 -rw-r--r-- 1 root root 7072 Jan 26 2010 ufs2_stage1_5 -rw-r--r-- 1 root root 6272 Jan 26 2010 vstafs_stage1_5 -rw-r--r-- 1 root root 8872 Jan 26 2010 xfs_stage1_5
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Besides recovering the files, you'll need to delete some of them to free up space.
Here's an idea of how to go about it:
Yes...thank you for the suggestion...since that was the cause of my problem in the first place!! I should have known better; all I had to do was remove some of the outdated kernel files. And when I did the dumb thing of deleting the /boot files, they were moved into the "protected" .Trash-boot directory.
Todd
On 3/8/2011 5:51 PM, compdoc wrote:
Besides recovering the files, you'll need to delete some of them to free up space.
Here's an idea of how to go about it:
http://www.howtoforge.com/forums/showthread.php?t=19788
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 03/08/11 6:15 PM, Todd Cary wrote:
Yes...thank you for the suggestion...since that was the cause of my problem in the first place!! I should have known better; all I had to do was remove some of the outdated kernel files. And when I did the dumb thing of deleting the /boot files, they were moved into the "protected" .Trash-boot directory.
rather than manually rm'ing the old kernels, you really should use rpm -e kernel-$oldversion
# rpm -e kernel-2.6.18-194.17.1 kernel-2.6.18-194.26.1 kernel-2.6.18-194.132.1
this will clean up not only /boot but also stuff in /lib/modules and the rpm database etc.
Many thanks!
Todd
On 3/8/2011 6:43 PM, John R Pierce wrote:
On 03/08/11 6:15 PM, Todd Cary wrote:
Yes...thank you for the suggestion...since that was the cause of my problem in the first place!! I should have known better; all I had to do was remove some of the outdated kernel files. And when I did the dumb thing of deleting the /boot files, they were moved into the "protected" .Trash-boot directory.
rather than manually rm'ing the old kernels, you really should use rpm -e kernel-$oldversion
# rpm -e kernel-2.6.18-194.17.1 kernel-2.6.18-194.26.1kernel-2.6.18-194.132.1
this will clean up not only /boot but also stuff in /lib/modules and the rpm database etc.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yes...thank you for the suggestion...since that was the cause of my problem in the first place!! I should have known better; all I had to do was remove some of the outdated kernel files. And when I did the dumb thing of deleting the /boot files, they were moved into the "protected" .Trash-boot directory.
OK, now let us know exactly what you have. Is it CentOS 4 as I expected? If so, the listing of files in /boot should look like so:
[root@abc ~]# ls -laR /boot/ /boot/: total 3771 drwxr-xr-x 4 root root 1024 Mar 3 11:31 . drwxr-xr-x 24 root root 4096 Mar 3 11:37 .. -rw-r--r-- 1 root root 51676 Feb 18 07:41 config-2.6.9-100.EL drwxr-xr-x 2 root root 1024 Mar 3 11:31 grub -rw-r--r-- 1 root root 1364958 Mar 3 11:20 initrd-2.6.9-100.EL.img drwx------ 2 root root 12288 Jul 8 2005 lost+found -rw-r--r-- 1 root root 9371 Aug 13 2006 message -rw-r--r-- 1 root root 9371 Aug 13 2006 message.ja -rw-r--r-- 1 root root 67797 Feb 18 07:41 symvers-2.6.9-100.EL.gz -rw-r--r-- 1 root root 770652 Feb 18 07:41 System.map-2.6.9-100.EL -rw-r--r-- 1 root root 1538264 Feb 18 07:41 vmlinuz-2.6.9-100.EL
/boot/grub: total 198 drwxr-xr-x 2 root root 1024 Mar 3 11:31 . drwxr-xr-x 4 root root 1024 Mar 3 11:31 .. -rw-r--r-- 1 root root 82 Aug 9 2005 device.map -rw-r--r-- 1 root root 7956 Aug 9 2005 e2fs_stage1_5 -rw-r--r-- 1 root root 7684 Aug 9 2005 fat_stage1_5 -rw-r--r-- 1 root root 6996 Aug 9 2005 ffs_stage1_5 -rw------- 1 root root 589 Mar 3 11:31 grub.conf -rw------- 1 root root 593 Aug 9 2005 grub.conf.orig -rw-r--r-- 1 root root 7028 Aug 9 2005 iso9660_stage1_5 -rw-r--r-- 1 root root 8448 Aug 9 2005 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Aug 9 2005 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 7188 Aug 9 2005 minix_stage1_5 -rw-r--r-- 1 root root 9396 Aug 9 2005 reiserfs_stage1_5 -rw-r--r-- 1 root root 3605 Aug 13 2006 splash.xpm.gz -rw-r--r-- 1 root root 512 Aug 9 2005 stage1 -rw-r--r-- 1 root root 103816 Aug 9 2005 stage2 -rw-r--r-- 1 root root 7272 Aug 9 2005 ufs2_stage1_5 -rw-r--r-- 1 root root 6612 Aug 9 2005 vstafs_stage1_5 -rw-r--r-- 1 root root 9308 Aug 9 2005 xfs_stage1_5
/boot/lost+found: total 14 drwx------ 2 root root 12288 Jul 8 2005 . drwxr-xr-x 4 root root 1024 Mar 3 11:31 ..
1) I don't know which tool you have used to move things to "Trash" but you should be aware that it may well be the case that some permissions and or file types like symlinks may not be correct after recovering from "Trash".
2) The directory "lost+found" can be recreated using the command 'mklost+found'
3) I'm not sure on how to make grub work again, but maybe some steps qre required after copying everything back to /boot. I hope someone else can give you better info about this.
Simon
Todd
On 3/8/2011 5:51 PM, compdoc wrote:
Besides recovering the files, you'll need to delete some of them to free up space.
Here's an idea of how to go about it:
http://www.howtoforge.com/forums/showthread.php?t=19788
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, Mar 9, 2011 at 10:12 AM, Simon Matter simon.matter@invoca.ch wrote:
Yes...thank you for the suggestion...since that was the cause of my problem in the first place!! I should have known better; all I had to do was remove some of the outdated kernel files. And when I did the dumb thing of deleting the /boot files, they were moved into the "protected" .Trash-boot directory.
OK, now let us know exactly what you have. Is it CentOS 4 as I expected? If so, the listing of files in /boot should look like so:
[root@abc ~]# ls -laR /boot/ /boot/: total 3771 drwxr-xr-x 4 root root 1024 Mar 3 11:31 . drwxr-xr-x 24 root root 4096 Mar 3 11:37 .. -rw-r--r-- 1 root root 51676 Feb 18 07:41 config-2.6.9-100.EL drwxr-xr-x 2 root root 1024 Mar 3 11:31 grub -rw-r--r-- 1 root root 1364958 Mar 3 11:20 initrd-2.6.9-100.EL.img drwx------ 2 root root 12288 Jul 8 2005 lost+found -rw-r--r-- 1 root root 9371 Aug 13 2006 message -rw-r--r-- 1 root root 9371 Aug 13 2006 message.ja -rw-r--r-- 1 root root 67797 Feb 18 07:41 symvers-2.6.9-100.EL.gz -rw-r--r-- 1 root root 770652 Feb 18 07:41 System.map-2.6.9-100.EL -rw-r--r-- 1 root root 1538264 Feb 18 07:41 vmlinuz-2.6.9-100.EL
/boot/grub: total 198 drwxr-xr-x 2 root root 1024 Mar 3 11:31 . drwxr-xr-x 4 root root 1024 Mar 3 11:31 .. -rw-r--r-- 1 root root 82 Aug 9 2005 device.map -rw-r--r-- 1 root root 7956 Aug 9 2005 e2fs_stage1_5 -rw-r--r-- 1 root root 7684 Aug 9 2005 fat_stage1_5 -rw-r--r-- 1 root root 6996 Aug 9 2005 ffs_stage1_5 -rw------- 1 root root 589 Mar 3 11:31 grub.conf -rw------- 1 root root 593 Aug 9 2005 grub.conf.orig -rw-r--r-- 1 root root 7028 Aug 9 2005 iso9660_stage1_5 -rw-r--r-- 1 root root 8448 Aug 9 2005 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Aug 9 2005 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 7188 Aug 9 2005 minix_stage1_5 -rw-r--r-- 1 root root 9396 Aug 9 2005 reiserfs_stage1_5 -rw-r--r-- 1 root root 3605 Aug 13 2006 splash.xpm.gz -rw-r--r-- 1 root root 512 Aug 9 2005 stage1 -rw-r--r-- 1 root root 103816 Aug 9 2005 stage2 -rw-r--r-- 1 root root 7272 Aug 9 2005 ufs2_stage1_5 -rw-r--r-- 1 root root 6612 Aug 9 2005 vstafs_stage1_5 -rw-r--r-- 1 root root 9308 Aug 9 2005 xfs_stage1_5
/boot/lost+found: total 14 drwx------ 2 root root 12288 Jul 8 2005 . drwxr-xr-x 4 root root 1024 Mar 3 11:31 ..
- I don't know which tool you have used to move things to "Trash" but you
should be aware that it may well be the case that some permissions and or file types like symlinks may not be correct after recovering from "Trash".
- The directory "lost+found" can be recreated using the command
'mklost+found'
- I'm not sure on how to make grub work again, but maybe some steps qre
required after copying everything back to /boot. I hope someone else can give you better info about this.
Simon
Wouldn't it have been easier to reinstall the kernel & grub, i.e.:
yum reinstall kernel grub
Surely if yum reinstalls it, it would re-create the permissions & symlinks as well?
I haven't done, or tried this before, but it might work?
OK, here is what I have after manually copying files back to /boot, leaving behind old kernel files:
/boot/: total 9169 drwxr-xr-x 5 root root 9216 Mar 8 20:24 . drwxr-xr-x 24 root root 4096 Jan 24 08:34 .. -rw-r--r-- 1 root root 51676 Feb 17 22:41 config-2.6.9-100.EL -rw-r--r-- 1 root root 51645 Mar 8 17:38 config-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 51270 Mar 8 17:38 config-2.6.9-89.35.1.ELsmp drwxr-xr-x 2 root root 1024 Mar 8 20:38 grub -rw-r--r-- 1 root root 1343048 Mar 8 20:24 initrd-2.6.9-100.EL.img -rw-r--r-- 1 root root 692224 Mar 8 17:51 initrd-2.6.9-89.35.1.EL.img -rw-r--r-- 1 root root 0 Mar 8 17:51 initrd-2.6.9-89.35.1.ELsmp.img drwx------ 2 root root 12288 Jan 12 2007 lost+found -rw-r--r-- 1 root root 9371 Mar 8 17:46 message -rw-r--r-- 1 root root 9371 Mar 8 17:46 message.ja -rw-r--r-- 1 root root 67797 Feb 17 22:41 symvers-2.6.9-100.EL.gz -rw-r--r-- 1 root root 67701 Mar 8 17:49 symvers-2.6.9-89.35.1.EL.gz -rw-r--r-- 1 root root 68477 Mar 8 17:49 symvers-2.6.9-89.35.1.ELsmp.gz -rw-r--r-- 1 root root 770652 Feb 17 22:41 System.map-2.6.9-100.EL -rw-r--r-- 1 root root 769061 Mar 8 17:48 System.map-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 786055 Mar 8 17:48 System.map-2.6.9-89.35.1.ELsmp drwx------ 2 root root 9216 Mar 8 17:58 .Trash-root -rw-r--r-- 1 root root 1538264 Feb 17 22:41 vmlinuz-2.6.9-100.EL -rw-r--r-- 1 root root 1536995 Mar 8 17:47 vmlinuz-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 1472967 Mar 8 17:47 vmlinuz-2.6.9-89.35.1.ELsmp
/boot/grub: total 345 drwxr-xr-x 2 root root 1024 Mar 8 20:38 . drwxr-xr-x 5 root root 9216 Mar 8 20:24 .. -rw-r--r-- 1 root root 82 Mar 8 17:39 device.map -rw-r--r-- 1 root root 7956 Mar 8 17:40 e2fs_stage1_5 -rw-r--r-- 1 root root 7684 Mar 8 17:40 fat_stage1_5 -rw-r--r-- 1 root root 6996 Mar 8 17:40 ffs_stage1_5 -rw------- 2 root root 4240 Mar 8 20:24 grub.conf -rw-r--r-- 1 root root 7028 Mar 8 17:40 iso9660_stage1_5 -rw-r--r-- 1 root root 8448 Mar 8 17:40 jfs_stage1_5 -rw------- 2 root root 4240 Mar 8 20:24 menu.lst -rw-r--r-- 1 root root 7188 Mar 8 17:40 minix_stage1_5 -rw-r--r-- 1 root root 9396 Mar 8 17:40 reiserfs_stage1_5 -rw-r--r-- 1 root root 512 Mar 8 17:45 stage1 -rw-r--r-- 1 root root 103688 Mar 8 17:45 stage2 -rw-r--r-- 1 root root 67701 Mar 8 18:30 symvers-2.6.9-89.35.1.EL.gz -rw-r--r-- 1 root root 68477 Mar 8 18:30 symvers-2.6.9-89.35.1.ELsmp.gz -rw-r--r-- 1 root root 7272 Mar 8 17:40 ufs2_stage1_5 -rw-r--r-- 1 root root 6612 Mar 8 17:40 vstafs_stage1_5 -rw-r--r-- 1 root root 9308 Mar 8 17:40 xfs_stage1_5
/boot/lost+found: total 22 drwx------ 2 root root 12288 Jan 12 2007 . drwxr-xr-x 5 root root 9216 Mar 8 20:24 ..
/boot/.Trash-root: total 81058 drwx------ 2 root root 9216 Mar 8 17:58 . drwxr-xr-x 5 root root 9216 Mar 8 20:24 .. -rw-r--r-- 1 root root 51502 Jan 14 2009 config-2.6.9-78.0.13.EL -rw-r--r-- 1 root root 51127 Jan 14 2009 config-2.6.9-78.0.13.ELsmp -rw-r--r-- 1 root root 51614 Sep 15 2009 config-2.6.9-89.0.11.EL -rw-r--r-- 1 root root 51239 Sep 15 2009 config-2.6.9-89.0.11.ELsmp -rw-r--r-- 1 root root 51614 Nov 3 2009 config-2.6.9-89.0.16.EL -rw-r--r-- 1 root root 51239 Nov 3 2009 config-2.6.9-89.0.16.ELsmp -rw-r--r-- 1 root root 51614 Dec 15 2009 config-2.6.9-89.0.18.EL -rw-r--r-- 1 root root 51239 Dec 15 2009 config-2.6.9-89.0.18.ELsmp -rw-r--r-- 1 root root 51614 Jan 8 2010 config-2.6.9-89.0.19.EL -rw-r--r-- 1 root root 51239 Jan 8 2010 config-2.6.9-89.0.19.ELsmp -rw-r--r-- 1 root root 51614 Feb 2 2010 config-2.6.9-89.0.20.EL -rw-r--r-- 1 root root 51239 Feb 2 2010 config-2.6.9-89.0.20.ELsmp -rw-r--r-- 1 root root 51645 May 6 2010 config-2.6.9-89.0.25.EL -rw-r--r-- 1 root root 51270 May 6 2010 config-2.6.9-89.0.25.ELsmp -rw-r--r-- 1 root root 51645 Aug 20 2010 config-2.6.9-89.0.28.EL -rw-r--r-- 1 root root 51270 Aug 20 2010 config-2.6.9-89.0.28.ELsmp -rw-r--r-- 1 root root 51645 Oct 19 14:27 config-2.6.9-89.31.1.EL -rw-r--r-- 1 root root 51270 Oct 19 15:17 config-2.6.9-89.31.1.ELsmp -rw-r--r-- 1 root root 51645 Dec 2 07:23 config-2.6.9-89.33.1.EL -rw-r--r-- 1 root root 51270 Dec 2 07:41 config-2.6.9-89.33.1.ELsmp -rw-r--r-- 1 root root 51645 Jan 18 15:06 config-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 51270 Jan 18 15:36 config-2.6.9-89.35.1.ELsmp -rw-r--r-- 1 root root 82 Jan 13 2007 device.map -rw-r--r-- 1 root root 7956 Jan 13 2007 e2fs_stage1_5 -rw-r--r-- 1 root root 7684 Jan 13 2007 fat_stage1_5 -rw-r--r-- 1 root root 6996 Jan 13 2007 ffs_stage1_5 -rw------- 1 root root 4091 Jan 28 07:21 grub.conf -rw-r--r-- 1 root root 1333301 Mar 14 2009 initrd-2.6.9-78.0.13.EL.img -rw-r--r-- 1 root root 1319564 Mar 14 2009 initrd-2.6.9-78.0.13.ELsmp.img -rw-r--r-- 1 root root 1342750 Sep 22 2009 initrd-2.6.9-89.0.11.EL.img -rw-r--r-- 1 root root 1327296 Sep 22 2009 initrd-2.6.9-89.0.11.ELsmp.img -rw-r--r-- 1 root root 1342746 Nov 26 2009 initrd-2.6.9-89.0.16.EL.img -rw-r--r-- 1 root root 1327291 Nov 26 2009 initrd-2.6.9-89.0.16.ELsmp.img -rw-r--r-- 1 root root 1342761 Dec 24 2009 initrd-2.6.9-89.0.18.EL.img -rw-r--r-- 1 root root 1327310 Dec 24 2009 initrd-2.6.9-89.0.18.ELsmp.img -rw-r--r-- 1 root root 1342742 Jan 26 2010 initrd-2.6.9-89.0.19.EL.img -rw-r--r-- 1 root root 1327294 Jan 26 2010 initrd-2.6.9-89.0.19.ELsmp.img -rw-r--r-- 1 root root 1342764 Feb 4 2010 initrd-2.6.9-89.0.20.EL.img -rw-r--r-- 1 root root 1327296 Feb 4 2010 initrd-2.6.9-89.0.20.ELsmp.img -rw-r--r-- 1 root root 1343054 Jun 11 2010 initrd-2.6.9-89.0.25.EL.img -rw-r--r-- 1 root root 1327615 Jun 11 2010 initrd-2.6.9-89.0.25.ELsmp.img -rw-r--r-- 1 root root 1343135 Aug 26 2010 initrd-2.6.9-89.0.28.EL.img -rw-r--r-- 1 root root 1327568 Aug 26 2010 initrd-2.6.9-89.0.28.ELsmp.img -rw-r--r-- 1 root root 1343143 Nov 12 07:39 initrd-2.6.9-89.31.1.EL.img -rw-r--r-- 1 root root 1327711 Nov 12 07:39 initrd-2.6.9-89.31.1.ELsmp.img -rw-r--r-- 1 root root 1343556 Jan 13 09:18 initrd-2.6.9-89.33.1.EL.img -rw-r--r-- 1 root root 1328928 Jan 13 09:17 initrd-2.6.9-89.33.1.ELsmp.img -rw-r--r-- 1 root root 1343561 Jan 28 07:21 initrd-2.6.9-89.35.1.EL.img -rw-r--r-- 1 root root 1328788 Jan 28 07:21 initrd-2.6.9-89.35.1.ELsmp.img -rw-r--r-- 1 root root 7028 Jan 13 2007 iso9660_stage1_5 -rw-r--r-- 1 root root 8448 Jan 13 2007 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Jan 13 2007 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 9371 Aug 12 2006 message -rw-r--r-- 1 root root 9371 Aug 12 2006 message.ja -rw-r--r-- 1 root root 7188 Jan 13 2007 minix_stage1_5 -rw-r--r-- 1 root root 9396 Jan 13 2007 reiserfs_stage1_5 -rw-r--r-- 1 root root 3605 Aug 12 2006 splash.xpm.gz -rw-r--r-- 1 root root 512 Jan 13 2007 stage1 -rw-r--r-- 1 root root 103688 Jan 13 2007 stage2 -rw-r--r-- 1 root root 66235 Jan 14 2009 symvers-2.6.9-78.0.13.EL.gz -rw-r--r-- 1 root root 67032 Jan 14 2009 symvers-2.6.9-78.0.13.ELsmp.gz -rw-r--r-- 1 root root 67596 Sep 15 2009 symvers-2.6.9-89.0.11.EL.gz -rw-r--r-- 1 root root 68382 Sep 15 2009 symvers-2.6.9-89.0.11.ELsmp.gz -rw-r--r-- 1 root root 67596 Nov 3 2009 symvers-2.6.9-89.0.16.EL.gz -rw-r--r-- 1 root root 68382 Nov 3 2009 symvers-2.6.9-89.0.16.ELsmp.gz -rw-r--r-- 1 root root 67596 Dec 15 2009 symvers-2.6.9-89.0.18.EL.gz -rw-r--r-- 1 root root 68382 Dec 15 2009 symvers-2.6.9-89.0.18.ELsmp.gz -rw-r--r-- 1 root root 67596 Jan 8 2010 symvers-2.6.9-89.0.19.EL.gz -rw-r--r-- 1 root root 68382 Jan 8 2010 symvers-2.6.9-89.0.19.ELsmp.gz -rw-r--r-- 1 root root 67596 Feb 2 2010 symvers-2.6.9-89.0.20.EL.gz -rw-r--r-- 1 root root 68382 Feb 2 2010 symvers-2.6.9-89.0.20.ELsmp.gz -rw-r--r-- 1 root root 67650 May 6 2010 symvers-2.6.9-89.0.25.EL.gz -rw-r--r-- 1 root root 68434 May 6 2010 symvers-2.6.9-89.0.25.ELsmp.gz -rw-r--r-- 1 root root 67650 Aug 20 2010 symvers-2.6.9-89.0.28.EL.gz -rw-r--r-- 1 root root 68434 Aug 20 2010 symvers-2.6.9-89.0.28.ELsmp.gz -rw-r--r-- 1 root root 67667 Oct 19 14:30 symvers-2.6.9-89.31.1.EL.gz -rw-r--r-- 1 root root 68453 Oct 19 15:17 symvers-2.6.9-89.31.1.ELsmp.gz -rw-r--r-- 1 root root 67701 Dec 2 07:24 symvers-2.6.9-89.33.1.EL.gz -rw-r--r-- 1 root root 68477 Dec 2 07:42 symvers-2.6.9-89.33.1.ELsmp.gz -rw-r--r-- 1 root root 67701 Jan 18 15:07 symvers-2.6.9-89.35.1.EL.gz -rw-r--r-- 1 root root 68477 Jan 18 15:36 symvers-2.6.9-89.35.1.ELsmp.gz -rw-r--r-- 1 root root 780162 Jan 14 2009 System.map-2.6.9-78.0.13.EL -rw-r--r-- 1 root root 797154 Jan 14 2009 System.map-2.6.9-78.0.13.ELsmp -rw-r--r-- 1 root root 768606 Sep 15 2009 System.map-2.6.9-89.0.11.EL -rw-r--r-- 1 root root 785600 Sep 15 2009 System.map-2.6.9-89.0.11.ELsmp -rw-r--r-- 1 root root 768660 Nov 3 2009 System.map-2.6.9-89.0.16.EL -rw-r--r-- 1 root root 785654 Nov 3 2009 System.map-2.6.9-89.0.16.ELsmp -rw-r--r-- 1 root root 768688 Dec 15 2009 System.map-2.6.9-89.0.18.EL -rw-r--r-- 1 root root 785682 Dec 15 2009 System.map-2.6.9-89.0.18.ELsmp -rw-r--r-- 1 root root 768688 Jan 8 2010 System.map-2.6.9-89.0.19.EL -rw-r--r-- 1 root root 785682 Jan 8 2010 System.map-2.6.9-89.0.19.ELsmp -rw-r--r-- 1 root root 768688 Feb 2 2010 System.map-2.6.9-89.0.20.EL -rw-r--r-- 1 root root 785682 Feb 2 2010 System.map-2.6.9-89.0.20.ELsmp -rw-r--r-- 1 root root 768853 May 6 2010 System.map-2.6.9-89.0.25.EL -rw-r--r-- 1 root root 785847 May 6 2010 System.map-2.6.9-89.0.25.ELsmp -rw-r--r-- 1 root root 768881 Aug 20 2010 System.map-2.6.9-89.0.28.EL -rw-r--r-- 1 root root 785875 Aug 20 2010 System.map-2.6.9-89.0.28.ELsmp -rw-r--r-- 1 root root 769059 Oct 19 14:27 System.map-2.6.9-89.31.1.EL -rw-r--r-- 1 root root 786053 Oct 19 15:17 System.map-2.6.9-89.31.1.ELsmp -rw-r--r-- 1 root root 769059 Dec 2 07:23 System.map-2.6.9-89.33.1.EL -rw-r--r-- 1 root root 786053 Dec 2 07:41 System.map-2.6.9-89.33.1.ELsmp -rw-r--r-- 1 root root 769061 Jan 18 15:06 System.map-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 786055 Jan 18 15:36 System.map-2.6.9-89.35.1.ELsmp -rw-r--r-- 1 root root 7272 Jan 13 2007 ufs2_stage1_5 -rw-r--r-- 1 root root 1545561 Jan 14 2009 vmlinuz-2.6.9-78.0.13.EL -rw-r--r-- 1 root root 1483646 Jan 14 2009 vmlinuz-2.6.9-78.0.13.ELsmp -rw-r--r-- 1 root root 1533468 Sep 15 2009 vmlinuz-2.6.9-89.0.11.EL -rw-r--r-- 1 root root 1472648 Sep 15 2009 vmlinuz-2.6.9-89.0.11.ELsmp -rw-r--r-- 1 root root 1536244 Nov 3 2009 vmlinuz-2.6.9-89.0.16.EL -rw-r--r-- 1 root root 1472608 Nov 3 2009 vmlinuz-2.6.9-89.0.16.ELsmp -rw-r--r-- 1 root root 1536254 Dec 15 2009 vmlinuz-2.6.9-89.0.18.EL -rw-r--r-- 1 root root 1472585 Dec 15 2009 vmlinuz-2.6.9-89.0.18.ELsmp -rw-r--r-- 1 root root 1536247 Jan 8 2010 vmlinuz-2.6.9-89.0.19.EL -rw-r--r-- 1 root root 1472612 Jan 8 2010 vmlinuz-2.6.9-89.0.19.ELsmp -rw-r--r-- 1 root root 1536258 Feb 2 2010 vmlinuz-2.6.9-89.0.20.EL -rw-r--r-- 1 root root 1472655 Feb 2 2010 vmlinuz-2.6.9-89.0.20.ELsmp -rw-r--r-- 1 root root 1536380 May 6 2010 vmlinuz-2.6.9-89.0.25.EL -rw-r--r-- 1 root root 1472613 May 6 2010 vmlinuz-2.6.9-89.0.25.ELsmp -rw-r--r-- 1 root root 1536716 Aug 20 2010 vmlinuz-2.6.9-89.0.28.EL -rw-r--r-- 1 root root 1472739 Aug 20 2010 vmlinuz-2.6.9-89.0.28.ELsmp -rw-r--r-- 1 root root 1536908 Oct 19 14:27 vmlinuz-2.6.9-89.31.1.EL -rw-r--r-- 1 root root 1472798 Oct 19 15:17 vmlinuz-2.6.9-89.31.1.ELsmp -rw-r--r-- 1 root root 1536830 Dec 2 07:23 vmlinuz-2.6.9-89.33.1.EL -rw-r--r-- 1 root root 1472713 Dec 2 07:41 vmlinuz-2.6.9-89.33.1.ELsmp -rw-r--r-- 1 root root 1536995 Jan 18 15:06 vmlinuz-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 1472967 Jan 18 15:36 vmlinuz-2.6.9-89.35.1.ELsmp -rw-r--r-- 1 root root 6612 Jan 13 2007 vstafs_stage1_5 -rw-r--r-- 1 root root 9308 Jan 13 2007 xfs_stage1_5
On 3/9/2011 12:12 AM, Simon Matter wrote:
Yes...thank you for the suggestion...since that was the cause of my problem in the first place!! I should have known better; all I had to do was remove some of the outdated kernel files. And when I did the dumb thing of deleting the /boot files, they were moved into the "protected" .Trash-boot directory.
OK, now let us know exactly what you have. Is it CentOS 4 as I expected? If so, the listing of files in /boot should look like so:
[root@abc ~]# ls -laR /boot/ /boot/: total 3771 drwxr-xr-x 4 root root 1024 Mar 3 11:31 . drwxr-xr-x 24 root root 4096 Mar 3 11:37 .. -rw-r--r-- 1 root root 51676 Feb 18 07:41 config-2.6.9-100.EL drwxr-xr-x 2 root root 1024 Mar 3 11:31 grub -rw-r--r-- 1 root root 1364958 Mar 3 11:20 initrd-2.6.9-100.EL.img drwx------ 2 root root 12288 Jul 8 2005 lost+found -rw-r--r-- 1 root root 9371 Aug 13 2006 message -rw-r--r-- 1 root root 9371 Aug 13 2006 message.ja -rw-r--r-- 1 root root 67797 Feb 18 07:41 symvers-2.6.9-100.EL.gz -rw-r--r-- 1 root root 770652 Feb 18 07:41 System.map-2.6.9-100.EL -rw-r--r-- 1 root root 1538264 Feb 18 07:41 vmlinuz-2.6.9-100.EL
/boot/grub: total 198 drwxr-xr-x 2 root root 1024 Mar 3 11:31 . drwxr-xr-x 4 root root 1024 Mar 3 11:31 .. -rw-r--r-- 1 root root 82 Aug 9 2005 device.map -rw-r--r-- 1 root root 7956 Aug 9 2005 e2fs_stage1_5 -rw-r--r-- 1 root root 7684 Aug 9 2005 fat_stage1_5 -rw-r--r-- 1 root root 6996 Aug 9 2005 ffs_stage1_5 -rw------- 1 root root 589 Mar 3 11:31 grub.conf -rw------- 1 root root 593 Aug 9 2005 grub.conf.orig -rw-r--r-- 1 root root 7028 Aug 9 2005 iso9660_stage1_5 -rw-r--r-- 1 root root 8448 Aug 9 2005 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Aug 9 2005 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 7188 Aug 9 2005 minix_stage1_5 -rw-r--r-- 1 root root 9396 Aug 9 2005 reiserfs_stage1_5 -rw-r--r-- 1 root root 3605 Aug 13 2006 splash.xpm.gz -rw-r--r-- 1 root root 512 Aug 9 2005 stage1 -rw-r--r-- 1 root root 103816 Aug 9 2005 stage2 -rw-r--r-- 1 root root 7272 Aug 9 2005 ufs2_stage1_5 -rw-r--r-- 1 root root 6612 Aug 9 2005 vstafs_stage1_5 -rw-r--r-- 1 root root 9308 Aug 9 2005 xfs_stage1_5
/boot/lost+found: total 14 drwx------ 2 root root 12288 Jul 8 2005 . drwxr-xr-x 4 root root 1024 Mar 3 11:31 ..
- I don't know which tool you have used to move things to "Trash" but you
should be aware that it may well be the case that some permissions and or file types like symlinks may not be correct after recovering from "Trash".
- The directory "lost+found" can be recreated using the command
'mklost+found'
- I'm not sure on how to make grub work again, but maybe some steps qre
required after copying everything back to /boot. I hope someone else can give you better info about this.
Simon
Todd
On 3/8/2011 5:51 PM, compdoc wrote:
Besides recovering the files, you'll need to delete some of them to free up space.
Here's an idea of how to go about it:
http://www.howtoforge.com/forums/showthread.php?t=19788
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
OK, here is what I have after manually moving files into /boot/ and /boot/grub/, leaving behind old kernel files. Of course, no links.
/boot/: total 9169 drwxr-xr-x 5 root root 9216 Mar 8 20:24 . drwxr-xr-x 24 root root 4096 Jan 24 08:34 .. -rw-r--r-- 1 root root 51676 Feb 17 22:41 config-2.6.9-100.EL -rw-r--r-- 1 root root 51645 Mar 8 17:38 config-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 51270 Mar 8 17:38 config-2.6.9-89.35.1.ELsmp drwxr-xr-x 2 root root 1024 Mar 8 20:38 grub -rw-r--r-- 1 root root 1343048 Mar 8 20:24 initrd-2.6.9-100.EL.img -rw-r--r-- 1 root root 692224 Mar 8 17:51 initrd-2.6.9-89.35.1.EL.img -rw-r--r-- 1 root root 0 Mar 8 17:51 initrd-2.6.9-89.35.1.ELsmp.img drwx------ 2 root root 12288 Jan 12 2007 lost+found -rw-r--r-- 1 root root 9371 Mar 8 17:46 message -rw-r--r-- 1 root root 9371 Mar 8 17:46 message.ja -rw-r--r-- 1 root root 67797 Feb 17 22:41 symvers-2.6.9-100.EL.gz -rw-r--r-- 1 root root 67701 Mar 8 17:49 symvers-2.6.9-89.35.1.EL.gz -rw-r--r-- 1 root root 68477 Mar 8 17:49 symvers-2.6.9-89.35.1.ELsmp.gz -rw-r--r-- 1 root root 770652 Feb 17 22:41 System.map-2.6.9-100.EL -rw-r--r-- 1 root root 769061 Mar 8 17:48 System.map-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 786055 Mar 8 17:48 System.map-2.6.9-89.35.1.ELsmp drwx------ 2 root root 9216 Mar 8 17:58 .Trash-root -rw-r--r-- 1 root root 1538264 Feb 17 22:41 vmlinuz-2.6.9-100.EL -rw-r--r-- 1 root root 1536995 Mar 8 17:47 vmlinuz-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 1472967 Mar 8 17:47 vmlinuz-2.6.9-89.35.1.ELsmp
/boot/grub: total 345 drwxr-xr-x 2 root root 1024 Mar 8 20:38 . drwxr-xr-x 5 root root 9216 Mar 8 20:24 .. -rw-r--r-- 1 root root 82 Mar 8 17:39 device.map -rw-r--r-- 1 root root 7956 Mar 8 17:40 e2fs_stage1_5 -rw-r--r-- 1 root root 7684 Mar 8 17:40 fat_stage1_5 -rw-r--r-- 1 root root 6996 Mar 8 17:40 ffs_stage1_5 -rw------- 2 root root 4240 Mar 8 20:24 grub.conf -rw-r--r-- 1 root root 7028 Mar 8 17:40 iso9660_stage1_5 -rw-r--r-- 1 root root 8448 Mar 8 17:40 jfs_stage1_5 -rw------- 2 root root 4240 Mar 8 20:24 menu.lst -rw-r--r-- 1 root root 7188 Mar 8 17:40 minix_stage1_5 -rw-r--r-- 1 root root 9396 Mar 8 17:40 reiserfs_stage1_5 -rw-r--r-- 1 root root 512 Mar 8 17:45 stage1 -rw-r--r-- 1 root root 103688 Mar 8 17:45 stage2 -rw-r--r-- 1 root root 67701 Mar 8 18:30 symvers-2.6.9-89.35.1.EL.gz -rw-r--r-- 1 root root 68477 Mar 8 18:30 symvers-2.6.9-89.35.1.ELsmp.gz -rw-r--r-- 1 root root 7272 Mar 8 17:40 ufs2_stage1_5 -rw-r--r-- 1 root root 6612 Mar 8 17:40 vstafs_stage1_5 -rw-r--r-- 1 root root 9308 Mar 8 17:40 xfs_stage1_5
/boot/lost+found: total 22 drwx------ 2 root root 12288 Jan 12 2007 . drwxr-xr-x 5 root root 9216 Mar 8 20:24 ..
/boot/.Trash-root: total 81058 drwx------ 2 root root 9216 Mar 8 17:58 . drwxr-xr-x 5 root root 9216 Mar 8 20:24 .. -rw-r--r-- 1 root root 51502 Jan 14 2009 config-2.6.9-78.0.13.EL -rw-r--r-- 1 root root 51127 Jan 14 2009 config-2.6.9-78.0.13.ELsmp -rw-r--r-- 1 root root 51614 Sep 15 2009 config-2.6.9-89.0.11.EL -rw-r--r-- 1 root root 51239 Sep 15 2009 config-2.6.9-89.0.11.ELsmp -rw-r--r-- 1 root root 51614 Nov 3 2009 config-2.6.9-89.0.16.EL -rw-r--r-- 1 root root 51239 Nov 3 2009 config-2.6.9-89.0.16.ELsmp -rw-r--r-- 1 root root 51614 Dec 15 2009 config-2.6.9-89.0.18.EL -rw-r--r-- 1 root root 51239 Dec 15 2009 config-2.6.9-89.0.18.ELsmp -rw-r--r-- 1 root root 51614 Jan 8 2010 config-2.6.9-89.0.19.EL -rw-r--r-- 1 root root 51239 Jan 8 2010 config-2.6.9-89.0.19.ELsmp -rw-r--r-- 1 root root 51614 Feb 2 2010 config-2.6.9-89.0.20.EL -rw-r--r-- 1 root root 51239 Feb 2 2010 config-2.6.9-89.0.20.ELsmp -rw-r--r-- 1 root root 51645 May 6 2010 config-2.6.9-89.0.25.EL -rw-r--r-- 1 root root 51270 May 6 2010 config-2.6.9-89.0.25.ELsmp -rw-r--r-- 1 root root 51645 Aug 20 2010 config-2.6.9-89.0.28.EL -rw-r--r-- 1 root root 51270 Aug 20 2010 config-2.6.9-89.0.28.ELsmp -rw-r--r-- 1 root root 51645 Oct 19 14:27 config-2.6.9-89.31.1.EL -rw-r--r-- 1 root root 51270 Oct 19 15:17 config-2.6.9-89.31.1.ELsmp -rw-r--r-- 1 root root 51645 Dec 2 07:23 config-2.6.9-89.33.1.EL -rw-r--r-- 1 root root 51270 Dec 2 07:41 config-2.6.9-89.33.1.ELsmp -rw-r--r-- 1 root root 51645 Jan 18 15:06 config-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 51270 Jan 18 15:36 config-2.6.9-89.35.1.ELsmp -rw-r--r-- 1 root root 82 Jan 13 2007 device.map -rw-r--r-- 1 root root 7956 Jan 13 2007 e2fs_stage1_5 -rw-r--r-- 1 root root 7684 Jan 13 2007 fat_stage1_5 -rw-r--r-- 1 root root 6996 Jan 13 2007 ffs_stage1_5 -rw------- 1 root root 4091 Jan 28 07:21 grub.conf -rw-r--r-- 1 root root 1333301 Mar 14 2009 initrd-2.6.9-78.0.13.EL.img -rw-r--r-- 1 root root 1319564 Mar 14 2009 initrd-2.6.9-78.0.13.ELsmp.img -rw-r--r-- 1 root root 1342750 Sep 22 2009 initrd-2.6.9-89.0.11.EL.img -rw-r--r-- 1 root root 1327296 Sep 22 2009 initrd-2.6.9-89.0.11.ELsmp.img -rw-r--r-- 1 root root 1342746 Nov 26 2009 initrd-2.6.9-89.0.16.EL.img -rw-r--r-- 1 root root 1327291 Nov 26 2009 initrd-2.6.9-89.0.16.ELsmp.img -rw-r--r-- 1 root root 1342761 Dec 24 2009 initrd-2.6.9-89.0.18.EL.img -rw-r--r-- 1 root root 1327310 Dec 24 2009 initrd-2.6.9-89.0.18.ELsmp.img -rw-r--r-- 1 root root 1342742 Jan 26 2010 initrd-2.6.9-89.0.19.EL.img -rw-r--r-- 1 root root 1327294 Jan 26 2010 initrd-2.6.9-89.0.19.ELsmp.img -rw-r--r-- 1 root root 1342764 Feb 4 2010 initrd-2.6.9-89.0.20.EL.img -rw-r--r-- 1 root root 1327296 Feb 4 2010 initrd-2.6.9-89.0.20.ELsmp.img -rw-r--r-- 1 root root 1343054 Jun 11 2010 initrd-2.6.9-89.0.25.EL.img -rw-r--r-- 1 root root 1327615 Jun 11 2010 initrd-2.6.9-89.0.25.ELsmp.img -rw-r--r-- 1 root root 1343135 Aug 26 2010 initrd-2.6.9-89.0.28.EL.img -rw-r--r-- 1 root root 1327568 Aug 26 2010 initrd-2.6.9-89.0.28.ELsmp.img -rw-r--r-- 1 root root 1343143 Nov 12 07:39 initrd-2.6.9-89.31.1.EL.img -rw-r--r-- 1 root root 1327711 Nov 12 07:39 initrd-2.6.9-89.31.1.ELsmp.img -rw-r--r-- 1 root root 1343556 Jan 13 09:18 initrd-2.6.9-89.33.1.EL.img -rw-r--r-- 1 root root 1328928 Jan 13 09:17 initrd-2.6.9-89.33.1.ELsmp.img -rw-r--r-- 1 root root 1343561 Jan 28 07:21 initrd-2.6.9-89.35.1.EL.img -rw-r--r-- 1 root root 1328788 Jan 28 07:21 initrd-2.6.9-89.35.1.ELsmp.img -rw-r--r-- 1 root root 7028 Jan 13 2007 iso9660_stage1_5 -rw-r--r-- 1 root root 8448 Jan 13 2007 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Jan 13 2007 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 9371 Aug 12 2006 message -rw-r--r-- 1 root root 9371 Aug 12 2006 message.ja -rw-r--r-- 1 root root 7188 Jan 13 2007 minix_stage1_5 -rw-r--r-- 1 root root 9396 Jan 13 2007 reiserfs_stage1_5 -rw-r--r-- 1 root root 3605 Aug 12 2006 splash.xpm.gz -rw-r--r-- 1 root root 512 Jan 13 2007 stage1 -rw-r--r-- 1 root root 103688 Jan 13 2007 stage2 -rw-r--r-- 1 root root 66235 Jan 14 2009 symvers-2.6.9-78.0.13.EL.gz -rw-r--r-- 1 root root 67032 Jan 14 2009 symvers-2.6.9-78.0.13.ELsmp.gz -rw-r--r-- 1 root root 67596 Sep 15 2009 symvers-2.6.9-89.0.11.EL.gz -rw-r--r-- 1 root root 68382 Sep 15 2009 symvers-2.6.9-89.0.11.ELsmp.gz -rw-r--r-- 1 root root 67596 Nov 3 2009 symvers-2.6.9-89.0.16.EL.gz -rw-r--r-- 1 root root 68382 Nov 3 2009 symvers-2.6.9-89.0.16.ELsmp.gz -rw-r--r-- 1 root root 67596 Dec 15 2009 symvers-2.6.9-89.0.18.EL.gz -rw-r--r-- 1 root root 68382 Dec 15 2009 symvers-2.6.9-89.0.18.ELsmp.gz -rw-r--r-- 1 root root 67596 Jan 8 2010 symvers-2.6.9-89.0.19.EL.gz -rw-r--r-- 1 root root 68382 Jan 8 2010 symvers-2.6.9-89.0.19.ELsmp.gz -rw-r--r-- 1 root root 67596 Feb 2 2010 symvers-2.6.9-89.0.20.EL.gz -rw-r--r-- 1 root root 68382 Feb 2 2010 symvers-2.6.9-89.0.20.ELsmp.gz -rw-r--r-- 1 root root 67650 May 6 2010 symvers-2.6.9-89.0.25.EL.gz -rw-r--r-- 1 root root 68434 May 6 2010 symvers-2.6.9-89.0.25.ELsmp.gz -rw-r--r-- 1 root root 67650 Aug 20 2010 symvers-2.6.9-89.0.28.EL.gz -rw-r--r-- 1 root root 68434 Aug 20 2010 symvers-2.6.9-89.0.28.ELsmp.gz -rw-r--r-- 1 root root 67667 Oct 19 14:30 symvers-2.6.9-89.31.1.EL.gz -rw-r--r-- 1 root root 68453 Oct 19 15:17 symvers-2.6.9-89.31.1.ELsmp.gz -rw-r--r-- 1 root root 67701 Dec 2 07:24 symvers-2.6.9-89.33.1.EL.gz -rw-r--r-- 1 root root 68477 Dec 2 07:42 symvers-2.6.9-89.33.1.ELsmp.gz -rw-r--r-- 1 root root 67701 Jan 18 15:07 symvers-2.6.9-89.35.1.EL.gz -rw-r--r-- 1 root root 68477 Jan 18 15:36 symvers-2.6.9-89.35.1.ELsmp.gz -rw-r--r-- 1 root root 780162 Jan 14 2009 System.map-2.6.9-78.0.13.EL -rw-r--r-- 1 root root 797154 Jan 14 2009 System.map-2.6.9-78.0.13.ELsmp -rw-r--r-- 1 root root 768606 Sep 15 2009 System.map-2.6.9-89.0.11.EL -rw-r--r-- 1 root root 785600 Sep 15 2009 System.map-2.6.9-89.0.11.ELsmp -rw-r--r-- 1 root root 768660 Nov 3 2009 System.map-2.6.9-89.0.16.EL -rw-r--r-- 1 root root 785654 Nov 3 2009 System.map-2.6.9-89.0.16.ELsmp -rw-r--r-- 1 root root 768688 Dec 15 2009 System.map-2.6.9-89.0.18.EL -rw-r--r-- 1 root root 785682 Dec 15 2009 System.map-2.6.9-89.0.18.ELsmp -rw-r--r-- 1 root root 768688 Jan 8 2010 System.map-2.6.9-89.0.19.EL -rw-r--r-- 1 root root 785682 Jan 8 2010 System.map-2.6.9-89.0.19.ELsmp -rw-r--r-- 1 root root 768688 Feb 2 2010 System.map-2.6.9-89.0.20.EL -rw-r--r-- 1 root root 785682 Feb 2 2010 System.map-2.6.9-89.0.20.ELsmp -rw-r--r-- 1 root root 768853 May 6 2010 System.map-2.6.9-89.0.25.EL -rw-r--r-- 1 root root 785847 May 6 2010 System.map-2.6.9-89.0.25.ELsmp -rw-r--r-- 1 root root 768881 Aug 20 2010 System.map-2.6.9-89.0.28.EL -rw-r--r-- 1 root root 785875 Aug 20 2010 System.map-2.6.9-89.0.28.ELsmp -rw-r--r-- 1 root root 769059 Oct 19 14:27 System.map-2.6.9-89.31.1.EL -rw-r--r-- 1 root root 786053 Oct 19 15:17 System.map-2.6.9-89.31.1.ELsmp -rw-r--r-- 1 root root 769059 Dec 2 07:23 System.map-2.6.9-89.33.1.EL -rw-r--r-- 1 root root 786053 Dec 2 07:41 System.map-2.6.9-89.33.1.ELsmp -rw-r--r-- 1 root root 769061 Jan 18 15:06 System.map-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 786055 Jan 18 15:36 System.map-2.6.9-89.35.1.ELsmp -rw-r--r-- 1 root root 7272 Jan 13 2007 ufs2_stage1_5 -rw-r--r-- 1 root root 1545561 Jan 14 2009 vmlinuz-2.6.9-78.0.13.EL -rw-r--r-- 1 root root 1483646 Jan 14 2009 vmlinuz-2.6.9-78.0.13.ELsmp -rw-r--r-- 1 root root 1533468 Sep 15 2009 vmlinuz-2.6.9-89.0.11.EL -rw-r--r-- 1 root root 1472648 Sep 15 2009 vmlinuz-2.6.9-89.0.11.ELsmp -rw-r--r-- 1 root root 1536244 Nov 3 2009 vmlinuz-2.6.9-89.0.16.EL -rw-r--r-- 1 root root 1472608 Nov 3 2009 vmlinuz-2.6.9-89.0.16.ELsmp -rw-r--r-- 1 root root 1536254 Dec 15 2009 vmlinuz-2.6.9-89.0.18.EL -rw-r--r-- 1 root root 1472585 Dec 15 2009 vmlinuz-2.6.9-89.0.18.ELsmp -rw-r--r-- 1 root root 1536247 Jan 8 2010 vmlinuz-2.6.9-89.0.19.EL -rw-r--r-- 1 root root 1472612 Jan 8 2010 vmlinuz-2.6.9-89.0.19.ELsmp -rw-r--r-- 1 root root 1536258 Feb 2 2010 vmlinuz-2.6.9-89.0.20.EL -rw-r--r-- 1 root root 1472655 Feb 2 2010 vmlinuz-2.6.9-89.0.20.ELsmp -rw-r--r-- 1 root root 1536380 May 6 2010 vmlinuz-2.6.9-89.0.25.EL -rw-r--r-- 1 root root 1472613 May 6 2010 vmlinuz-2.6.9-89.0.25.ELsmp -rw-r--r-- 1 root root 1536716 Aug 20 2010 vmlinuz-2.6.9-89.0.28.EL -rw-r--r-- 1 root root 1472739 Aug 20 2010 vmlinuz-2.6.9-89.0.28.ELsmp -rw-r--r-- 1 root root 1536908 Oct 19 14:27 vmlinuz-2.6.9-89.31.1.EL -rw-r--r-- 1 root root 1472798 Oct 19 15:17 vmlinuz-2.6.9-89.31.1.ELsmp -rw-r--r-- 1 root root 1536830 Dec 2 07:23 vmlinuz-2.6.9-89.33.1.EL -rw-r--r-- 1 root root 1472713 Dec 2 07:41 vmlinuz-2.6.9-89.33.1.ELsmp -rw-r--r-- 1 root root 1536995 Jan 18 15:06 vmlinuz-2.6.9-89.35.1.EL -rw-r--r-- 1 root root 1472967 Jan 18 15:36 vmlinuz-2.6.9-89.35.1.ELsmp -rw-r--r-- 1 root root 6612 Jan 13 2007 vstafs_stage1_5 -rw-r--r-- 1 root root 9308 Jan 13 2007 xfs_stage1_5
On 3/9/2011 12:12 AM, Simon Matter wrote:
Yes...thank you for the suggestion...since that was the cause of my problem in the first place!! I should have known better; all I had to do was remove some of the outdated kernel files. And when I did the dumb thing of deleting the /boot files, they were moved into the "protected" .Trash-boot directory.
OK, now let us know exactly what you have. Is it CentOS 4 as I expected? If so, the listing of files in /boot should look like so:
[root@abc ~]# ls -laR /boot/ /boot/: total 3771 drwxr-xr-x 4 root root 1024 Mar 3 11:31 . drwxr-xr-x 24 root root 4096 Mar 3 11:37 .. -rw-r--r-- 1 root root 51676 Feb 18 07:41 config-2.6.9-100.EL drwxr-xr-x 2 root root 1024 Mar 3 11:31 grub -rw-r--r-- 1 root root 1364958 Mar 3 11:20 initrd-2.6.9-100.EL.img drwx------ 2 root root 12288 Jul 8 2005 lost+found -rw-r--r-- 1 root root 9371 Aug 13 2006 message -rw-r--r-- 1 root root 9371 Aug 13 2006 message.ja -rw-r--r-- 1 root root 67797 Feb 18 07:41 symvers-2.6.9-100.EL.gz -rw-r--r-- 1 root root 770652 Feb 18 07:41 System.map-2.6.9-100.EL -rw-r--r-- 1 root root 1538264 Feb 18 07:41 vmlinuz-2.6.9-100.EL
/boot/grub: total 198 drwxr-xr-x 2 root root 1024 Mar 3 11:31 . drwxr-xr-x 4 root root 1024 Mar 3 11:31 .. -rw-r--r-- 1 root root 82 Aug 9 2005 device.map -rw-r--r-- 1 root root 7956 Aug 9 2005 e2fs_stage1_5 -rw-r--r-- 1 root root 7684 Aug 9 2005 fat_stage1_5 -rw-r--r-- 1 root root 6996 Aug 9 2005 ffs_stage1_5 -rw------- 1 root root 589 Mar 3 11:31 grub.conf -rw------- 1 root root 593 Aug 9 2005 grub.conf.orig -rw-r--r-- 1 root root 7028 Aug 9 2005 iso9660_stage1_5 -rw-r--r-- 1 root root 8448 Aug 9 2005 jfs_stage1_5 lrwxrwxrwx 1 root root 11 Aug 9 2005 menu.lst -> ./grub.conf -rw-r--r-- 1 root root 7188 Aug 9 2005 minix_stage1_5 -rw-r--r-- 1 root root 9396 Aug 9 2005 reiserfs_stage1_5 -rw-r--r-- 1 root root 3605 Aug 13 2006 splash.xpm.gz -rw-r--r-- 1 root root 512 Aug 9 2005 stage1 -rw-r--r-- 1 root root 103816 Aug 9 2005 stage2 -rw-r--r-- 1 root root 7272 Aug 9 2005 ufs2_stage1_5 -rw-r--r-- 1 root root 6612 Aug 9 2005 vstafs_stage1_5 -rw-r--r-- 1 root root 9308 Aug 9 2005 xfs_stage1_5
/boot/lost+found: total 14 drwx------ 2 root root 12288 Jul 8 2005 . drwxr-xr-x 4 root root 1024 Mar 3 11:31 ..
- I don't know which tool you have used to move things to "Trash" but you
should be aware that it may well be the case that some permissions and or file types like symlinks may not be correct after recovering from "Trash".
- The directory "lost+found" can be recreated using the command
'mklost+found'
- I'm not sure on how to make grub work again, but maybe some steps qre
required after copying everything back to /boot. I hope someone else can give you better info about this.
Simon
Todd
On 3/8/2011 5:51 PM, compdoc wrote:
Besides recovering the files, you'll need to delete some of them to free up space.
Here's an idea of how to go about it:
http://www.howtoforge.com/forums/showthread.php?t=19788
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Simon -
Did I screw up? I deleted what was in /boot!
Yes :(
Now don't reboot!
OK, if you try to reboot now it won't come up, so be warned.
You should be able to reinstall the packages which have files in /boot, and then reconfigure grub so it will be able to boot again.
Unfortunately my time is up for today, but I hope someone else can help you out.
The packages which need to be forceinstalled are at least: kernel grub redhat-logos
Sorry I have to finish here, hope someone can help you further,
Simon
Wait for the next mail...
Simon
Todd
On 3/8/2011 3:31 PM, Simon Matter wrote:
Here is the output of mount:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc1 on /boot type ext3 (rw)
^^^^^ It's mounted here, the device is /dev/hdc1.
But now, also show us 'df' and 'ls -la /boot'
How did you boot if /boot was empty?
Simon
none 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)
Does not appear to be mounted...correct?
Todd
On 3/8/2011 3:08 PM, Simon Matter wrote:
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
Hm, that's not good.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
Is /boot mounted? Please show as the output of 'mount'.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
First, to check the filesystem you have to unmount it. And then to check, you usually give the device name, not it's label (I'm not sure it work by naming with the label). Usually something like
fsck.ext3 /dev/sda1
Simon
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software Petaluma, CA 94952
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
on 15:39 Tue 08 Mar, Todd Cary (todd@aristesoftware.com) wrote:
Simon -
Did I screw up? I deleted what was in /boot!
Yes, as others have noted.
Lessons:
1: Don't go randomly/arbitrarily deleting system files (unless you're curious to see what happens when randomly deleting systems files).
2: Understand how Linux functions. E.g.: the boot process, and the significance of the /boot directory/filesystem.
3: Use your package management system. If you /are/ going to delete arbitrary system files, doing it through your package manager is going to a) give you some idea when you're about to do something really stupid (generally other Really Important Stuff depends on them) and b) at the very least does the damage in an orderly manner.
4: Have a boot disk. Know how to use it.
5: Know how to restore GRUB and an emergency boot kernel.
Circling back to #3: your package management system can also dig you out of this hole.
You should be able to identify and replace all files in an arbitrary tree, for example, /boot, using an RPM bash one-liner:
$ rpm -qa # lists all packages installed $ rpm -ql <package> # lists all files in a package $ command | grep -q <expression> # success/fail on match / no match $ command1 && command2 # runs command2 if command1 exits true # rpm -Uvh --replacepkgs <package list> # (re)installs packages $ $( command ) # executes output of 'command'
Putting that together:
rpm -Uvh --replacepkgs $( for pkg in $( rpm -qa ); do rpm -ql $pkg | grep -q ^/boot && && echo $pkg done )
Incidentally, the list of packages works out to:
filesystem-2.4.0-3.el5 grub-0.97-13.5 kernel-2.6.18-194.17.1.el5 redhat-logos-4.9.99-11.el5.centos
On 3/8/2011 5:17 PM, Todd Cary wrote:
Here is the output of mount:
/dev/hdc1 on /boot type ext3 (rw)
Does not appear to be mounted...correct?
Looks like /dev/hdc1 to me.
Is this a strictly-IDE system with boot disk/CD cables backwards from normal?
Les -
This is a one disk simple server I use for exchanging files (ftp) and post images. It has not been touched in a LONG time other than yum update and rsync. One of the reasons I am not very compitent with Linux...set it up and it just runs.
Todd
On 3/8/2011 3:38 PM, Les Mikesell wrote:
On 3/8/2011 5:17 PM, Todd Cary wrote:
Here is the output of mount:
/dev/hdc1 on /boot type ext3 (rw)
Does not appear to be mounted...correct?
Looks like /dev/hdc1 to me.
Is this a strictly-IDE system with boot disk/CD cables backwards from normal?
On Tue, Mar 8, 2011 at 6:44 PM, Todd Cary todd@aristesoftware.com wrote:
Les -
This is a one disk simple server I use for exchanging files (ftp) and post images. It has not been touched in a LONG time other than yum update and rsync. One of the reasons I am not very compitent with Linux...set it up and it just runs.
Todd
On 3/8/2011 3:38 PM, Les Mikesell wrote:
On 3/8/2011 5:17 PM, Todd Cary wrote:
Here is the output of mount:
/dev/hdc1 on /boot type ext3 (rw)
Does not appear to be mounted...correct?
Looks like /dev/hdc1 to me.
Is this a strictly-IDE system with boot disk/CD cables backwards from normal?
The confusion is because your PATA drive is plugged into the second PATA port., not the first one. This is not usually a big deal, but it can be *very* confusing when everyone talks about "play with /dev/hda" commands and your /boot is on /dev/hdc.
Deleting /boot was a not-very-good thing to do. You deleted your /boot/grub/* files, which hold your disk configuration. If you don't back these up, you need to get a copy of one from a similarly set up machine and rebuild those files, then use the the "grub-install" command to reload the MBR, ideally *before* you reboot the machine.
Alternatively, at this point, you might consider doing a forklift upgrade to a new OS. But if you accidentally reboot before getting it all straightened out, you can boot from a live CD to mount your old OS and keep tinkering with the old OS to get it right.
A couple of lessons should be rememberd here:
1) CentOS and RHEL and Fedora, by default, keep your old kernels lying around in /boot, even if you don't use them anymore. It's worth reviewing the list of kernels now and then and flushing the spares, especially if you're doing frequent updates of kernels.
2) Always backup your systems. *ALWAYS*. External drives are cheap, and so is rsnapshot and other tools. Your time recovering from this is not cheap.
3) It's amazingly handy to be able to rebuild your development systems from scratch if you need to.
When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files.
If I do a df -h, there is no available space yet it shows that it has a lot of used space.
The fstab shows the following:
# This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / 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 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,exec,noauto,managed 0 0
# fschk.ext3 /boot gives this error:
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 am not sure what I should do next.
Thank you in advance for any suggestions...
Todd
(caveat: I'm as newbie at this as you)
I can't tell from your email which partition /boot is mounted to (/dev/hda1?), but to get a list of the alternative superblocks, you can do this:
dumpe2fs /dev/hda1 | grep superblock
AFAIK, dumpe2fs doesn't support labels as device specifiers, so you will need to substitute /dev/hda1 for whichever partition /boot is mounted to.
You should probably boot into single-user mode and unmount /boot before running fsck.ext3 -b <superblock> <device> on it btw.
Also:
http://www.cyberciti.biz/faq/recover-bad-superblock-from-corrupted-partition... http://planet.admon.org/using-alternative-superblock-to-check-ext3/
HTH
Steve
-
compdoc -
Dr. Ed Morbius -
John R Pierce -
Les Mikesell -
Nico Kadel-Garcia -
Rudi Ahlers -
Simon Matter -
Steve Barnes -
Todd Cary