Lobes06
Group: Members
Posts: 5
Joined: Aug. 2006 |
 |
Posted: Sep. 10 2006,01:37 |
 |
| Quote (brianw @ Sep. 09 2006,21:04) | Sorry for the delay in responding. When you say that you run the command I am assuming you run the mount command is that correct?
Have you manually run the fsck command at the prompt before a reboot?
If you type fsck --help (use sudo in front if you are not currently root) you get a list of the options. If you use -p or -y the process will be automatic (-p repairs automatically -y answers yes automatically each time a fix is required). |
Here are the results from running fsck -v
fsck 1.34-WIP (21-May-2003)
e2fsck 1.34-WIP (21-May-2003)
/dev/hda1 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? yes
/dev/hda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
11804 inodes used (0%)
14 non-contiguous inodes (0.1%)
#of inodes with ind/dind/tind blocks: 412/0/0
91514 blocks used (2%)
0 bad blocks
0 large files
5360 regular files
1018 directories
1489 character device files
3390 block device files
3 fifos
0 links
527 symbolic links (527 fast symbolic links)
8 sockets
--------
11795 files
I guess that means there were no errors? I guess I can just live with having to boot twice whenever I want to use it (or just not turn it off)! But it would be nice to at least know whats causing it...
Thanks again for your help, I sure do appreciate it.
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
