Please help! Lost my LVM VG...
Hello All, I have a MythTV system running on Fedora 8. Initially the system only had one VolumeGroup: VolGroup00. Later on I added two more physical drives and created a completely new VolumeGroup (VolTerabytes00) to store all my data. This setup used to work fine for about a month. Today I switched my system off to make some physical cleaning (a lot of dust gets inside). After switching it ON, my Fedora doesn't boot, stopping at the "checking filesystems" phase with an error: "fsck.ext3: No such file or directory while trying to open /dev/VolTerabytes00/Data00" I'm prompted to enter a root password to get to system maintenance, or Ctrl+D to continue. In the system maintenance I can see there's /dev/VolGroup00 but there's no /dev/VolTerabytes00, so my newly-created VG seem to be missing! I tried running lvm and it says "Locking type 1 initialisation failed" no matter what command I enter... What can I do to get my volume group back??? Please help!! I have some valuable data on that volume, but more important to me is to find out what I did wrong... My system is Fedora 8, kernel 2.6.26.6-49.fc8 -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Please help! Lost my LVM VG...
Thursday, February 12, 2009, 9:42:38 PM, you wrote: > Running the command: > vgchange -ay VolTerabytes00 > Should activate the VG, assuming that all PVs are present (and any > needed modules have been loaded). >> I tried running lvm and it says "Locking type 1 initialisation failed" >> no matter what command I enter... > Check that the file system providing /var has been mounted and is > writable. > Assuming it's part of / you probably just need to run: > mount -n -oremount,rw / Ah, that worked! Thank you! What shall I do to automatically activate this VG during boot? -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Please help! Lost my LVM VG...
Hello Bryn, > You need to understand why it wasn't being activated automatically. > Boot logs (dmesg and/or /var/log/messages) would help here. Normally, > devices are scanned for LVM metadata when rc.sysinit runs. > There were some bugs in older releases (f8 is no longer > supported/maintained) where udev would not wait long enough for some > devices to appear, causing these scans to "miss" the VG. That sounds > plausible here since the vgchange -ay worked after the system had > booted but there's not really enough information to say for sure. > Try adding a "sleep 5" or "udevsettle --timeout=30" command to > rc.sysinit above each of the LVM activation commands. /var/log/messages doesn't contain any information about that problem. The error happened too early during boot - so that the data didn't get into the log files (disks were mounted in read-only mode). Anyway, the problem does not appear anymore. I just restarted the system several times (including complete power-down / power-up cycle), to be sure. I don't know what the reason was, but it seem to be fixed now! Thank you very-very-very much for your help!!! -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Please help! Lost my LVM VG...
Thursday, February 12, 2009, 11:29:07 PM, you wrote: > In any case, it would be interesting to have the OP reboot, and see > if the VG is active on reboot. I did. I even powered the system down. It starts now without that problem and everything gets mounted automatically during boot. So the problem went away when I activated the VG manually. P.S. What does the 'OP' mean? Something like 'Original Poster'? :) -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
No DVB after upgrade to 2.6.26.3 (solution)
Hello All, I recently upgraded my Fedora 8 system kernel from 2.6.25.9 to 2.6.26.3. After a reboot, both of my DVB TT S-1401 cards disappeared. Looking through /var/log/messages, I noticed that with kernel 2.6.25.x my DVB drivers were loading somehow like this: Sep 24 22:54:56 mythbackend kernel: saa7146: register extension 'budget dvb'. Sep 24 22:54:56 mythbackend kernel: ACPI: PCI Interrupt :0b:09.0[A] -> GSI 18 (level, low) -> IRQ 18 Sep 24 22:54:56 mythbackend kernel: saa7146: found saa7146 @ mem f8a0 (revision 1, irq 18) (0x13c2,0x1018). Sep 24 22:54:56 mythbackend kernel: saa7146 (0): dma buffer size 192512 Sep 24 22:54:56 mythbackend kernel: DVB: registering new adapter (TT-Budget-S-1401 PCI) Sep 24 22:54:56 mythbackend kernel: adapter has MAC addr = 00:d0:5c:61:4c:67 Sep 24 22:54:56 mythbackend kernel: DVB: registering frontend 0 (Philips TDA10086 DVB-S)... Sep 24 22:54:56 mythbackend kernel: ACPI: PCI Interrupt :00:1e.2[A] -> GSI 17 (level, low) -> IRQ 17 Sep 24 22:54:56 mythbackend kernel: ACPI: PCI Interrupt :0b:0b.0[A] -> GSI 19 (level, low) -> IRQ 19 Sep 24 22:54:56 mythbackend kernel: saa7146: found saa7146 @ mem f8c36400 (revision 1, irq 19) (0x13c2,0x1018). Sep 24 22:54:56 mythbackend kernel: saa7146 (1): dma buffer size 192512 Sep 24 22:54:56 mythbackend kernel: DVB: registering new adapter (TT-Budget-S-1401 PCI) Sep 24 22:54:56 mythbackend kernel: adapter has MAC addr = 00:d0:5c:0b:01:2d Sep 24 22:54:56 mythbackend kernel: DVB: registering frontend 1 (Philips TDA10086 DVB-S)... And with kernel 2.6.26.3 I could only see this: Sep 24 22:48:54 mythbackend kernel: ACPI: PCI Interrupt :0b:09.0[A] -> GSI 18 (level,low) -> IRQ 18 Sep 24 22:48:54 mythbackend kernel: Audiowerk 2 sound card (saa7146 chipset) detected and managed Sep 24 22:48:54 mythbackend kernel: ACPI: PCI Interrupt :0b:0b.0[A] -> GSI 19 (level, low) -> IRQ 19 Sep 24 22:48:54 mythbackend kernel: Audiowerk 2 sound card (saa7146 chipset) detected and managed Sep 24 22:48:54 mythbackend kernel: input: PC Speaker as /class/input/input5 Sep 24 22:48:54 mythbackend kernel: saa7146: register extension 'budget dvb'. And that's it. No more mention of dvb, saa7146 or TDA10086. I wonder what "Audiowerk 2 sound card" has to do with my DVB card... I didn't have these messages in previous kernel. So I checked with 'lspci -v' and noticed that the newer kernel loads some "snd-aw2" module, which interferes with the DVB drivers. Here's what 'lspci -v' showed about my DVB-S cards in kernel 2.6.25.9: 0b:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH DVB S-1401 Flags: bus master, medium devsel, latency 123, IRQ 18 Memory at f0221000 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget dvb Kernel modules: budget 0b:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH DVB S-1401 Flags: bus master, medium devsel, latency 123, IRQ 19 Memory at f0221400 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget dvb Kernel modules: budget And this is what 'lspci -v' shows about my DVB-S cards in kernel 2.6.26.3: 0b:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH DVB S-1401 Flags: bus master, medium devsel, latency 123, IRQ 18 Memory at f0221000 (32-bit, non-prefetchable) [size=512] Kernel driver in use: Emagic Audiowerk 2 Kernel modules: budget, snd-aw2 0b:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH DVB S-1401 Flags: bus master, medium devsel, latency 123, IRQ 19 Memory at f0221400 (32-bit, non-prefetchable) [size=512] Kernel driver in use: Emagic Audiowerk 2 Kernel modules: budget, snd-aw2 So the problem was easily solved by adding the line: blacklist snd-aw2 to /etc/modprobe.d/blacklist After a reboot, my DVB was back and running just fine (although I didn't test it much yet). I don't know if there's a problem somewhere, or it's a normal behavior. But I hope this will help to the ones who faced a similar issue. -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Upgrading from FC8 to F12 - please help
Hello All, I tried to upgrade my old machine running Fedora Core 8 to the shiny new Fedora 12 using 'preupgrade'. I know this isn't a recommended method, but I thought I would still try - as it went just fine on a test machine with a similar configuration. I have 4 disks on my main machine: 2x200Gb are mirrored (RAID1) using a cheap Promise controller card (they were still visible as separate disks in FC8: /dev/sda and /dev/sdb), and other 2x1Tb drives are connected directly to the motherboard (/dev/sdc and /dev/sdd). Everywhere LVM is used (well, it was almost a default install of Fedora 8). My system was on /dev/sda (or /dev/sdb, which is basically the same). Two terabyte drives were used as data-disks only. Within my old system, 'preupgrade' ran without visible errors. Then I restarted the system, adding 'upgradeany' parameter in grub (otherwise it won't find a target drive - same was on the test machine as well). My boot options in grub look like this: kernel /upgrade/vmlinuz preupgrade repo=hd::/var/cache/yum/preupgrade stage2=hd:UUID=:/upgrade/install.img ks=hd:UUID=:/upgrade/ks.cfg upgradeany It booted to the upgrade image and notified me that it can't initialize /dev/sda and /dev/sdb, which are (according to the error message) 1Tb each! So it says that it couldn't initialize my data drives - Ok, I thought that I could deal with that later. So I ignored the message and then got next error: "Unable to read package metadata... Cannon retrieve repository metadata (repmod.xml) for repository: anaconda-InstallationRepo-200911081854.i386. Please verify its path and try again." I searched for the file and it's actually at: /mnt/sysimage/var/cache/yum/ But that's probably not where installer expects it to be... Here's output of df -k (copied it by hand, sorry for a bad spacing): FilesystemUsed Available Mounted on /dev 204 508876 /dev none 119076 390004 /tmp /dev/loop0118912 0 /mnt/runtime /dev/mapper/VolGroup00-LogVol00 380885623013188 /mnt/sysimage /dev/mapper/pdc_eceihagjhp1 164366 20037 /mnt/sysimage/boot /dev 204 508876 /mnt/sysimage/dev /dev/tmpfs 0 509080 /mnt/sysimage/dev/shm /dev/mapper/VolGroup00-LogVol02 4756984 145787384 /mnt/sysimage/storage Looks like my filesystem is somehow mounted, although I'm not sure if I should also have 'VolGroup00-LogVol01' somewhere as well... As my installation couldn't continue, I decided to 'exit installer' and reboot to my previous system. But my old system is now not available as well. It starts to boot, shows something regarding LVM (like it found a drive) and then shows a lot of lines: /bin/sh invalid option --n and stops with a login prompt. I can't login either - after I enter a username it waits for some seconds and then brings a new login prompt again... Well, I know I did something wrong, and I don't know what it is. But I would really like to bring my system back - either in Fedora 12 or Fedora 8. Is there a way to do it, without reinstalling the whole system from scratch (there are some valuable data, especially on the 1Tb drives)...? I apologise for such a messy description. If there's anything I can provide or clarify - let me know how I could do it. I would really appreciate any hints on how to get my system back... -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrading from FC8 to F12 - please help
> Hello All, > I tried to upgrade my old machine running Fedora Core 8 to the shiny > new Fedora 12 using 'preupgrade'. I know this isn't a recommended > method, but I thought I would still try - as it went just fine on a > test machine with a similar configuration. > I have 4 disks on my main machine: 2x200Gb are mirrored (RAID1) using > a cheap Promise controller card (they were still visible as separate > disks in FC8: /dev/sda and /dev/sdb), and other 2x1Tb drives are > connected directly to the motherboard (/dev/sdc and /dev/sdd). > Everywhere LVM is used (well, it was almost a default install of Fedora 8). > My system was on /dev/sda (or /dev/sdb, which is basically the same). > Two terabyte drives were used as data-disks only. > Within my old system, 'preupgrade' ran without visible errors. Then I > restarted the system, adding 'upgradeany' parameter in grub (otherwise > it won't find a target drive - same was on the test machine as well). > My boot options in grub look like this: > kernel /upgrade/vmlinuz preupgrade > repo=hd::/var/cache/yum/preupgrade > stage2=hd:UUID=:/upgrade/install.img > ks=hd:UUID=:/upgrade/ks.cfg upgradeany > It booted to the upgrade image and notified me that it can't > initialize /dev/sda and /dev/sdb, which are (according to the > error message) 1Tb each! So it says that it couldn't initialize my > data drives - Ok, I thought that I could deal with that later. > So I ignored the message and then got next error: > "Unable to read package metadata... > > Cannon retrieve repository metadata (repmod.xml) for repository: > anaconda-InstallationRepo-200911081854.i386. Please verify its path > and try again." > I searched for the file and it's actually at: > /mnt/sysimage/var/cache/yum/ > But that's probably not where installer expects it to be... > Here's output of df -k (copied it by hand, sorry for a bad > spacing): > FilesystemUsed Available Mounted on > /dev 204 508876 /dev > none 119076 390004 /tmp > /dev/loop0118912 0 /mnt/runtime > /dev/mapper/VolGroup00-LogVol00 > 380885623013188 /mnt/sysimage > /dev/mapper/pdc_eceihagjhp1 > 164366 20037 /mnt/sysimage/boot > /dev 204 508876 /mnt/sysimage/dev > /dev/tmpfs 0 509080 /mnt/sysimage/dev/shm > /dev/mapper/VolGroup00-LogVol02 > 4756984 145787384 /mnt/sysimage/storage > Looks like my filesystem is somehow mounted, although I'm not sure if > I should also have 'VolGroup00-LogVol01' somewhere as well... > As my installation couldn't continue, I decided to 'exit installer' > and reboot to my previous system. But my old system is now not > available as well. It starts to boot, shows something regarding LVM > (like it found a drive) and then shows a lot of lines: > /bin/sh invalid option --n > and stops with a login prompt. I can't login either - after I enter a > username it waits for some seconds and then brings a new login > prompt again... > Well, I know I did something wrong, and I don't know what it is. But I > would really like to bring my system back - either in Fedora 12 or > Fedora 8. Is there a way to do it, without reinstalling the whole > system from scratch (there are some valuable data, especially on the > 1Tb drives)...? > I apologise for such a messy description. If there's anything I can > provide or clarify - let me know how I could do it. > I would really appreciate any hints on how to get my system back... Update: now while trying to boot to an old FC8, I get an error: /sbin/init: error while loading shared libraries: /lib/libsepol.so.1: invalid ELF header Kernel panic - not syncing: Attempted to kill init! Doesn't look good... :-( I would prefer to continue with an upgrade to F12 if possible, but I don't know how to do it and I'm not sure it is possible at all... -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrading from FC8 to F12 - please help
Wednesday, November 25, 2009, 11:24:28 AM, you wrote: > Andrew Junev wrote: >>> I apologise for such a messy description. If there's anything I can >>> provide or clarify - let me know how I could do it. >> >>> I would really appreciate any hints on how to get my system back... >> >> >> >> Update: now while trying to boot to an old FC8, I get an error: >> >> >> /sbin/init: error while loading shared libraries: /lib/libsepol.so.1: >> invalid ELF header >> Kernel panic - not syncing: Attempted to kill init! >> >> >> Doesn't look good... :-( >> >> I would prefer to continue with an upgrade to F12 if possible, but I >> don't know how to do it and I'm not sure it is possible at all... > I would suggest you to separate your recovery in steps. > First thing: disconnect your two 1TB drives where you have your data. > Second: try to fix the system when using only the 2 200GB disks. > Losing the system will be bad, losing the data would be worse. Ok, I disconnected data drives and also disconnected one of the mirrored drives (I know, I know - I should have done it before I tried the whole upgrade thing)... With only one drive connected (degraded RAID) I booted from a Live CD and tried to run fsck. It gave me a lot of errors about incorrect inodes and something like that. I then tried to correct the errors, but it didn't change the situation - I still couldn't boot from the hard disk to either FC8 or F12. Well, I still have another drive from this mirror disconnected, so I can (hopefully) get my system back to where it was before I ran fsck. Next step, I tried to reinstall F12 to my degraded array from the very beginning. I booted F12 istallation DVD, but it complained it can't find any drive to install the system to. I can see in the log files it detects my disk as /dev/sda, but then it says: wrong # of devices in RAID set "pdc_eceihagjh" [1/2] on /dev/sda So the installer probably rejects an idea to install Fedora on a degraded array - am I right? Is there a way to force it? I'd like to keep an old system on the spare drive for the time being. It is actually accessible when booting from a Live CD and I think I may need some configuration files from there to set up new system correctly. -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrading from FC8 to F12 - please help
Wednesday, November 25, 2009, 9:30:03 PM, you wrote: > On Wed, 25 Nov 2009 20:44:04 +0300 > Andrew Junev wrote: >> I can see in the log files it detects my disk as /dev/sda, but then it >> says: >> >> wrong # of devices in RAID set "pdc_eceihagjh" [1/2] on /dev/sda >> >> So the installer probably rejects an idea to install Fedora on a >> degraded array - am I right? Is there a way to force it? >> >> I'd like to keep an old system on the spare drive for the time being. >> It is actually accessible when booting from a Live CD and I think I >> may need some configuration files from there to set up new system >> correctly. >> > I am not an expert in this, but my question would be, "Are you > comfortable with using gparted or fdisk to change the drive so it is > seen as empty?" Alternatively you could use mke2fs to create an empty > ext? filesystem on it. That should take care of the anaconda issue. > By the way, it sounds like you are doing just fine in resolving this > issue. Well, unfortunately I don't have much of experience in Linux. But I'm trying to learn. :) I probably could repartition a drive with fdisk - shouldn't be a big deal. But I don't see the point. I do not use a software RAID (dmraid). RAID1 is setup on my SATA controller card (Promise FastTrak). While installing F12 onto a degraded RAID, anaconda does not show /dev/sda at all - otherwise repartitioning should have been possible right from the installer. Am I wrong? I searched on the Net and found some old discussions on installing Fedora onto a degraded RAID1. In short, it was not possible. There may be a workaround in case a software RAID is used, but I found nothing regarding a RAID setup on a controller card. There was an old bug report on this topic: https://bugzilla.redhat.com/show_bug.cgi?id=105598 It was closed with wontfix message. Is it still the same in Fedora 12? P.S. Personally I don't understand it. If I have a mirror and want to do something risky (an upgrade) - I need to take one disk out while the system is still fine, and then do the risky part. So that if it doesn't work as expected - a fallback is always possible... Maybe there's a different idea behind forbidding to install/upgrade a system on a degraded array? -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrading from FC8 to F12 - please help
Hello Craig, Wednesday, November 25, 2009, 10:35:04 PM, you wrote: > As I understand it, a Promise FastTrak RAID is what is known as 'fake > raid' and not supported by out of the box installation unless you > provide a 'driver module' at boot time. I suspect that this is something > you did to get F8 installed originally. Yes, it's probably a 'fake raid'. But I didn't need any additional drivers to install Fedora 8 several years ago - I remember that for sure. > The real Linux recommendation is to disable the 'fake raid' aspects of > the FastTrak controller and just use the drives as normal SATA drives > and create software RAID upon installation. It will be faster, more > reliable and not create any portability issues later on. > Then the other problem you have is that anaconda, as you have discovered > does not support installation to a degraded RAID setup. It's not > impossible to do, you just have to work around it. The idea would be to > setup the degraded array manually and then choose the existing > partitions for you installation within anaconda manually and don't let > anaconda create the RAID partitions at all...just use what is existing. In this case anaconda doesn't see anything! No physical devices at all! I tried deleting existing partitions and running installer again - same story, anaconda acts as there are no drives installed. Thinking of a bad/missing driver again, but I'm pretty sure it worked 'as is' in Fedora 8. > I think you are making this way too difficult on yourself. I would give > up completely on 'upgrade' from F8 to F12. I would give up using Promise > FastTrak 'fake' RAID, back up all of your files from your 'fake raid' > installation and then use anaconda to do a clean install and set up the > software raid for you and then you still have your files backed up on > another drive. Yep! Doing it now. Killed the RAID on my FastTrak board, anaconda saw the disk and is now installing. Not sure if I will want to make it a RAID again, as I don't see any benefits now... Perhaps, getting a 'real' RAID adapter could make things better. I suppose a real RAID1 would be visible as one device only, so anaconda (or whatever software it will be) won't know if it's degraded or not and will just work until last drive fails - that's what I expect from RAID1, generally. Unfortunately I don't have a real raid card to test it now. Will have to check it some other time. P.S. Still really worried about my data drives. They're now disconnected, waiting for install process to finish. It will be very, very bad if they got corrupted during my attempt of 'preupgrade'... -- Best regards... Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrading from FC8 to F12 - please help
Hello All, Wednesday, November 25, 2009, 11:14:34 PM: > Hello Craig, > Wednesday, November 25, 2009, 10:35:04 PM, you wrote: >> As I understand it, a Promise FastTrak RAID is what is known as 'fake >> raid' and not supported by out of the box installation unless you >> provide a 'driver module' at boot time. I suspect that this is something >> you did to get F8 installed originally. > Yes, it's probably a 'fake raid'. But I didn't need any additional > drivers to install Fedora 8 several years ago - I remember that for > sure. >> The real Linux recommendation is to disable the 'fake raid' aspects of >> the FastTrak controller and just use the drives as normal SATA drives >> and create software RAID upon installation. It will be faster, more >> reliable and not create any portability issues later on. >> Then the other problem you have is that anaconda, as you have discovered >> does not support installation to a degraded RAID setup. It's not >> impossible to do, you just have to work around it. The idea would be to >> setup the degraded array manually and then choose the existing >> partitions for you installation within anaconda manually and don't let >> anaconda create the RAID partitions at all...just use what is existing. > In this case anaconda doesn't see anything! No physical devices at > all! I tried deleting existing partitions and running installer again > - same story, anaconda acts as there are no drives installed. > Thinking of a bad/missing driver again, but I'm pretty sure it > worked 'as is' in Fedora 8. >> I think you are making this way too difficult on yourself. I would give >> up completely on 'upgrade' from F8 to F12. I would give up using Promise >> FastTrak 'fake' RAID, back up all of your files from your 'fake raid' >> installation and then use anaconda to do a clean install and set up the >> software raid for you and then you still have your files backed up on >> another drive. > Yep! Doing it now. Killed the RAID on my FastTrak board, anaconda saw > the disk and is now installing. Not sure if I will want to make it a > RAID again, as I don't see any benefits now... > Perhaps, getting a 'real' RAID adapter could make things better. I > suppose a real RAID1 would be visible as one device only, so anaconda > (or whatever software it will be) won't know if it's degraded or not > and will just work until last drive fails - that's what I expect from > RAID1, generally. > Unfortunately I don't have a real raid card to test it now. Will have > to check it some other time. > P.S. Still really worried about my data drives. They're now > disconnected, waiting for install process to finish. It will be very, > very bad if they got corrupted during my attempt of 'preupgrade'... I finally finished with reinstallation and basic configuration of my new F12 system. No RAID this time, at least not yet... It appeared that my data drives were not modified by the preupgrade process (or whatever it was that caused my system partition to go mad), so I didn't loose any critical data. Thanks a lot for all your help! I couldn't make it without you! -- Best regards, Andrew -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
