Description of problem:
I'm trying to install F19 Beta on a Samsung 830 SSD, but during install I am only able to select my HDD.
Before I get to the selection menu and after the language selection, I get an error about something in Timbuktu with on of the dialog options "Get out of here"
I cannot remember the exact wording but it looks more like a bit out of the hitchhiker guide to the galaxy then an actual useful error message :-&
Version-Release number of selected component (if applicable):
F19 Beta 1
Tried it a couple of times, also with a different SSD of the same type. I also did a dd if=/dev/zero, to no avail.
Please follow the procedure outlined below to collect some information to help us diagnose your problem:
1. reproduce the problem (get to the point where your ssd is not shown during disk selection)
2. switch to the shell on tty2 by pressing ctrl+alt+f2
3. run the following command to generate a file containing the necessary data:
kill -USR2 `cat /var/run/anaconda.pid`
(you can find this command in the shell's history by pressing the up arrow
several times once in the shell)
4. transfer all files matching /tmp/anaconda-tb-* somewhere from whence you
can add them to this bug reports as attachments
NOTE: there will most likely only be one file to attach
Created attachment 762461 [details]
Requeste anaconda log
Your SSD is, for some reason, configured to be in a firmware-RAID array. The Fedora tools for working with such arrays seem to be having trouble with yours:
11:57:51,989 INFO kernel:[ 27.563464] dmraid: segfault at 0 ip 00007f1cc9b4d1ef sp 00007fff1508cd58 error 4 in libc-2.17.so[7f1cc9abd000+1b5000]
Perhaps you could run the following commands and attach the full output to this bug:
dmraid -v -r
dmraid -v -s
Thanks in advance.
Thanks, that was the problem. One of my co-workers used them for benchmarking a RAID array and put them back on the shelf...
I created a new partition table with gparted.
Do you still need the output? I have some more of these SSD's laying around.
I don't need the output since you have verified my suspicion is correct. This is a common problem, and one that there is no simple solution to other than teaching people to correctly wipe raid metadata from their disks when moving them from one system to another. Thanks for reporting back.