Topic: Upgrade to Raid1

[vineus]

Hi,

I have a SME 7.2 with a 160GB HD and I want to upgrade to a 320GB HD and then add a second 320GB HD to create a Raid1 format. These drives are IDE's, HD1 is on IDE channel 1 and HD2 is on IDE channel 2. I've inserted the first 320GB HD as HD2 on IDE channel 2 to start a raid1 format, to copy the data from the 160GB HD as HD1 on IDE channel 1. I did the option 5 under the Admin menu. After many many hours, reduncancy was finished. Pulled the 160GB HD and replaced with 320GB HD as primary HD on IDE channel 1.

Computer won't boot.

I'm guessing the OS did not copy to the 320GB HD.

What did I do wrong?

I hope this makes sense, I am new (green) with raid concepts.

VWW

[byte]

I did the option 5 under the Admin menu. After many many hours, reduncancy was finished. Pulled the 160GB HD and replaced with 320GB HD as primary HD on IDE channel 1.

Sounds right, but did you wait for it to finish sync'in ?

Computer won't boot.

What does computer won't boot mean ? What do you see or what does it say  ?

What did I do wrong?

Did you see this link ?

http://wiki.contribs.org/Raid#Upgrading_the_Hard_Drive_Size

I did this under VM a few months as when you have a 160GB on a 320GB it will only be a 160GB until you upgrade/resize the Hard drive, if you follow those instructions to a "T" you can't go wrong

[vineus]

Sounds right, but did you wait for it to finish sync'in ?

Yes, I did wait for the sync process.

What does computer won't boot mean ? What do you see or what does it say  ?

When computer is powered on, it sees the 320GB HD on IDE channel 1. After all the bios startup listings the computer asks, Boot from CD?

Did you see this link ?

Yes, I saw the link in the How To's.

http://wiki.contribs.org/Raid#Upgrading_the_Hard_Drive_Size

I did this under VM a few months as when you have a 160GB on a 320GB it will only be a 160GB until you upgrade/resize the Hard drive, if you follow those instructions to a "T" you can't go wrong

To resize, I have to get the 320GB HD to boot and go into single user mode, correct?

VWW

Thanks for the reply

I didn't do the reply right. I think.

[p-jones]

I went through this excercise just two days ago and had some similiar bad experiences.

Have a look in your log files and maybe use some disk utilities to have a look at the partition layout on the new drive. Also search the forums using words like pvresize.

You may also use the option 5 again a little bit later in the process and see if the raid rebuilding.
(or from a console screen cat /proc/mdstat)

When the drive is replicated it works in blocks, however partitioning seems to work in cylinders. What I found was that the two disimiliar drives had differing geometry and the blocks did not end at cylinder boundaries. As a result I was able to boot the new replicated drive to the point where it came to mount the second partition but the boundaries of the first partition encroached on the second partition and the result was a kernel panic.  I suspect you may find something similiar.

Sep  9 21:01:00 gulfserv1 add_drive_to_raid: Warning: partition 1 does not end at a cylinder boundary
Sep  9 21:01:00 gulfserv1 add_drive_to_raid:
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: Disk /dev/sda: 9729 cylinders, 255 heads, 63 sectors/track
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: Old situation:
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: Units = blocks of 1024 bytes, counting from 0
Sep  9 21:01:00 gulfserv1 add_drive_to_raid:
Sep  9 21:01:00 gulfserv1 add_drive_to_raid:    Device Boot   Start       End    #blocks   Id  System
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: /dev/sda1   *        0+   104384     104384+  fd  Linux raid autodetect
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: /dev/sda2       104385  78148191   78043807   fd  Linux raid autodetect
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: /dev/sda3            0         -          0    0  Empty
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: /dev/sda4            0         -          0    0  Empty
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: New situation:
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: Units = blocks of 1024 bytes, counting from 0
Sep  9 21:01:00 gulfserv1 add_drive_to_raid:
Sep  9 21:01:00 gulfserv1 add_drive_to_raid:    Device Boot   Start       End    #blocks   Id  System
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: /dev/sda1   *        0+   104384     104384+  fd  Linux raid autodetect
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: /dev/sda2       104385  78148191   78043807   fd  Linux raid autodetect
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: /dev/sda3            0         -          0    0  Empty
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: /dev/sda4            0         -          0    0  Empty
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: Successfully wrote the new partition table
Sep  9 21:01:00 gulfserv1 add_drive_to_raid:
Sep  9 21:01:00 gulfserv1 add_drive_to_raid: Re-reading the partition table ...
Sep  9 21:01:04 gulfserv1 kernel: SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Sep  9 21:01:04 gulfserv1 kernel: SCSI device sda: drive cache: write back
Sep  9 21:01:04 gulfserv1 kernel:  sda: sda1 sda2

There probably is a solution to this but I havent found it yet. The other obvious solution is also pushed heavily in these forums and that is to do a new install and reload the backups. I resorted to the latter as I had a time constraint and it worked just fine.

[NickCritten]

Hi,

I have a SME 7.2 with a 160GB HD and I want to upgrade to a 320GB HD and then add a second 320GB HD to create a Raid1 format. These drives are IDE's, HD1 is on IDE channel 1 and HD2 is on IDE channel 2. I've inserted the first 320GB HD as HD2 on IDE channel 2 to start a raid1 format, to copy the data from the 160GB HD as HD1 on IDE channel 1. I did the option 5 under the Admin menu. After many many hours, reduncancy was finished. Pulled the 160GB HD and replaced with 320GB HD as primary HD on IDE channel 1.

Computer won't boot.

I'm guessing the OS did not copy to the 320GB HD.

What did I do wrong?

I hope this makes sense, I am new (green) with raid concepts.

VWW

I Think that this may simply be that your second hard drive isn't part of your BIOS boot sequence.

i.e. Your boot sequence with a Linux RAID system should be something like:

1: HDD1
2: HDD2
3: CDROM
4: Disabled

Nick