root partition was full and problem start

[unin89]

We have SunOS 5.7 m/c. Following is the situation and problem what we are facing -



- The root partition was full.

- No login was possible on server (not from console also)

- M/c was power swithced off

- After this only console login is possible. FTP is possible. No telnet is possible.



I want to know what could be the probable reasons. Also what files I have to check on the server to see that they are in normal state.



Regards,

Rahul

More Information:

1. This imaginary machine has a Linux boot partition on /dev/hda5, a root partition on /dev/hda7, and a Windows installation on /dev/hda1
2. When I got up the next morning I found a bad surprise: my small root partition was full, there was no disk space, so I had a bad upgrade of 09/06 and the 08
3. 1 post - 1 authorHi everyone, I posted this first to thread 'Boot problem - "Gave up waiting for root device
4. You cannot perform a full unencapsulation and still maintain Volume Manager functionality if the root disk is the ONLY disk in the rootdg diskgroup
5. 22 posts - 14 authors - Last post: Apr 11, 2005Now the problem is that the root file system is showing 97 %
6. N900 - Issues surrounding full root partition (No space left on device) Nokia N900
7. 3 GB was the largest I could make my root partition
8. No, for root partition installations because the XFS superblock is written at block zero, where LILO would be installed

[trandu_tkqn]

Your full file system is the problem. You must check for what happened to fill it up and then decide what to do about it so it will not happen again.



Check your /var/adm/messages file for possible clues - if you have access to SunSolve, search for "filesystem full" or "/ full no login"- It gives different possible problems - one may be this:



This is caused by a full file system and the system has no space

to write its utmpx (login info) entry.



To get around this condition the system must be booted up

into single user mode. Then clear (do not delete) the files:



/var/adm/utmp

/var/adm/utmpx



This can be done by typing:



#cat /dev/null > filename



This command will zero out the file but keep it there with

the correct permissions.



In some cases after removing these files your /var filesystem may

still be full. In this case type:



du -askd /var |sort -nr |more



This will give you a listing of the files from largest to smallest

on the /var filesystem.



In order to create space you may zero out the following files:



/var/cron/log

/var/spool/lp/logs

/var/adm/messages



You may also check the following for any large files that can be deleted:



/.wastebasket

/lost found



----------------------------------------------------

Subsequent logins should work fine after this.



Keywords: var, umptx, wtmpx, utmp, wtmp







full file system



changing a flat filesystem

More Information:

1. 2002 1:09 PM > Subject: Re: [uClinux-dev] Boot problem for Samsung 4510B in new uClinux > full distribution > > > VAN DUC UY <ducuy@tlnet
2. It is now possible to encrypt an entire Linux system, including root, the boot partition, and even the kernel itself
3. If you have WINXP installed to MBR on your hard drive, install LILO to the root partition instead of the MBR
4. For example, if the kernel in question was built on a system that used `/dev/hda1' as the root partition, then the default root device would be `/dev/hda1'
5. Since I use XOSL or NT boot loader as my boot manager, I always choose not to install GRUB on the MBR, but I install it on the root partition instead

[linhxuankhanh]

Thanx for the ans. The null writting over utmp and wtmp has already done. Also the space has been made on the root file system. Still the problem persist.



Regards,

Rahul

More Information:

1. …but anyway, what problems can rise the GRUB? i don't know why my Linux don't want to starting up
2. For the sake of this section, let's assume that /dev/sda1 is a dedicated /boot partition and /dev/sda2 is the root partition of your distro
3. An important prerequisite of this procedure is that the root partition is less that half full (so that a copy of it can be created in a logical volume)
4. Boot into the live user mode and mount the root partition
5. Following is the situation and problem what we are facing - - The root partition was full