Hylton Conacher(ZR1HPC) wrote:
I entered the password and remounted / as rw. Initially I tried #fsck / which returned that the journal had neen recovered, however there was a JBD error which I'll cover in anoter mail. After CTRL-D to reboot the system again complained about / needing checking.
You should never ever do am fsck on a rw mounted partition.
Would a kind sole please let me know what fsck syntax I should use if the / or any other partition needs repairing? The fsck error from hell has meant that I have left the machine running and susceptible to power outages.
It depends on the filesystem. for ext3, man fsck.ext3. In a pinch, fsck.ext3 -f /dev/hdxx, replacing xx with the correct drive and
Joe Morris (NTM) wrote: partition. Joe Morris (NTM) wrote:
Hylton Conacher(ZR1HPC) wrote:
I entered the password and remounted / as rw. Initially I tried #fsck / which returned that the journal had neen recovered, however there was a JBD error which I'll cover in anoter mail. After CTRL-D to reboot the system again complained about / needing checking.
You should never ever do am fsck on a rw mounted partition. Why, Surely fsck would need to write changes to correct the fs? So you are saying that eventhough they mention the option of remounting RW, I shouldm't?
Would a kind sole please let me know what fsck syntax I should use if the / or any other partition needs repairing? The fsck error from hell has meant that I have left the machine running and susceptible to power outages.
It depends on the filesystem. for ext3, man fsck.ext3. In a pinch, fsck.ext3 -f /dev/hdxx, replacing xx with the correct drive and partition. Doh, Forgot to mention the fs. fs is ext3. -- ======================================================================== Currently using unpatched SuSE 9.2 Professional with KDE and Mozilla 1.7.2 Linux user # 229959 at http://counter.li.org ========================================================================