Polaris96
May 29th, 2009, 06:24 AM
I want to transfer my / and /var directories to a RAID0 array. I'm almost there (if it can actually be done). here's what I have done, so far, and where I'm hitting the wall:
1. Installed and addressed 1 PCI-e Adaptec SCSI U320 controller and 2 Seagate Cheetah U320 15k x 18G HDDs
2. Installed mdadm and lvm2. Configured and initialized RAID0 array md0 with drives listed above. set them up in two LVs (md0v and md0r)
3. used mkfs to install reiser4 FS's on both partitions
4. used dd to clone my existing / and /var onto md0r and md0v, respectively.
OK, all of that worked GR8. Not only did I not get errors, but I was able to mount and verify the integrity of the data on the RAID array partitions. Then:
5. Altered fstab to mount / and /var onto the new partitions (I used the UUIDs of md0r and md0v)
6. Rebooted and .... splat! "filesystem failed integrity check"
7. used a single user session to restore the original fstab and now things are back to original.
I figured just changing fstab would be a bit of a hack and I'm not surprised it failed. Is there a way to make the system boot from the Raid directories instead of the original PATA directories of the same name? The data are identical. I'm hoping one or more of the following will fix this up:
a) Maybe either mdadm or lvm have not set up the devices, yet, when fstab tries to mount them?
b) Maybe there's something in /boot that can be tweaked to redirect the root directory to it's new location.
I learned a lot getting to this point and even if I need to restart from scratch I'll live with it, but I really hope somebody can help me get past this final hurdle.
I'm on the pearson retrofit of KDE3.5 for Jaunty, and I don't believe that comes in an alternate install version. Also, I have read that mdadm is a better solution than fakeraid unless you plan on a dual boot system (I've closed my last window). I figure there MUST be a way to make this work. Any help would be much appreciated.
1. Installed and addressed 1 PCI-e Adaptec SCSI U320 controller and 2 Seagate Cheetah U320 15k x 18G HDDs
2. Installed mdadm and lvm2. Configured and initialized RAID0 array md0 with drives listed above. set them up in two LVs (md0v and md0r)
3. used mkfs to install reiser4 FS's on both partitions
4. used dd to clone my existing / and /var onto md0r and md0v, respectively.
OK, all of that worked GR8. Not only did I not get errors, but I was able to mount and verify the integrity of the data on the RAID array partitions. Then:
5. Altered fstab to mount / and /var onto the new partitions (I used the UUIDs of md0r and md0v)
6. Rebooted and .... splat! "filesystem failed integrity check"
7. used a single user session to restore the original fstab and now things are back to original.
I figured just changing fstab would be a bit of a hack and I'm not surprised it failed. Is there a way to make the system boot from the Raid directories instead of the original PATA directories of the same name? The data are identical. I'm hoping one or more of the following will fix this up:
a) Maybe either mdadm or lvm have not set up the devices, yet, when fstab tries to mount them?
b) Maybe there's something in /boot that can be tweaked to redirect the root directory to it's new location.
I learned a lot getting to this point and even if I need to restart from scratch I'll live with it, but I really hope somebody can help me get past this final hurdle.
I'm on the pearson retrofit of KDE3.5 for Jaunty, and I don't believe that comes in an alternate install version. Also, I have read that mdadm is a better solution than fakeraid unless you plan on a dual boot system (I've closed my last window). I figure there MUST be a way to make this work. Any help would be much appreciated.