4 posts / 0 new
Last post
mattdarnell
mattdarnell's picture
Joined: 2007/10/25
Points: 20

Building a new system and the installer hangs when trying to install SATA RAID.

If I choose the option for manual control the system works but you have to manually create the partitions.

Here is a video showing the two scenarios; is there a log of the output.
https://www.youtube.com/watch?v=DucOI4UC3Js

Is there a way to see output during the startup?

-----------------------------------------------

That part of the kickstart file seems pretty innocuous:

#Partition clearing information
clearpart --all --initlabel

# Creates the BOOT partition that is 200mb in size
part raid.01 --size=200 --ondisk=hda --asprimary
part raid.02 --size=200 --ondisk=hdb --asprimary

# Creates the SWAP partition (512mb)
part raid.11 --size=512 --ondisk=hda --grow --maxsize=2048
part raid.12 --size=512 --ondisk=hdb --grow --maxsize=2048

# Creates the root (/) partition that is able to grow to fill
part raid.21 --size=1024 --grow --ondisk=hda
part raid.22 --size=1024 --grow --ondisk=hdb

# Creates the root (/drbd) partition that is able to grow to fill
part raid.31 --size=1024 --grow --ondisk=hda
part raid.32 --size=1024 --grow --ondisk=hdb

# Now create the raids using the above partitions
raid /boot --level=1 --device=md0 --fstype=ext3 raid.01 raid.02
raid swap --level=1 --device=md1 --fstype=swap raid.11 raid.12
raid / --level=1 --device=md2 --fstype=ext4 raid.21 raid.22
raid /drbd --level=1 --device=md3 --fstype=ext4 raid.31 raid.32

mattdarnell
mattdarnell's picture
Joined: 2007/10/25
Points: 20

Tried Single, and both RAID options, neither worked.

SATA Kickstart:
#Partition clearing information
clearpart --all --initlabel

# Creates the BOOT partition that is 200mb in size
part raid.01 --size=200 --ondisk=sda --asprimary
part raid.02 --size=200 --ondisk=sdb --asprimary

# Creates the SWAP partition (512mb)
part raid.11 --size=512 --ondisk=sda --grow --maxsize=2048
part raid.12 --size=512 --ondisk=sdb --grow --maxsize=2048

# Creates the root (/) partition that is able to grow to fill
part raid.21 --size=1024 --grow --ondisk=sda
part raid.22 --size=1024 --grow --ondisk=sdb

# Creates the root (/drbd) partition that is able to grow to fill
part raid.31 --size=1024 --grow --ondisk=sda
part raid.32 --size=1024 --grow --ondisk=sdb

# Now create the raids using the above partitions
raid /boot --level=1 --device=md0 --fstype=ext3 raid.01 raid.02
raid swap --level=1 --device=md1 --fstype=swap raid.11 raid.12
raid / --level=1 --device=md2 --fstype=ext4 raid.21 raid.22
raid /drbd --level=1 --device=md3 --fstype=ext4 raid.31 raid.32

mattdarnell
mattdarnell's picture
Joined: 2007/10/25
Points: 20

I have been looking more at the partitions and wondering what the drbd partition is for? It takes up about 50% of the drive space.

There is no drdb mount point and the partition is unmounted & wasted space.

Is that for replication if you use the "Thirdlane UC Cluster"?

eeman
eeman's picture
Joined: 2007/11/06
Points: 260

its for people wanting to do the HA option. If you dont reserve it initially there is no way to implement it later. You can always customize your kickstart file and tweak it.

Erik Smith
dCAP
Thirdlane/Asterisk Support available
esmith.bgnv@gmail.com