OpenSUSE repair from 12.1 DVD

How do repair openSUSE from 12.1 DVD.
Checked media.
Loaded** Xfce** OS…on raid (mirror) with two harddisks.
Worked…

Add/removed Software
Updated everything…worked.

changed gmixer… by removing some settings…
On re-booted fails to load.

Trying to repair/rescue failed system.

There is no dialog box for rescue/repair on DVD.

That feature has gone

Fails to load —How? explain

t, for replying…newbie

when I boot up…the sys just runs with splash screen, So I hit esc…see that there is some “loop” process going on. Usaully 15-35 sec bootup …now hangs…

I’m not sure whether it will help. But here’s what I did when I needed to “rescue” the system:
Rescuing Susie

Its the darn DMRAID. it read and writes too often. Even when there is no disk activity.
Re-installed many times due to this.

AFTER re-install system boots then crashes again. Thinking I should go back to fedora.

On 01/02/2012 08:16 PM, just4me2 wrote:
> changed gmixer… by removing some settings…
> On re-booted fails to load.

no dvd repair needed…just put back what you removed.

or, restore from the backup you made prior to your changes…


DD
openSUSE®, the “German Engineered Automobiles” of operating systems!

there was no backup, yet. system ran for only two hours.

This is what I did:

On dell t5500 workstation with two clean disks running raid (mirror).
Inte RAID status Normal.

Installed Xfce OpenSuse. MDRaid turned on.
Installed fine ran.

Changed settings fonts, etc

With Add/remove dialog gui.
Removed LibreOffice, others
Added Wine (333MB), Mysql, SQLyog, UnixODBC, scipy, others
Added two dir to /
Added files two dir in / (230MB, 330MB)
Worked with files for 30 minutes…

Turned off and on…
Intel Raid says needs verify…

System wont start…
In some kind of lookup loop.
FAILsafe wont load same lookup loop.

Inserted Install disk.
App says that there is no installed system,
cant read disks.

On 01/03/2012 03:36 PM, just4me2 wrote:
> Turned off and on…
> Intel Raid says needs verify…

sorry, i know less about raid than i know about windows…(but believe
both cause more problems than they solve)

i guess you need a linux RAID guru…


DD
openSUSE®, the “German Engineered Automobiles” of operating systems!

I am really annoyed with this stupid forum software. That’s the third time this afternoon my session has dropped in the middle of trying to post. And it is configured to be for entertainment rather than technical forums. And it does not produce W3C compliant pages and is anti-accessibility good practice with its SEO obfuscation plug-n. GRRRR!

Fake RAID is an abomination. Much better to turn it off and use soft RAID. ArchLinux have an OK fake RAID primer:
https://wiki.archlinux.org/index.php/Fakeraid

Also be aware that 12.1 and *systemd * does not work well with either soft or fake RAID.

On 01/03/2012 06:06 PM, eng-int wrote:
> I am really annoyed with this stupid forum software.

avoid it completely and enter via nntp,
http://forums.opensuse.org/faq.php?faq=novfor#faq_nntp


DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

DenverD wrote:
> avoid it completely and enter via nntp,

Well, I have tried KNode, and it avoids the aborted sessions, and it is
generally much less stressful to use with TTS etc.
but:

If threading is switched on it seems unable to sort by most recent post,
only by time of the first post in the thread.

It does not solve the link obfuscation, although some of that is done
deliberately by the posters, along with references to file-sharing sites.

On 01/03/2012 08:04 PM, eng-int wrote:
> If threading is switched on it seems unable to sort by most recent post,
> only by time of the first post in the thread.

i’ve used knode and several other nntp clients over the years…for the
last several i’ve used mozilla thunderbird for all of email (including
gmail and ISP), mail lists, usenet and the openSUSE forums (and novell
forums before)…

it sorts by most anything you can think of and if (for example) and old
OLD thread is resurrected by someone posting to it, it will pop-up at
the top (or bottom, as you wish) of the list of threads…

it is kinda nice to have all of that stuff presented in the same format…

> It does not solve the link obfuscation, although some of that is done
> deliberately by the posters, along with references to file-sharing sites.

link obfuscation is gonna be here forever…i never understood the
purpose of being frightened by them…

http://5z8.info/-----TAKE.TWITTER.LOGIN-----_n0x4dj_smut


DD

was suse 11.4 any better? Or all SUSE bad with RAIDS.

just4me2 wrote:
> was suse 11.4 any better? Or all SUSE bad with RAIDS.

All [open]suse are good with RAIDs. And contrary to what DD says, RAID
is extremely useful.

> On dell t5500 workstation with two clean disks running raid (mirror).
> Inte RAID status Normal.
>
> Installed Xfce OpenSuse. MDRaid turned on.
> Installed fine ran.

Are you aware that MDRaid (i.e. using mdadm) is soft RAID and is
different to either fakeRaid or hardware RAID? So it won’t be compatible
with Intel RAID if the Intel RAID is turned on.

> System wont start…
> In some kind of lookup loop.
> FAILsafe wont load same lookup loop.

If you want help diagnosing the problem, you will need to post the exact
error messages you are seeing, not “some kind of lookup loop”! You can
use a camera to take a picture if you can’t capture the text.

Ignoring the description of the RAID installation – because it does not make sense.
The described observed behaviour seems to match the experiences reported in bugzilla (Bug #731230) for 12.1, systemd, and soft RAID. There, there is a description of escaping out of the hiatus and proceeding to boot, also that the behaviour is erratic for some and consistent for others. Once booted, the system can be configured to use either sysvinit or Frederic Crozat’s updated systemd.

I had already partially circumvented this on my test machine (oS-12.1 64bit, KDE-4.7.95, VBox-3.1.3) by using a 2GB non-raid sda1 for root, (rsynced periodically to sdb1) and separate /usr /home and /var soft RAID0 partitions. The root filesystem ,including /boot, currently occupies 309MB.