On 06/04/15 22:33, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
In a galaxy long ago one could boot into openSUSE by putting level 1 in the boot command and login as root after which you could manually check for any errors in the ext3 or ext4 file system by issuing the following commands:
mount -o remount, ro /dev/<hdX>/<sdX>
followed by
e2fsck /dev/<hdX>/<sdX> Since long time ago I don't use this approach, it failed for one or another reason. Instead, I keep some type of rescue system and I do
On 2015-04-05 09:28, Basil Chupin wrote: the fsck of the target root from there.
It can be the installation DVD, or another partition on the same hard disk with at least a minimal install. Recently, it can be the XFCE CD rescue image which you get from our download page and place on a USB stick. Yes, it is of course slower than the real system, but you get an openSUSE graphical system running.
I am not about to go trying out your suggestion as I simply do not have the time but please refer to my earlier post where I stated that the RESCUE DISC - at least for 13.2 - contained GParted which does a CHECK AND *REPAIR* run on the partition you want checked. I also stated that if this Check and Repair feature in GParted used the command 'e2fsck -p' then I do NOT want any part of it because an entry in my "little black book" states that this '-p' option has problems and can corrupt the file system - and therefore I have never used it. So, any 'rescue' disc is a no-no unless it uses some other command to do e2fsck or if the '-p' option in this 'e2fsck' command has been fixed. Since I have not received any comment re what "check and repair" in GParted really does and/or if the "-p" option in e2fsck has now been rectified, I am not using any 'rescue disc' which has GParted.
Booting into level 1 seems to be OK and logging in as root was OK but then when I issued the command-
mount -o remount, ro /dev/sda5 [#]
I got the response (error msg) that-
mount: / is busy
It probably means that some files are open for writing. Maybe you can find which with lsof.
Thanks for this, I will use 'lsof' to check this. However, as I already stated, in the past the commands I mentioned in my OP did the job perfectly. The same commands should also work as well NOW - otherwise it is a regression in openSUSE (nee S.u.S.E.). BC -- Using openSUSE 13.2, KDE 4.14.6 & kernel 3.19.3-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org