On 10/02/06 09:40:00AM -0700, Bob McGowan wrote:
> Sorry, I forgot that bit ;(
>
> The command 'mkswap -L label device' will create a swap area and add a
> label for it. This should probably be done from a rescue disk
> environment, so you don't confuse the running kernel with changes to its
>
Sorry, I forgot that bit ;(
The command 'mkswap -L label device' will create a swap area and add a
label for it. This should probably be done from a rescue disk
environment, so you don't confuse the running kernel with changes to its
swap area. I'm not aware of a separate tool to label a swa
This one time, at band camp, Joost Kraaijeveld said:
> Hi Bob,
>
> Thanks: it works as described.
>
> Just 1 other question: can I label my swap partition?
>
> If I try e2label /dev/sda5 /my_name it returns:
>
> e2label: Bad magic number in super-block while trying to open /dev/sdb5
> Couldn'
Hi Bob,
Thanks: it works as described.
Just 1 other question: can I label my swap partition?
If I try e2label /dev/sda5 /my_name it returns:
e2label: Bad magic number in super-block while trying to open /dev/sdb5
Couldn't find valid filesystem superblock.
TIA
--
Groeten,
Joost Kraaijeveld
On 9/29/06, Joost Kraaijeveld <[EMAIL PROTECTED]> wrote:
Hi,
After an update of my kernel to 2.6.17 my machine only boots at random.
I have googled for a solution and it appears that it happens because of
the way the harddisks are found during startup . The solution described
involves using labl
I'm only familiar with the ext[23]/xfs filesystem commands which is what
you appear to be using. Other FS's have similar tools, I expect.
First, you need to be sure your disks are labeled. For ext[23], the
command is 'e2label -L /dev/...' where ... would be sda4 or hdb2, or
whatever else you
6 matches
Mail list logo
