On 05/04/15 22:31, Marco Calistri wrote:
Il 05/04/2015 04:28, Basil Chupin ha scritto:
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>
and, if errors were found, follow the prompt(s) to have any errors repaired.
A few minutes ago I tried this on the laptop which has Tumbleweed installed on ext4 file system (I didn't want to this experiment on my main system on the desktop).
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
The above sequence of commands worked for years in SuSE and then openSUSE so why has it now stopped working?
Or put another way, how does one go about manually checking the file system for errors by running "e2fsck"?
Why run "e2fsck" manually you may ask? Because I have found that the checking which is done automatically after X number of boots by the built-in system does not always pickup the errors in the ext3/4 file system.
(Don't try to convince me otherwise because I have proven that to myself several times over the years.
In any case, this is not the point. The point is why I now cannot check the file system using the method above which was spelt out in detail in the Administrative Manual which came with the version of S.u.S.E.?)
Can anyone please give details on how now to manually check the ext3/4 file system for errors?
[#] sda5 is where / of TW is installed.
BC
Hi, I have not tried your experience so far on my standard 13.2 nor Tumbleweed which I have not available here but if it really doesn't work you can also try to verify your disc by booting your system with gparted: http://gparted.org/livecd.php which contains a check file-system option.
The SystemRescueCD (http://www.sysresccd.org/) also contains GParted which will check file systems (Including, BTW btrfs - with a qualification!). However, the check in GParted will do a check *AND* repair which is NOT what I really want. I don't know if GParted uses 'e2fsck -p' in this check process but I have a note in my "little black book" which states that this command has a problem and that it causes problems/corruptions and so not to use it but rather simply follow the prompts which e2fsck gives you if it comes up with errors in the file system to repair any damage. So, from my point of view the GParted path is not what I want. In any case, using either the GParted CD you mention or GParted in the SystemRescueCD is having to use a third-party application to do something which was - and should be - available in openSUSE itself. As I state in my initial post following the commands I quote when and after booting into S.u.S.E./openSUSE checked the file system so why should this still be the case? Or are we now moving towards the MS model where everything is done by 3rd party software? 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