I have two RAID devices on my computer, a RAID0 and RAID1. When installing Fedora 18 Beta using Manual Partitioning I can see two software RAID entries under Unknow at the very bottom of the left columns. I cannot see the actual partitions: 1 under my RAID 0 and two under my RAID1 I cannot set mount points for them.
You have partitioned md arrays? Please attach the following files from the shell on tty2 after entering the custom storage setup screen: /tmp/anaconda.log /tmp/storage.log /tmp/program.log /tmp/syslog Please attach them individually and use text/plain for the type if possible. No archives, please. Thanks.
I'm trying to install F18 over an existing Ubuntu system. / and /home are ext4 formated RAID1 partitions, /dev/md2 is mounted on /, /dev/md3 is mounted on /home I cannot set mount points for those devices unless I mark them for reformatting. I'll attach the requested logs (when I found out how this works here).
Created attachment 679727 [details] requested log file: /tmp/storage.log
Created attachment 679728 [details] Requested log file: anaconda.log
Created attachment 679729 [details] Requested log file: /tmp/program.log
Forgot to save /tmp/syslog. Will be provided later.
(In reply to comment #2) > I'm trying to install F18 over an existing Ubuntu system. / and /home are > ext4 formated RAID1 partitions, /dev/md2 is mounted on /, /dev/md3 is > mounted on /home I cannot set mount points for those devices unless I mark > them for reformatting. I'll attach the requested logs (when I found out how > this works here). What happened to your first run? It looks like something interrupted it and caused things to enter an inconsistent state. Consider rebooting the live media and trying again, this time taking care not to kill the installer while it is running.
On the first run the very same happened. That's why I interrupted anaconda. I couldn't even find a clean way to exit without being afraid of data loss. (Hint: It's not clear at all when changes the user makes to the disk layout will be applied - immediately, later on, onWhateverClicked(). This keeps the user in a permanent state of fear and uncertainty if there's data he actually wants to keep.) So when exactly do you actually want me to take the snapshots of all the logs?
(In reply to comment #7) > Consider rebooting the live media and trying again, this time taking care > not to kill the installer while it is running. OK, I've run it again. See the new logs. There is no /tmp/syslog btw. Once again for the record: Anaconda is really causing extreme fear and uncertainty when it comes to partitioning. You never know when you could possibly damage your disks and data. There's no "Abort" or "Cancel" button and no description whatsoever telling what "Done" actually means or does.
Created attachment 684982 [details] /tmp/anaconda.log
Created attachment 684983 [details] /tmp/program.log
Created attachment 684991 [details] /tmp/storage.log
Nothing is written to disk until you click the "Begin Installation" button on the main screen.
(In reply to comment #2) > I'm trying to install F18 over an existing Ubuntu system. / and /home are > ext4 formated RAID1 partitions, /dev/md2 is mounted on /, /dev/md3 is > mounted on /home I cannot set mount points for those devices unless I mark > them for reformatting. I'll attach the requested logs (when I found out how > this works here). You cannot use a preexisting filesystem for / -- you must create a new one. For /home you should be able to simply enter the mountpoint and click "Apply Changes".
(In reply to comment #14) > You cannot use a preexisting filesystem for / -- you must create a new one. Sure, it wouldn't make sense to use an installer otherwise.It's /home I care for. > For /home you should be able to simply enter the mountpoint and click "Apply > Changes". Exactly, I *should* be able. I filed this bug report because I am *not* able to do this. The field where I am supposed to enter the mount point is not editable unless I mark my existing /home partition for reformatting. I definitely don't want my /home partition to be reformatted.
There's a problem detecting the filesystem on /dev/md/3. As a workaround, please try deactivating all of your md devices before running liveinst. Let me know how that goes.
I chose to not use my existing /home but to install without a dedicated /home partition, first. Afterwards I added my md devices in /etc/fstab. This surely works but should not be neccessary.
Several issues with detection of md devices have been fixed for fedora 19 beta, which should be released within a couple of weeks. If you find that this issue remains in any version of Fedora 19 please reopen this bug and attach the new logs.