AW: Error with "raid swap" in kickstart

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I ran into the same problem not long ago. I'd got no idea how to work around

until someone in this mailing list pointed my attention to the definition of

the "swap". He asked :
Why do you want to make a raid partition for temporary data in the swap area
??
So I defined two independent swap spaces, one on each disk and it worked.

See my disk configuration section :

# /boot
part raid.1 --size=128 --ondisk=sda
part raid.11 --size=128 --ondisk=sdb
# / 
part raid.2 --size=2048 --ondisk=sda
part raid.12 --size=2048 --ondisk=sdb
# /home
part raid.3 --size=2048 --ondisk=sda
part raid.13 --size=2048 --ondisk=sdb
# /tmp
part raid.4 --size=1024 --ondisk=sda
part raid.14 --size=1024 --ondisk=sdb
# /usr (rest of disk volume)
part raid.5 --size=1 --grow --ondisk=sda
part raid.15 --size=1 --grow --ondisk=sdb
# swap
part swap --size=512 --ondisk=sda
part swap --size=512 --ondisk=sdb

# RAID 1 disk assignment
raid /boot   --fstype ext3 --level 1 --device md0 raid.1 raid.11
raid /       --fstype ext3 --level 1 --device md1 raid.2 raid.12
raid /home   --fstype ext3 --level 1 --device md3 raid.3 raid.13
raid /tmp    --fstype ext3 --level 1 --device md4 raid.4 raid.14
raid /usr  --fstype ext3 --level 1 --device md5 raid.5 raid.15

Hope I could help 

Dirk
----------------------------------------------------------------------------
------------
Dirk Albert
Siemens AG, PG L 621, Germany
* Tel.: +49 - 9131 - 18 82206 (Erlangen)
* Tel.: +49 - 721 - 595 2381 (Karlsruhe)
* mailto:dirk.albert@xxxxxxxxxxx
----------------------------------------------------------------------------
------------



-----Ursprüngliche Nachricht-----
Von: Jay McCanta [mailto:mccantaj@xxxxxxxxxxx]
Gesendet: Freitag, 15. Februar 2002 17:46
An: kickstart-list@xxxxxxxxxx
Betreff: Error with "raid swap" in kickstart


I am having problems setting up a kickstart disk on v7.2.  I have a
workaround, but before I report this as a bug, can someone verify that it is
not?

Here is the disk configuration section.

clearpart --all
part raid.1 --size 46 --ondisk hda
part raid.2 --size 46 --ondisk hdb
part raid.3 --size 512 --ondisk hda
part raid.4 --size 512 --ondisk hdb
part raid.5 --size 1 --grow --ondisk hda
part raid.6 --size 1 --grow --ondisk hdb
raid /boot --fstype ext3 --level 1 --device md0 raid.2 raid.1
raid /     --fstype ext3 --level 1 --device md2 raid.5 raid.6
raid swap  --fstype swap --level 1 --device md1 raid.3 raid.4

I get the following error messages (with dump info included here).  If I
comment out the "raid swap" line, kickstart works flawlessly.

Traceback (innermost last):
  File "/usr/bin/anaconda", line 620, in ?
    intf.run(id, dispatch, configFileData)
  File "/usr/lib/anaconda/text.py", line 364, in run
    (step, args) = dispatch.currentStep()
  File "/usr/lib/anaconda/dispatch.py", line 243, in currentStep
    self.gotoNext()
  File "/usr/lib/anaconda/dispatch.py", line 143, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
    rc = apply(func, self.bindArgs(args))
  File "/usr/lib/anaconda/autopart.py", line 899, in doAutoPartition
    (errors, warnings) = sanityCheckAllRequests(partitions, diskset, 1)
  File "/usr/lib/anaconda/partitioning.py", line 595, in
sanityCheckAllRequests
    swapSize = swapSize + requestSize(request, diskset)
TypeError: number coercion failed
-----------------------------------
In Debug mode, "print requestSize(request, diskset)" returns "none" (might
be "None").  Here is more dump info...
------------------------
Local variables in innermost frame:
size: 20
baseChecks: 1
requests: <partitioning.Partitions instance at 849ded0>
rc: None
slash: mountpoint: /   type: ext3   uniqueID:9
  size: NoneM   requestSize: NoneM  grow: 0   max: None
  start: None   end: None   partnum: None
  drive: None   primary: None
  format: 1, options: None  device: None, currentDrive: None
  raidlevel: RAID1  raidspares: 0  raidmembers: ['raid.5', 'raid.6']
diskset: <partitioning.DiskSet instance at 81a5fc8>
swapSize: 0
request: mountpoint: None   type: swap   uniqueID:7
  size: NoneM   requestSize: NoneM  grow: 0   max: None
  start: None   end: None   partnum: None
  drive: None   primary: None
  format: 1, options: None  device: None, currentDrive: None
  raidlevel: RAID1  raidspares: 0  raidmembers: ['raid.3', 'raid.4']
req: mountpoint: /boot   type: ext3   uniqueID:8
  size: NoneM   requestSize: NoneM  grow: 0   max: None
  start: None   end: None   partnum: None
  drive: None   primary: None
  format: 1, options: None  device: None, currentDrive: None
  raidlevel: RAID1  raidspares: 0  raidmembers: ['raid.2', 'raid.1']
mount: /boot
warnings: []
errors: []
foundSwap: 1
checkSizes: [('/usr', 250), ('/tmp', 50), ('/var', 50), ('/home', 100),
('/boot', 20)]
----------------------------------------------------------------------------

Is this a bug or user error?  Any help is appreciated beyond compensation.

Jay McCanta
Immunex





_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux