Re: Replacing both disks in RAID1
Toomas Aas wrote: But if it is necessary, it should be possible to bring the machine up to single user mode and modify the fstab there, right? Given, of course, that the root partition is left on ar0s1a. Yes, that makes fine sense. Although if you want to feel _really_ good about it, have a live CD on hand. I would recommend FreeSBIE 1.1, but it won't boot with the Promise card. (at least for me and others it won't... see pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/72960) Cheers, Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Replacing both disks in RAID1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 14 January 2005 18:47, Toomas Aas wrote: > Derek wrote: > But if it is necessary, it should be possible to bring the machine up to > single user mode and modify the fstab there, right? Given, of course, > that the root partition is left on ar0s1a. If a valid fstab-entry for the rootfilesystem is missing, the system asks you to enter the filesystem-type and the device where the rootfilesystem resides. You just need to enter a string like "ufs:ar0s1a". If some more fstab-entries fail to mount your filesystems during system startup, you will end up automatically at a shell prompt. From there you can mount your filesystems by using the 'mount' command and edit your fstab. It's maybe good to be familiar with 'man 8 boot', just in case. Cheers, ch - -- Christian Hiris <[EMAIL PROTECTED]> | OpenPGP KeyID 0x3BCA53BE OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB6BMo09WjGjvKU74RAg/2AJ9pm0ud8M1HwGQs+qIhyUlOaup47QCZAWxB E+SjWJj1MwaKIwF81Wb3+Pc= =kWqf -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Replacing both disks in RAID1
Derek wrote: Toomas Aas wrote: 1. Attach one of the new drives to free ICH4 IDE port on motherboard, partition it and transfer the data using dump/tar. At this stage, I would recommend doing this in single user mode, to keep filesystem modifications during the procedure down. Yes, that was my plan. Definitely a good idea. I typically use dump for all partitions when in single user mode like so: #adjkerntz -i #swapon -a #mount -a ... #mount /dev/ad0s1a /mnt/newroot ... /mnt/newroot# dump 0af - / | restore xf - /mnt/newtmp# dump 0af - /tmp | restore xf - ...etc I need to use tar for some things, since I'd also like to re-arrange partitioning a bit. I think I have that part figured out, including how to make all the daemons happy with new locations for the data. 2. Remove the 80 GB drives, attach 200 GB drives (one with data, one blank) to TX2 IDE ports and re-create the mirror using Promise onboard BIOS utility. I would go with this if you can afford the time. On servers that we don't want down for long, I recreate the mirror in the BIOS, let it mirror to 1%, and then reboot (ignoring the RAID error), and start rebuilding with atacontrol. It still takes a while, and the server is slow because of the excessive disk i/o, but it is responding. I'm planning to do this on Saturday when downtime is not that big an issue. 3. Reboot, fix the fstab (if necessary) and be done with it. Shouldn't need a reboot/mess with fstab if you are careful. If I'd left the partitioning the same, then yes, but I do want to do some changes there. From my experience with the Promise cards, this is the way to go. I've had to upgrade serveral machines, as we've been using the cards in production. Thanks for confirmation. I sleep better tonight. The one caveat that I would warn you about is making sure that all your corresponding partitions line up, to prevent having to mess with fstab (and have the data in the same relative physical location on the drive) But if it is necessary, it should be possible to bring the machine up to single user mode and modify the fstab there, right? Given, of course, that the root partition is left on ar0s1a. Thanks a lot, -- Toomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Replacing both disks in RAID1
Toomas Aas wrote: 1. Attach one of the new drives to free ICH4 IDE port on motherboard, partition it and transfer the data using dump/tar. At this stage, I would recommend doing this in single user mode, to keep filesystem modifications during the procedure down. I typically use dump for all partitions when in single user mode like so: #adjkerntz -i #swapon -a #mount -a ... #mount /dev/ad0s1a /mnt/newroot ... /mnt/newroot# dump 0af - / | restore xf - /mnt/newtmp# dump 0af - /tmp | restore xf - ...etc 2. Remove the 80 GB drives, attach 200 GB drives (one with data, one blank) to TX2 IDE ports and re-create the mirror using Promise onboard BIOS utility. I would go with this if you can afford the time. On servers that we don't want down for long, I recreate the mirror in the BIOS, let it mirror to 1%, and then reboot (ignoring the RAID error), and start rebuilding with atacontrol. It still takes a while, and the server is slow because of the excessive disk i/o, but it is responding. 3. Reboot, fix the fstab (if necessary) and be done with it. Shouldn't need a reboot/mess with fstab if you are careful. From my experience with the Promise cards, this is the way to go. I've had to upgrade serveral machines, as we've been using the cards in production. The one caveat that I would warn you about is making sure that all your corresponding partitions line up, to prevent having to mess with fstab (and have the data in the same relative physical location on the drive) So if your fstab looks something like: /dev/ar0s1b none swap... /dev/ar0s1a / ufs... /dev/ar0s1f /tmp ufs... /dev/ar0s1g /usr ufs... /dev/ar0s1e /var ufs Make sure that your new disk label's partions correpond to the lettering: newswap -> /dev/ad0s1b newroot -> /dev/ad0s1a newtmp -> /dev/ad0s1f newusr -> /dev/ad0s1g newvar -> /dev/ad0s1e You don't need any dumping for the swapfs. I don't know what will happen if you do, never tried. Cheers, Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Replacing both disks in RAID1
Toomas Aas wrote: I have a small server running FreeBSD 4.10, 2 x 80 GB drives mirrored on Promise TX2 integrated RAID1 controller. I'd like to replace the 80 GB drives with 200 GB drives. Here's my current plan: 1. Attach one of the new drives to free ICH4 IDE port on motherboard, partition it and transfer the data using dump/tar. 2. Remove the 80 GB drives, attach 200 GB drives (one with data, one blank) to TX2 IDE ports and re-create the mirror using Promise onboard BIOS utility. 3. Reboot, fix the fstab (if necessary) and be done with it. I have one doubt with it. Currently my partitions are ar0s1a (/), ar0s1b (swap), ar0s1e (/var) etc. When I create corresponding partitions on the new drive while it is attached to ICH4 controller, the partitions are created as ad0s1a, ad0s1b etc. When I then move this drive to TX2 port and re-create the mirror the partitions should again be ar0s1a, ar0s1b etc. Will it "just work" or will it not work at all? Another thought - maybe I shouldn't create the new array using the Promise BIOS utility, but instead should bring the server up and use 'atacontrol create RAID1'? What do you think? Which method has a better chance of success? -- Toomas Aas |arvutivõrgu peaspetsialist | head specialist on computer networks| |Tartu Linnakantselei | Tartu City Office | - +372 736 1274 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Replacing both disks in RAID1
Hello! I have a small server running FreeBSD 4.10, 2 x 80 GB drives mirrored on Promise TX2 integrated RAID1 controller. I'd like to replace the 80 GB drives with 200 GB drives. Here's my current plan: 1. Attach one of the new drives to free ICH4 IDE port on motherboard, partition it and transfer the data using dump/tar. 2. Remove the 80 GB drives, attach 200 GB drives (one with data, one blank) to TX2 IDE ports and re-create the mirror using Promise onboard BIOS utility. 3. Reboot, fix the fstab (if necessary) and be done with it. I have one doubt with it. Currently my partitions are ar0s1a (/), ar0s1b (swap), ar0s1e (/var) etc. When I create corresponding partitions on the new drive while it is attached to ICH4 controller, the partitions are created as ad0s1a, ad0s1b etc. When I then move this drive to TX2 port and re-create the mirror the partitions should again be ar0s1a, ar0s1b etc. Will it "just work" or will it not work at all? Thanks in advance, -- Toomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
