Mailinglist Archive: opensuse-bugs (15092 mails)
| < Previous | Next > |
[Bug 304657] Yast2 repair doesn' t check or repair system installed on MD Raid
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Fri, 14 Sep 2007 06:41:50 -0600 (MDT)
- Message-id: <20070914124150.8DF45CC789@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=304657#c14
--- Comment #14 from Richard Creighton <rccj@xxxxxxxxxxx> 2007-09-14 06:41:50 MST ---
(In reply to comment #13 from Jiří Suchomel)
> Created an attachment (id=164079)
--> (https://bugzilla.novell.com/attachment.cgi?id=164079) [details]
> patch for /usr/share/YaST2/modules/OSRFstab.ycp
>
> Richard, here is my first attempt: use this patch on
> /usr/share/YaST2/modules/OSRFstab.ycp and run 'ycpc -c
> /usr/share/YaST2/modules/OSRFstab.ycp'. Than run 'yast2 repair' and attach the
> log files from your "check session" (I do not advise you to do any repairs,
> but I hope you would not need them anyway)
>
Since we last 'spoke', I totally reinstalled 10.2 on that DMraid machine then
ran 10.3 upgrade from the B3 DVD so the environment has changed somewhat, but
the upgrade still failed but I was afraid to try the repair because last time
it almost ruined my 10.2 system on my IDE drive. This machine has 9 drives 4
of which are only accessable by a raid controller that as yet won't run with
kernels past 2.6.18.
I had thought that drive safe previously (and under 10.2 it had been) but with
the SATA/IDE rename thing in 10.3, everything has been subject to damage
including the MBR of that supposedly immune IDE drive.
Now, I am willing to risk it again now that I know I *can* recover but I am NOT
a programmer so I am not real sure how to apply the patch you have provided
Im I correct in assuming that there is a program available to me as root called
'ycpc' that I can run and use the patch as an argument? Then re-run yast2
repair an capture the log file for you. If that is correct, I will be happy
to oblige. Sorry for my stupidity...I am 64 years old and play with Linux but
am not a serious system programmer and I respect you that are.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
--- Comment #14 from Richard Creighton <rccj@xxxxxxxxxxx> 2007-09-14 06:41:50 MST ---
(In reply to comment #13 from Jiří Suchomel)
> Created an attachment (id=164079)
--> (https://bugzilla.novell.com/attachment.cgi?id=164079) [details]
> patch for /usr/share/YaST2/modules/OSRFstab.ycp
>
> Richard, here is my first attempt: use this patch on
> /usr/share/YaST2/modules/OSRFstab.ycp and run 'ycpc -c
> /usr/share/YaST2/modules/OSRFstab.ycp'. Than run 'yast2 repair' and attach the
> log files from your "check session" (I do not advise you to do any repairs,
> but I hope you would not need them anyway)
>
Since we last 'spoke', I totally reinstalled 10.2 on that DMraid machine then
ran 10.3 upgrade from the B3 DVD so the environment has changed somewhat, but
the upgrade still failed but I was afraid to try the repair because last time
it almost ruined my 10.2 system on my IDE drive. This machine has 9 drives 4
of which are only accessable by a raid controller that as yet won't run with
kernels past 2.6.18.
I had thought that drive safe previously (and under 10.2 it had been) but with
the SATA/IDE rename thing in 10.3, everything has been subject to damage
including the MBR of that supposedly immune IDE drive.
Now, I am willing to risk it again now that I know I *can* recover but I am NOT
a programmer so I am not real sure how to apply the patch you have provided
Im I correct in assuming that there is a program available to me as root called
'ycpc' that I can run and use the patch as an argument? Then re-run yast2
repair an capture the log file for you. If that is correct, I will be happy
to oblige. Sorry for my stupidity...I am 64 years old and play with Linux but
am not a serious system programmer and I respect you that are.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |