I just upgraded a blade server via rsync from another server. Rebuilt the
initrd. It boots fine... except that it won't turn on the swap partition.
Several times, I've made sure swap was off, then mkswap -L SWAP-sda3
/dev/sda3, but when I do swapon -L SWAP-sda3, it complains it can't find
the device for the label.
The only thing I find while googling, other than redoing what I've done
several times now, is an old bug from CentOS 4, 0001399, which affected
*only* blade enclosures: the reporter says that all of his IBM blades were
affected (this isn't an IBM). His workaround was to make an ext2 fs, label
it, and turn that into swap.
Has anyone seen this recently, with 6.2?
mark
On 01/05/2012 06:14 PM, m.roth at 5-cent.us wrote:> mkswap -L SWAP-sda3 /dev/sda3Hi, I didn't know you could create a label within the mkswap command. I always used "e2label" as in: e2label /dev/sda2 myswap Try it with e2label just in case. Also, are you able to activate the swap using just the block device as reference? -- Jorge
From: "m.roth at 5-cent.us" <m.roth at 5-cent.us>> I just upgraded a blade server via rsync from another server. Rebuilt the > initrd. It boots fine... except that it won't turn on the swap partition. > Several times, I've made sure swap was off, then mkswap -L SWAP-sda3 > /dev/sda3, but when I do swapon -L SWAP-sda3, it complains it can't find > the device for the label.Did you check the partition label after the mkswap? I just am wondering if the '-' in the middle is handled correctly... JD