| View previous topic :: View next topic |
| Author |
Message |
voltaic
n00b
Joined: 14 Jun 2006
Posts: 44
|
 Posted: Wed Feb 21, 2007 3:55 am Post subject: [solved] weird partition issues |
 |
|
sorry for the vague title, but its an apt one.
i am running software raid 5 setup as described by these 2 articles: http://gentoo-wiki.com/HOWTO_Migrate_To_RAID and http://gentoo-wiki.com/HOWTO_Install_on_Software_RAID.
i seem to have somehow blown away my partition table, but am still able to boot from it from an old kernel i had kept just in case.
i am wondering if use fdisk to restore the partition information, if it will also blow away the file allocation table, as it seems to still be intact.
anyway, let me know if anyone has any thoughts on this. i'm going to attach what i get from fdisk -l. just notice that /dev/md2 has no partitions on it, but is the one i am booting from.
| Code: |
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 5 40162 83 Linux
/dev/hda2 6 255 2008125 82 Linux swap / Solaris
/dev/hda3 256 9729 76099905 83 Linux
Disk /dev/hdb: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 24792 199141708+ 83 Linux
Disk /dev/sda: 37.0 GB, 37019566080 bytes
255 heads, 63 sectors/track, 4500 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 2 16033+ fd Linux raid autodetect
/dev/sda2 3 127 1004062+ fd Linux raid autodetect
/dev/sda3 128 4500 35126122+ fd Linux raid autodetect
Disk /dev/sdb: 37.0 GB, 37019566080 bytes
255 heads, 63 sectors/track, 4500 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 2 16033+ fd Linux raid autodetect
/dev/sdb2 3 127 1004062+ fd Linux raid autodetect
/dev/sdb3 128 4500 35126122+ fd Linux raid autodetect
Disk /dev/sdc: 37.0 GB, 37019566080 bytes
255 heads, 63 sectors/track, 4500 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 2 16033+ fd Linux raid autodetect
/dev/sdc2 3 127 1004062+ fd Linux raid autodetect
/dev/sdc3 128 4500 35126122+ fd Linux raid autodetect
Disk /dev/md2: 71.9 GB, 71938080768 bytes
2 heads, 4 sectors/track, 17563008 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start End Blocks Id System
Disk /dev/md1: 16 MB, 16318464 bytes
2 heads, 4 sectors/track, 3984 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start End Blocks Id System
/dev/md1p1 * 1 3984 15934 83 Linux
|
thanks!
_________________
Sam C Anderson
Last edited by voltaic on Thu Mar 01, 2007 3:15 am; edited 1 time in total |
|
| Back to top |
|
 |
HeissFuss
Guru
Joined: 11 Jan 2005
Posts: 414
|
| Posted: Wed Feb 21, 2007 4:44 am Post subject: |
|
|
That's normal output. Your array looks fine. What does mount have to say about it?
If it hasn't worked at all on the kernel you're trying to run I'd suspect you missed a scsi driver or raid option in your config. |
|
| Back to top |
|
|
Ezhdeha
n00b
Joined: 13 Oct 2004
Posts: 60
Location: Sydney, Australia
|
| Posted: Wed Feb 21, 2007 4:55 am Post subject: Those devices are partitions |
|
|
/dev/md2 naturally won't contain any partitions because it IS a partition.
you will need to make the first partition a RAID 1 because I don't think it can boot of RAID 5 in software mode.
I know that's what I had to do with mine:
| Code: | Device Boot Start End Blocks Id System
/dev/sda1 1 6 48163+ fd Linux raid autodetect
/dev/sda2 7 67 489982+ 82 Linux swap / Solaris
/dev/sda3 68 1409 10779615 fd Linux raid autodetect
/dev/sda4 1410 30401 232878240 fd Linux raid autodetect
|
where:
/dev/md0 is RAID 1 (sda1+sdb1)
/dev/md1 is RAID 0 (sda3+sdb3)
/dev/md2 is RAID 0 (sda4+sdb4)
_________________
http://www.crossnet.com.au |
|
| Back to top |
|
|
voltaic
n00b
Joined: 14 Jun 2006
Posts: 44
|
| Posted: Wed Feb 21, 2007 7:58 am Post subject: |
|
|
so its not an issue that /dev/md1 has a partition /dev/md1p1 and there is no partition under /dev/md2? i hate to belabor the question, but that seems counterintuitive to me. might i have set up something wrong to begin with to cause the partition md1p1 to exist, or should md2 in fact have md2pX?
anyway, thanks again!
_________________
Sam C Anderson |
|
| Back to top |
|
|
HeissFuss
Guru
Joined: 11 Jan 2005
Posts: 414
|
| Posted: Wed Feb 21, 2007 5:35 pm Post subject: |
|
|
I assumed from your setup that your /boot was /dev/hda1 and your / was /dev/hda3.
Just because you can make partitions on the md1 partition doesn't mean you ought to. Normally when you use md raid you create your partitions on your devices and then assign them to a raid. That raid device you then treat as a large partition. If you are wanting to partition a raid device look into LVM2 first.
Please give us more details on your problem so that we can help. The contents of your /etc/fstab for one and let us know if you can't mount your raid devices (errors.)
Also please post your /boot/grub/grub.conf. |
|
| Back to top |
|
|
Ezhdeha
n00b
Joined: 13 Oct 2004
Posts: 60
Location: Sydney, Australia
|
| Posted: Sun Feb 25, 2007 6:21 am Post subject: grub information please |
|
|
Yes, grub.conf would be very useful here
_________________
http://www.crossnet.com.au |
|
| Back to top |
|
|
voltaic
n00b
Joined: 14 Jun 2006
Posts: 44
|
| Posted: Thu Mar 01, 2007 3:16 am Post subject: |
|
|
ok, well, looks like it was a simple matter of kernel not having the drivers compiled in for my sata controller.
thanks for the help guys!
_________________
Sam C Anderson |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
