[opensuse] Manually checking ext4 file system for any errors
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 -- 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
Le 05/04/2015 09:28, Basil Chupin a écrit :
Can anyone please give details on how now to manually check the ext3/4 file system for errors?
not a real answer, but you can still boot a rescue or live cd (if nothing else works) think also to try bdablocks -s /dev/sd... just in case some bad sectors shows jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/04/15 18:18, jdd wrote:
Le 05/04/2015 10:17, jdd a écrit :
bdablocks -s /dev/sd...
ark...
badblocks, of course :-(
Of course.....
sorry
Is OK :-) . 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
On 05/04/15 18:17, jdd wrote:
Le 05/04/2015 09:28, Basil Chupin a écrit :
Can anyone please give details on how now to manually check the ext3/4 file system for errors?
not a real answer, but you can still boot a rescue or live cd (if nothing else works)
Thanks for the suggestion. Apart from the fact that it takes a half-hour to boot the damn Rescue Disk it "cannot find <the drive one wants to work on> in /etc/fstab". As useful as tits on a bull.
think also to try
bdablocks -s /dev/sd...
just in case some bad sectors shows
Never found a problem with bad sectors in the past. In any case bad sectors are handled by other built-in thingies :-) . 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
Le 06/04/2015 09:08, Basil Chupin a écrit :
Apart from the fact that it takes a half-hour to boot the damn Rescue Disk it "cannot find <the drive one wants to work on> in /etc/fstab".
what does fstab have to do with the problem? fskhave to be used on non mounted system, use better fdisk -l ti know what the partition are I have two (old) disks with bad sectors on my desk, tested last week... fsck is for file system problems, badblocks for hard disk problem. and by the way usb booting is faster than dvd :-) I know it's slow, using ssd on my main, most anything else seems desperately slow :-)) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Basil Chupin composed on 2015-04-06 17:08 (UTC+1000):
jdd wrote:
Basil Chupin composed:
Can anyone please give details on how now to manually check the ext3/4 file system for errors?
not a real answer, but you can still boot a rescue or live cd (if nothing else works)
Thanks for the suggestion.
Apart from the fact that it takes a half-hour to boot the damn Rescue Disk it "cannot find <the drive one wants to work on> in /etc/fstab".
My "rescue disks" are very fast booting and very easy to find, yet another advantage of multiboot HDs. Install first "upgrade" of the first installation as a new installation on a separate / partition, and you don't have to restore from backup, try installing again, or reinstall the old, after finding the "upgrade" fell short of expectations, yet once the new turns out to be an acceptable replacement, the old sits in reserve not hurting anything, and taking up relatively little space on modern giant HDs, waiting for an opportunity to rescue the new. I have one system ready to boot at any time openSUSE 10.0, every openSUSE since released, plus Tumbleweed. Not to say it's right that what used to be possible no longer is, but that seems to be the legacy of started from scratch replacements for things that worked (KDE4 then KDF5 replacing KDE3; systemd replacing sysvinit; dracut replacing mkinitrd; wayland to be replacing xorg; etc.) that FOSS evolution has become. The wisdom of experience is routinely discarded, providing vast opportunities for new bugs and more downtime on account of the "upgrading" necessary to remain reasonably secure in an Internet-accessible environment. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. Regards, -- Marco Calistri opensuse 13.2 (Harlequin) 64 bit - Kernel 3.16.7-7-desktop Gnome 3.14.1 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 04/05/2015 03:28 AM, Basil Chupin wrote:
I got the response (error msg) that-
mount: / is busy
Subtext and slightly off topic. This is one reason I have a very small ROOT file system and lots and lots of mounted file systems. In maintenance mode I can unmount then all and easily fsck them. Yes the ROOT-fs is another matter, ... And lets not even THINK about what life is like with a BtrFS that encompasses the whole of the file system hierarchy in one FS ... And where is the fsck for THAT and how will this problem that basic describes be dealt with then? Sometimes I wonder if its worth Resurrecting my long discarded C programming skills (but when I think about that I have flashes of a Queen Xenomorph!) -- I don't know the key to success, but the key to failure is trying to please everybody -- Bill Cosby -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/04/15 23:00, Anton Aylward wrote:
On 04/05/2015 03:28 AM, Basil Chupin wrote:
I got the response (error msg) that-
mount: / is busy Subtext and slightly off topic.
This is one reason I have a very small ROOT file system and lots and lots of mounted file systems. In maintenance mode I can unmount then all and easily fsck them. Yes the ROOT-fs is another matter, ...
Considering that '/' is where all the "really good" stuff is, checking '/' for errors is rather "front-page stuff" wouldn't you agree? :-) It was _very_ simple in the past (as I describe in my initial post) therefore it should just as simple to do so now. Agree?
And lets not even THINK about what life is like with a BtrFS that encompasses the whole of the file system hierarchy in one FS ... And where is the fsck for THAT and how will this problem that basic describes be dealt with then?
As I mention in my reply to jdd, GParted can check btrfs for errors with one exception which has to do with UUID. I don't know what that means but you could check it out (as I wouldn't touch btrfs with a forty-foot pole while its still in its alpha stage).
Sometimes I wonder if its worth Resurrecting my long discarded C programming skills (but when I think about that I have flashes of a Queen Xenomorph!)
Whatever gives you goose pimples........ 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
On 04/06/2015 03:47 AM, Basil Chupin wrote:
On 05/04/15 23:00, Anton Aylward wrote:
On 04/05/2015 03:28 AM, Basil Chupin wrote:
I got the response (error msg) that-
mount: / is busy Subtext and slightly off topic.
This is one reason I have a very small ROOT file system and lots and lots of mounted file systems. In maintenance mode I can unmount then all and easily fsck them. Yes the ROOT-fs is another matter, ...
Considering that '/' is where all the "really good" stuff is, checking '/' for errors is rather "front-page stuff" wouldn't you agree? :-)
NOT! The core stuff may be in /bin and /lib but the "fun" stuff is in /opt and /usr/local. Heck, many of the essentials are in /usr/bin and /usr lib. If you don't know how to make /usr mountable, then at the very least migrate off /usr/share to a seperate FS. The logic behind having one FS for the whole system, the plan behind BtrFS, spanning multiple spindles, scares me. I know there is a posture of "all the eggs in one basket and make it a very good basket and protect it" -- see evolutionary biology models for details -- but BtrFS is still unstable. I've subscribed to the btrfs development list and the patches are coming though fast and furious, and many of the bugs/fixes seem .... Gee, what did we learn in programming 101? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/04/15 18:16, Anton Aylward wrote:
On 04/06/2015 03:47 AM, Basil Chupin wrote:
On 05/04/15 23:00, Anton Aylward wrote:
On 04/05/2015 03:28 AM, Basil Chupin wrote:
I got the response (error msg) that-
mount: / is busy Subtext and slightly off topic.
This is one reason I have a very small ROOT file system and lots and lots of mounted file systems. In maintenance mode I can unmount then all and easily fsck them. Yes the ROOT-fs is another matter, ...
Considering that '/' is where all the "really good" stuff is, checking '/' for errors is rather "front-page stuff" wouldn't you agree? :-) NOT!
The core stuff may be in /bin and /lib but the "fun" stuff is in /opt and /usr/local. Heck, many of the essentials are in /usr/bin and /usr lib.
I know that you keep trying, but you often miss the point :-) (and I mean this in a nice way). When one installs openSUSE, the installation process gives you the option of creating '/' and '/home' directories (the swap partition is not really mentioned in the choice as I remember). This means that all the "good stuff" is sitting in '/' when oS is installed. Yes or No to the above last paragraph? And as a normal, standard, sane, user of openSUSE I do not go about bothering about all the /bin and the /lib and the /usr/local and the /usr/bin and the /usr/lib s*** you mention above. I simply want to use openSUSE - just like someone who is into Windows wants to use Windows without having to take a Microsoft Certified Training Course to fiddle the Window's guts. Got the picture? :-) Alright, there *are* a few things I can fiddle with in oS to suit myself but they DO NOT involve all the "/opt" etc and so on which you mention :-) . I install openSUSE on a partition which is '/' and with a swap partition. NO separate /home - just '/' and swap. That's it - except that I create on a second HDD a partition to where I then SYMLINK most of the directories in my /home partition.
If you don't know how to make /usr mountable, then at the very least migrate off /usr/share to a seperate FS.
The logic behind having one FS for the whole system, the plan behind BtrFS, spanning multiple spindles, scares me.
BTRFS terrifies me as well which is why I won't touch it for years until it proves to be as reliable as, say, Reiserfs, or ext4 (with whatever faults it may have).
I know there is a posture of "all the eggs in one basket and make it a very good basket and protect it" -- see evolutionary biology models for details -- but BtrFS is still unstable. I've subscribed to the btrfs development list and the patches are coming though fast and furious, and many of the bugs/fixes seem .... Gee, what did we learn in programming 101?
Dunno, tell me - what did you learn in "programming 101"? 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
On 04/08/2015 03:26 AM, Basil Chupin wrote:
When one installs openSUSE, the installation process gives you the option of creating '/' and '/home' directories (the swap partition is not really mentioned in the choice as I remember).
This means that all the "good stuff" is sitting in '/' when oS is installed.
Yes or No to the above last paragraph?
I said NO and I meant NO. NO means NO. To coin a phrase :-) When one installs openSUSE the installation process gives you the option of creating .... *any number of partitions*
And as a normal, standard, sane, user of openSUSE I do not go about bothering about all the /bin and the /lib and the /usr/local and the /usr/bin and the /usr/lib s*** you mention above.
As a normal, standard, sane use of openSUSE ... who is a careful and diligent computer user who make sure he backs up his work, I partition my system for robustness, ease of backup and ease of restore. This involves partitioning along functional lines. Once upon a time UNIX didn't have /home. Its introduction was a goo innovation! Everything to do with my web server is on /srv. That is a functional division. OK, so if you don't have a a web server you won't care Local packages, Xmind, freemind, scrivener and the like end up in /opt I want to keep those, maybe move them when I get new h/w and don't want them zapped when / gets reformatted in a new installation. That justifies a functional division. OK, so if you never install custom stiff you won't care There are quite a number of reasons, many of them security (and not just hack-related but also dealing with containment) related that justify having a separate /tmp. You may have enough memory to make this a tmpfs :-) I exclude /tmp from my backups very simply by having it as a separate partition. Or you may not care. Even under /home I have mounted partitions. - My Documents - My Music - My Photographs It makes space management and backups easier to manage. Part of my backup strategy is to have (data) partitions that are under 5G so they can fit on a DVD. Regular readers will recall that I use LVM so more partitions - aka logical volumes - are easy for me, as are taking snapshots and making backups from the snapshots while 'live work' continues. This has all to do with planning and a strategic attitude towards disk management. Very little of *MY* good stuff lives on the ROOT file system. So when I said NO I meant NO. Of course you may about care about such matters as backups and restore, about making disk management easier. You may not care. I came to all this though unpleasant occurrences, inadequate backups, failed media and more. Call it paranoid: I now expect things to go wrong so I adopt a strategy to try and minimise the impact and make it more manageable. When one installs openSUSE the installation process gives you the option of creating .... *any number of partitions* I take that option. I take that option based on experience and prudence. Because I CARE ABOUT MY DATA. As far as I am concerned, the "Good Stuff" is the stuff I have created or purchased. So NO, I don't think the good stuff should be on the root partition when installing. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Basil Chupin wrote:
Or put another way, how does one go about manually checking the file system for errors by running "e2fsck"?
One boots a rescue system of one's choosing and then proceeds to run e2fsck etc. :-) -- Per Jessen, Zürich (2.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/04/15 17:48, Per Jessen wrote:
Basil Chupin wrote:
Or put another way, how does one go about manually checking the file system for errors by running "e2fsck"? One boots a rescue system of one's choosing and then proceeds to run e2fsck etc. :-)
See my comments in this thread about using the GParted (in the Rescue Discs). 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
Basil Chupin wrote:
On 06/04/15 17:48, Per Jessen wrote:
Basil Chupin wrote:
Or put another way, how does one go about manually checking the file system for errors by running "e2fsck"? One boots a rescue system of one's choosing and then proceeds to run e2fsck etc. :-)
See my comments in this thread about using the GParted (in the Rescue Discs).
Hi Basil, If it's important, could you summarize for me? I'm too lazy to read the rest of the thread. /Per -- Per Jessen, Zürich (3.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/04/15 17:31, Per Jessen wrote:
Basil Chupin wrote:
On 06/04/15 17:48, Per Jessen wrote:
Basil Chupin wrote:
Or put another way, how does one go about manually checking the file system for errors by running "e2fsck"? One boots a rescue system of one's choosing and then proceeds to run e2fsck etc. :-) See my comments in this thread about using the GParted (in the Rescue Discs). Hi Basil,
If it's important,
Define "important" :-) . But I guess it cannot be important to you otherwise you would read the few posts I made in this thread :-) re this feature of GParted.
could you summarize for me? I'm too lazy to read the rest of the thread.
At this point in time I'll see if I may stay awake long enough to do such a summary but I will do it just for you :-) . 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-07 08:56, Basil Chupin wrote:
On 06/04/15 17:48, Per Jessen wrote:
Basil Chupin wrote:
Or put another way, how does one go about manually checking the file system for errors by running "e2fsck"? One boots a rescue system of one's choosing and then proceeds to run e2fsck etc. :-)
See my comments in this thread about using the GParted (in the Rescue Discs).
And why do you want to use gparted, and not e2fsck? - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUlRnMACgkQja8UbcUWM1zOSAD+IptJH05T6jDEPT3mYXi/pvlx gF/Ug0iB27vwcoGEv8cA/R16QqCRKF2WXfSWjLhF9fHOQ4eADCwnDk/obuqH2UoO =MEBq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sun, 05 Apr 2015, Basil Chupin wrote: [..]
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?
systemd, what else?
Or put another way, how does one go about manually checking the file system for errors by running "e2fsck"?
# touch /forcefsck # reboot HTH, -dnh -- MSDOS didn't get as bad as it is overnight -- it took over ten years of careful development. -- dmeggins@aix1.uottawa.ca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-05 09:28, Basil Chupin wrote:
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 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.
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. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUifQ8ACgkQja8UbcUWM1xJ8wD/XoVIYgmZKKrjvSZbB4evMu5F q0WRNB2sjyRzlYMuGP0A/27cwZGmgd5sLRSfxb+BluihZc3hb0BEOi7tvOfsYwpt =5vCc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Apr 6, 2015 at 3:33 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-04-05 09:28, Basil Chupin wrote:
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 the fsck of the target root from there.
dracut usually performs fsck anyway; if in doubt, today one can simply use rd.break=pre-mount to stop in dracut shell before real root is mounted, then do fsck (fsck for root should be present in initrd) and Ctrl-D to continue. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-06 14:45, Andrei Borzenkov wrote:
dracut usually performs fsck anyway; if in doubt, today one can simply use rd.break=pre-mount to stop in dracut shell before real root is mounted, then do fsck (fsck for root should be present in initrd) and Ctrl-D to continue.
Oh... interesting. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUigUcACgkQja8UbcUWM1x9RAD/X3vjRQN+iiMgSfImUbd+iTbG 76fkvxKjcG9EW0hfqOcA/jVqOuKtdu3ga4XG8lBVMspidjzNZS6VMcvbqtuNsjPs =1v41 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 06/04/2015 14:45, Andrei Borzenkov a écrit :
dracut usually performs fsck anyway; if in doubt, today one can simply use rd.break=pre-mount to stop in dracut shell before real root is mounted, then do fsck (fsck for root should be present in initrd) and Ctrl-D to continue.
interesting. going to advanced menu, "e" to edit and add rd.break=pre-mount on the kernel line, gives you the emergency shell where one can use fsck. that said, no fdisk _l, one have to remember the partition number jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Apr 6, 2015 at 4:28 PM, jdd <jdd@dodin.org> wrote:
Le 06/04/2015 14:45, Andrei Borzenkov a écrit :
dracut usually performs fsck anyway; if in doubt, today one can simply use rd.break=pre-mount to stop in dracut shell before real root is mounted, then do fsck (fsck for root should be present in initrd) and Ctrl-D to continue.
interesting.
going to advanced menu, "e" to edit and add rd.break=pre-mount on the kernel line, gives you the emergency shell where one can use fsck.
that said, no fdisk _l, one have to remember the partition number
Or look in /etc/fstab. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/04/15 22:45, Andrei Borzenkov wrote:
On Mon, Apr 6, 2015 at 3:33 PM, Carlos E. R. <robin.listas@telefonica.net> 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.
dracut usually performs fsck anyway; if in doubt, today one can simply use rd.break=pre-mount to stop in dracut shell before real root is mounted, then do fsck (fsck for root should be present in initrd) and Ctrl-D to continue.
Many thanks, Andrei, for the above. Worked a treat on my "test bed", Tumbleweed! :-) 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
On 04/06/2015 03:33 PM, Carlos E. R. wrote:
> Recently, it can be the XFCE CD
> rescue image which you get from our download page and place on a USB
> stick
- what please is Download link address ?
thanks
ellan
--
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-06 14:58, ellanios82 wrote: > On 04/06/2015 03:33 PM, Carlos E. R. wrote: >> Recently, it can be the XFCE CD rescue image which you get from >> our download page and place on a USB stick > - what please is Download link address ? Same as for all openSUSE images. https://www.opensuse.org/ --> GET IT --> http://software.opensuse.org/132/en See box: +++·—·—·—·—·— Some alternative media (eg. live and rescue systems) are also available, although they are less tested and recommended for only limited use. Click here to display these alternative versions. ·—·—·—·—·—++- Well, click there. You see then several other boxes. One reads: +++·—·—·—·—·— Rescue Rescue system that you can run from CD or from USB stick. Can not be used for installation or upgrade. ·—·—·—·—·—++- Click there... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUiiLYACgkQja8UbcUWM1x5MAD/TsvtEVx3U3ImDliNpIQh74dr iCH1/Y4IBx0LgRh52vAA/0syA/SIr0rdtWBqyKBBFRQ4f/QS8N+4Vf+fuVFDeIXX =O7MH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/06/2015 04:23 PM, Carlos E. R. wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 2015-04-06 14:58, ellanios82 wrote: >> On 04/06/2015 03:33 PM, Carlos E. R. wrote: >>> Recently, it can be the XFCE CD rescue image which you get from >>> our download page and place on a USB stick >> - what please is Download link address ? > > Same as for all openSUSE images. > > > https://www.opensuse.org/ --> GET IT --> > > http://software.opensuse.org/132/en > > See box: > > +++·—·—·—·—·— > Some alternative media (eg. live and rescue systems) are also > available, although they are less tested and recommended for only > limited use. Click here to display these alternative versions. > ·—·—·—·—·—++- > > Well, click there. You see then several other boxes. One reads: > > > +++·—·—·—·—·— > Rescue > Rescue system that you can run from CD or from USB stick. > Can not be used for installation or upgrade. > ·—·—·—·—·—++- > > Click there... > > > - -- > Cheers / Saludos, > ..................... XFCE USB stick :: - Thank you kindly :: prolly i have spots before eyes :: or , moon is in wrong aspect or something :: i have tried to press the right buttons you have indicated :: guess it is just not 'my day' :: thanks ................ regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-04-07 08:53, Basil Chupin wrote:
On 06/04/15 22:33, Carlos E. R. wrote:
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.
You must be confused. The openSUSE rescue disks does _nothing_ automatically. It is up to you to start gparted, or a terminal and run fsck with whatever options you want. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUlRh4ACgkQja8UbcUWM1yLtgD8CNsVRBLpZA+MYWw1gkTet33r CPNKwxNxWMBTy5ckneMA/iObOscp9BcHah/F/f4gD4mVOBK2n8czjCDJEj0CnVQv =aO6B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Andrei Borzenkov -
Anton Aylward -
Basil Chupin -
Carlos E. R. -
David Haller -
ellanios82 -
Felix Miata -
jdd -
Marco Calistri -
Per Jessen