[opensuse] File system is not clean
openSUSE 12.1 64 bit AMD processor; I have noticed the message 'File system is not clean' when I boot the system. Other than slowing down the boot process this doesn't seem to have another effect on the system. I couldn't find any reason via Google and am wondering if this condition is serious, or can I ignore it? Also, when the system is rebooted the widgets on the icon bar are rearranged, even thought they are locked. Is there a solution to this? Enlightenment will be much appreciated. Thanks in advance. -- Stephen P. Molnar, Ph.D. Life is a fuzzy set Foundation for Chemistry Stochastic and multivariate http://www.FoundationForChemistry.com (614)312-7528 (c) Skype: smolnar1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17/02/12 23:21, Stephen P. Molnar wrote:
openSUSE 12.1 64 bit AMD processor;
I have noticed the message 'File system is not clean' when I boot the system. Other than slowing down the boot process this doesn't seem to have another effect on the system. I couldn't find any reason via Google and am wondering if this condition is serious, or can I ignore it?
Also, when the system is rebooted the widgets on the icon bar are rearranged, even thought they are locked. Is there a solution to this?
Enlightenment will be much appreciated.
Thanks in advance.
I begin with the assumption that your oS 12.1 system has been installed to an HDD partition which has been formatted with ext4 (or even ext3 or ext2 but not some of the other 'exotic' file systems). If so then proceed as follows - if not then do not do what follows. Find out on which partition (sdaX) your / is installed - look at the fstab in /etc/fstab to see where "/" is sitting. Boot up your system and at the grub boot menu prompt enter on the kernel boot command line "init 1" and let the system to boot. At the logon prompt which you will see logon as root. Then type- mount -o remount,ro /dev/sdaX where X is the number of the partition shown in fstab where / is sitting (or you could look in /boot/grub/menu.lst to see the same information). The "o" mentioned here are not zeros but the letter "o". Then type e2fsck /dev/sdaX <ENTER> and let the filesystem be checked for errors. Answer any questions which may arise as to what you want done with any errors. (The usual thing is to allow e2fsck to do its job by answering yes.) After this check is finished and errors repaired reboot the system (which is the simplest thing to do; there is something else you could do - but just reboot: hit the reset button). Any questions - ask BC -- Men never do good unless necessity drives them to it; but when they are free to choose and can do just as they please, confusion and disorder become rampant. Niccolo Machiavelli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/17/2012 07:49 AM, Basil Chupin wrote:
On 17/02/12 23:21, Stephen P. Molnar wrote:
openSUSE 12.1 64 bit AMD processor;
I have noticed the message 'File system is not clean' when I boot the system. Other than slowing down the boot process this doesn't seem to have another effect on the system. I couldn't find any reason via Google and am wondering if this condition is serious, or can I ignore it?
Also, when the system is rebooted the widgets on the icon bar are rearranged, even thought they are locked. Is there a solution to this?
Enlightenment will be much appreciated.
Thanks in advance.
I begin with the assumption that your oS 12.1 system has been installed to an HDD partition which has been formatted with ext4 (or even ext3 or ext2 but not some of the other 'exotic' file systems). If so then proceed as follows - if not then do not do what follows.
Find out on which partition (sdaX) your / is installed - look at the fstab in /etc/fstab to see where "/" is sitting.
Boot up your system and at the grub boot menu prompt enter on the kernel boot command line "init 1" and let the system to boot.
At the logon prompt which you will see logon as root.
Then type-
mount -o remount,ro /dev/sdaX
where X is the number of the partition shown in fstab where / is sitting (or you could look in /boot/grub/menu.lst to see the same information). The "o" mentioned here are not zeros but the letter "o".
Then type
e2fsck /dev/sdaX <ENTER>
and let the filesystem be checked for errors. Answer any questions which may arise as to what you want done with any errors. (The usual thing is to allow e2fsck to do its job by answering yes.)
After this check is finished and errors repaired reboot the system (which is the simplest thing to do; there is something else you could do - but just reboot: hit the reset button).
Any questions - ask
BC
Thank you for your prompt and detailed reply. I followed your instructions and solved the problem. No more long lines in the boot messages. The widgets were still rearranged when I rebooted the system, but that , of course, is a different problem. I really appreciate your detailed guidance, it's yust what a OS dummy such as myself needed. -- Stephen P. Molnar, Ph.D. Life is a fuzzy set Foundation for Chemistry Stochastic and multivariate http://www.FoundationForChemistry.com (614)312-7528 (c) Skype: smolnar1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18/02/12 01:04, Stephen P. Molnar wrote:
On 02/17/2012 07:49 AM, Basil Chupin wrote: [pruned]
After this check is finished and errors repaired reboot the system (which is the simplest thing to do; there is something else you could do - but just reboot: hit the reset button).
Any questions - ask
BC
Thank you for your prompt and detailed reply. I followed your instructions and solved the problem. No more long lines in the boot messages.
Glad to have been of help. If you have a sudden power failure, for example, it would pay to go through this process to be on the safe side, even though it may appear to be a waste of time. We had a sudden and inexplicable (to us, seeing as how the sun was shining :-) ) power failure after which my wife's computer started playing up. Even though at boot time the system performs the fsck check it cannot fix big faults and I had to do the above and manually allow efsck to do many repairs to the file system.
The widgets were still rearranged when I rebooted the system, but that , of course, is a different problem.
Had the same hassle a long time ago. Unlock the widgets. Go to Panel Options>Panel Settings and *move* the widgets into their correct spots. Exit this and Lock the widgets. Right click on Desktop, LEAVE>LOGOUT and log back on as yourself. The widgets should be in the locations you put them in.
I really appreciate your detailed guidance, it's yust what a OS dummy such as myself needed.
That's why this list exists and where young and old, experienced and inexperienced can ask questions :-) . BC -- Men never do good unless necessity drives them to it; but when they are free to choose and can do just as they please, confusion and disorder become rampant. Niccolo Machiavelli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Basil Chupin -
Stephen P. Molnar