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 05:33:55 -0600 (MDT)
  • Message-id: <20070914113355.60C17245350@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=304657#c12


Jiří­ Suchomel <jsuchome@xxxxxxxxxx> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                                        |NEEDINFO
      Info Provider|                                                |fehr@xxxxxxxxxx




--- Comment #12 from Jiří­ Suchomel <jsuchome@xxxxxxxxxx>  2007-09-14 05:33:54 MST ---
> Initially I received an UPDATE ...

If you want to report any other problem than this one about repair, file a
separate bug.

> I took screenshots but it does not save them on disk, but apparently in ram so > notknowing that, they were lost.

See comment 9 about how to save the logfiles or screenshot from that session.

> This screenshot is VERY interesting because it
> shows that it knew about MD1 and MD3 but immediately it also shows that it
> intended to do file system checks on sda1 and sdb2 among others which are NOT
> part of the installed Beta 3 system if you will refer to the PartTbl10.3.png. 
> Those devices are part of the 10.2 file system shown also in Partn10.2.png.

How is that possible? PartTbl10.3.png shows that sdb1 is used by md1, sdb2 by
md0 etc. Thomas: Storage::GetTargetMap reports that /dev/sdb2 in devices list
of /dev/md0:

$["chunk_size":32, "detected_fs":`swap, "device":"/dev/md0",
"devices":["/dev/sdb2", "/dev/
sdc2"], "fstopt":"defaults", "fstype":"MD Raid", "label":"swap",
"mount":"swap",
 "mountby":`label, "name":"md0", "nr":0, "raid_type":"raid0", "size_k":2104320,
"type":`sw_raid, "used_fs":`swap]


-- 
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 >