Re: GEOM_RAID in GENERIC 9.1
Hi. On 17.08.2012 14:44, Gabor Radnai wrote: Sorry the content of original mail I replied to was missed. For clarity here it is: [...] My reply again then: Unfortunately I am a less experienced user so no clue how to disable GEOM_RAID but i am hit by this issue. My zfs setup is totally messed up. Would appreciate if you could share the trick. Additionally: building a new kernel solves the issue naturally but is there anything more convenient solution? What is your trick? Your choice could be: - boot old kernel (even 8.x), compile a new one without GEOM_RAID and install/boot it - take the LiveCD, boot it, copy a kernel from the network without a GEOM_RAID instead your kernel - use usb stick with an installed FreeBSD (it must be using GEOM_RAID-free kernel) in order to do the same thing etc I did the thing with usb stick. There's also a way to clear the GEOM_RAID metadata from your disks, but I didn't manage how to do this (asked a couple of questions here though) so I won't be giving any advice about it. Eugene. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: GEOM_RAID in GENERIC 9.1
On 30.07.2012 08:33, Eugene M. Zheganin wrote: On 30.07.2012 11:04, Eugene M. Zheganin wrote: I am aware about how this thing works and what it does. However, every time I upgrade new server I got hit by it again and again, simply forgetting to remove it from the kernel's config. I'm afraid this thing will hit lots of FreeBSD installations after the release; it may be easily removed but still it will poison the life of many engineers and I really think it's a bomb, and should be removed from GENERIC. Okay, I feel like I need to clarify this, as some decent guys pointed me out that I'm very unclear and even rude (sorry for that, that's unintentional). GEOM_RAID was inserted instead of ataraid, but ataraid wasn't messing with zpooled disks: with GEOM_RAID the kernel takes both (in case of mirrored pool) providers, and mountroot just fails, as it sees no zfs pool. Plus, it's even more. This time I have "disabled" the raid in it's "BIOS" before installing FreeBSD. After mountroot failed, I booted 9.0-R from usb flash, trying to avoid any surgery with kernel files, like manual install from another machine. I was curious if I will be able to resolve this issue using base utilities. So, I loaded geom_raid via 'graid load', kernel said like 'Doh... I have ada0/ada1 spare disks', then I tried to remove the softraid label remains with 'graid remove' - and it failed, because there's no array at all, only "spares". So, the 'graid status' is empty, 'graid list' is empty' and it's obvious that some surgery is needed. And I'm not disappointed that it's happened to me, no, because I know how to resolve this. But the thing that I'm really afraid of is that this default option will hit the less experienced engineers. Thank you for your report. I will recheck deletion of spare disks. But what's about `geom status/list` in this case, there are special options -a and -g to handle geoms without providers. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: GEOM_RAID in GENERIC 9.1
Hi. On 30.07.2012 11:04, Eugene M. Zheganin wrote: I am aware about how this thing works and what it does. However, every time I upgrade new server I got hit by it again and again, simply forgetting to remove it from the kernel's config. I'm afraid this thing will hit lots of FreeBSD installations after the release; it may be easily removed but still it will poison the life of many engineers and I really think it's a bomb, and should be removed from GENERIC. Okay, I feel like I need to clarify this, as some decent guys pointed me out that I'm very unclear and even rude (sorry for that, that's unintentional). GEOM_RAID was inserted instead of ataraid, but ataraid wasn't messing with zpooled disks: with GEOM_RAID the kernel takes both (in case of mirrored pool) providers, and mountroot just fails, as it sees no zfs pool. Plus, it's even more. This time I have "disabled" the raid in it's "BIOS" before installing FreeBSD. After mountroot failed, I booted 9.0-R from usb flash, trying to avoid any surgery with kernel files, like manual install from another machine. I was curious if I will be able to resolve this issue using base utilities. So, I loaded geom_raid via 'graid load', kernel said like 'Doh... I have ada0/ada1 spare disks', then I tried to remove the softraid label remains with 'graid remove' - and it failed, because there's no array at all, only "spares". So, the 'graid status' is empty, 'graid list' is empty' and it's obvious that some surgery is needed. And I'm not disappointed that it's happened to me, no, because I know how to resolve this. But the thing that I'm really afraid of is that this default option will hit the less experienced engineers. Eugene. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
