current setup: fedora 9, amd mobo, sata drives, linux raid 1, startup loads driver called sata_nv new setup: intel mobo, marvel chipset??...same harddrives. I move the Hd's over (actually cloned them first) to the new mobo and startup goes, but when it tries to load the raid volumes, it stops with Booting fails as it cannot see the volumes or mount anything (and yet it loaded grub and other stuff just fine). What I did try earlier was to also perform the fedora 10 upgrade from dvd and I got linux to boot just fine (but I don't want fedora 10 due to ip and dns issues...so don't bother asking). So now I'm thinking if I can move the Hd's over and keep my existing setup I would be greatful. My questions is that do you think the issue is an sata/ahci controller issue and maybe the sata_nv (nvidia sata chipset from the amd mobo) is causing the boot problem. - Is there a way to modprobe before even starting the fedora 9, or maybe a way to remove the sata_nv from startup so that it probes itself? - I'm still fairly new so I may ask for detailed help. I was imagining going into resuce mode, chroot sysimage, then somehow fix the startup...all this from a cloned drive of course. TIA
or maybe an easier question if I didn't ask it above: How can I edit the "startup" so that it doesn't load the sata_nv driver once I move the drives over, this way fedora 9 will load the correct driver it needs (hopefully)? TIA
You can remove sata_nv from /etc/modules and create a new ramdisk with mkinitrd. But this works only if sata_nv was built as a module, not statically into the kernel.
sorry falko, I do't have a /etc/modules on my system. by the way, I'll check the ispconfig forums but has anyone asked why the upgrade from fc9 to fc10 kills the dns setup?
What's the output of ls -l /etc? Could also be modules.conf, or something with modprobe, or files in a subdirectory beginning with modules or modprobe. I didn't notice anything like that. What has happened? What exactly isn't working anymore? Any errors in your logs?
I found a /etc/modprob.d dir: anaconda blacklist floppy-pnp i915modeset modprobe.conf.dist as for the dns issue, not sure, I gave up on the upgrade/migration to f10 due to static ip issues that other people had as well....that's why I'm at where I am with this sata_nv issue. Of course, I could always do the "normal" Move ISP Config procedure, but I thought the hardware move should be easy enough. funny thing is, I have a another new f10 box and I'm having issue setting up ispconfig and finding sites on secondary internal ip's (secondary due to ssl's). (I won't bother you with this yet, I'll search around for answers first, I should be able to fix this one myself with forum help).
Falko, thank you for all your help and of course for ispconfig (and to you Till). Anyway, here is the solution to this problem: I think it was a new mobo controller issue, so I went into rescue mode, deleted udev persistent rules and ran /sbin/mkinitrd with the current kernel into the same named image. rebooted and tada, it worked! I can't take the credit though other than the days of searching... http://www.mail-archive.com/[email protected]/msg21247.html I do have a small issue with mount.nsf failing, so hopefully I can fix that.
