Re: Move Fedora Server to new machine, RAID1 -> Single disk

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Sep 28, 2024 at 11:23 AM Michael D. Setzer II <mikes@xxxxxxxx> wrote:
>
> On 27 Sep 2024 at 19:05, Jeffrey Walton wrote:
>
> From:                   Jeffrey Walton <noloader@xxxxxxxxx>
> Date sent:              Fri, 27 Sep 2024 19:05:31 -0400
> Subject:                Move Fedora Server to new machine, RAID1 ->
> Single disk
> To:                     users@xxxxxxxxxxxxxxxxxxxxxxx
> Send reply to:          noloader@xxxxxxxxx,
>         Community support for Fedora users
> <users@xxxxxxxxxxxxxxxxxxxxxxx>
>
> > Hi Everyone,
> >
> > I have a Fedora Server running F40 on an old Proliant G5 with hardware
> > RAID1. The machine is giving too much trouble so I would like to
> > migrate to newer hardware with a single SSD. Both machines are x86_64.
> >
> > I've been researching methods to perform the migration, but I am not
> > clear on the strategy. Some folks say provide a method and say it
> > works, other folks say it does not work. I think I have hit
> > diminishing returns on reading from the web.
> >
>
> Seen this message and a number of replies. Some comments.
> I've been maintainer of G4L disk imaging program since 2004, so
> some things.
>
> With some hardware raid systems the OS doesn't see it as raid,
> since it only sees that the hardware shows it. So might only show
> as a single drive.
> Had a Novell server with Duplexed Drives and noted only 1 drive
> had boot loader installed, so one had to manually copy it to second
> drive. So, would handle a drive failure, but boot from drive might
> not work on next boot. Old Novell 2.2 machine long long ago.
>
> Another thing. Should proble create a new rescue kernel, since the
> regular kernels generally only include the current hardware files,
> so if hardware is real different, might not have required files to
> load. Moved a system from old ide drive to sata drive and regular
> kernel didn't load. Used rescue kernel, and it worked fine. Then just
> hard id reinstall kernal, and it corrected issue with default kernel.

Thanks. I will look at it.

Jeff
-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux