Bug 501664

Do you actually have a dmraid setup?  If so, we're not at all detecting it and therefore you have no devices available for use.  Hence the crash.

No I don't use anything special.

It's my computer from work, pretty new. I just install a normal Fedora without LVM or any other particularities (at least not that I am aware of :) ).

[root@pingouLab ~]# dmraid -r
/dev/sda: isw, "isw_bdibhbjccd", GROUP, ok, 312581806 sectors, data@ 0

hm :s

(In reply to comment #3)
> [root@pingouLab ~]# dmraid -r
> /dev/sda: isw, "isw_bdibhbjccd", GROUP, ok, 312581806 sectors, data@ 0
> 
> hm :s  

Ok, so you do have a dmraid set and we are not detecting it. Can you please start a regular dvd install again and then save /tmp/anaconda.log and /tmp/storage.log somewhere (use scp or a usb-stick) and attach them here?

You can switch to tty2 (CTRL + ALT + F2) to get a shell when you're at
the partitioning screen with no disks, and save the log files from that shell.

Thanks!

Created attachment 345285 [details]
Anaconda.log

Created attachment 345286 [details]
storage.log

Ah, your disk used to be part of a dmraid array (so part of a raidset which can
be activated on some motherboards from the BIOS), but no longer is (you only have 1 disk), yet it still contains the isw raid (intel software raid) metadata on the disk, so we think its part of a set, does not find the other disks and then do not recognize it.

I guess you were lucky for this to work in F-10, this really is not a setup which
we want to support.

Your best way forward is to remove the isw metadata from the disk, so that
it gets seen as a normal disk. This can be done with the dmraid utility.

*WARNING* I've never done this, I know the BIOS will nuke the partition table
on the disk when you do this from the ISW BIOS (OROM), I do not expect dmraid to do the same, but be warned, this may cause data loss! *WARNING*

Ok, so you've made backups, right ? Then try the following command:
dmraid -x isw_bdibhbjccd

To remove the metadata.

Thanks for your help.

The raid might be due to the installation procedure used by the ICT department.

My only concern (once backup are done and computer ready) is:
The system is dual boot with a windows (needed for some application at work), I expect they will not be touch.

Am I right ?

(In reply to comment #8)
> Thanks for your help.
> 
> The raid might be due to the installation procedure used by the ICT department.
> 
> My only concern (once backup are done and computer ready) is:
> The system is dual boot with a windows (needed for some application at work), I
> expect they will not be touch.
> 
> Am I right ?  

You may want to check device manager in windows to see it is not seeing
the disk as part of a degraded (but still functional) raid set, if it is seeing
it like that I don't know how it will respond to the metadata going away. I suspect its just seeing it as a regular disk, in which case everything is fine.

[root@pingouLab ~]# dmraid -r
/dev/sda: isw, "isw_bdibhbjccd", GROUP, ok, 312581806 sectors, data@ 0
[root@pingouLab ~]# dmraid -x isw_bdibhbjccd
ERROR: either the required RAID set not found or more options required
no raid sets and with names: "isw_bdibhbjccd"

:S

(In reply to comment #10)
> [root@pingouLab ~]# dmraid -r
> /dev/sda: isw, "isw_bdibhbjccd", GROUP, ok, 312581806 sectors, data@ 0
> [root@pingouLab ~]# dmraid -x isw_bdibhbjccd
> ERROR: either the required RAID set not found or more options required
> no raid sets and with names: "isw_bdibhbjccd"
> 

Try doing just:
dmraid -x

(In reply to comment #11)
> (In reply to comment #10)
> > [root@pingouLab ~]# dmraid -r
> > /dev/sda: isw, "isw_bdibhbjccd", GROUP, ok, 312581806 sectors, data@ 0
> > [root@pingouLab ~]# dmraid -x isw_bdibhbjccd
> > ERROR: either the required RAID set not found or more options required
> > no raid sets and with names: "isw_bdibhbjccd"
> > 
> 
> Try doing just:
> dmraid -x  

That one worked :)

But it seems that windows doesn't want to boot anymore... 

Thanks for your help