SCIENTIFIC-LINUX-USERS Archives

December 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jos van Wezel <[log in to unmask]>
Reply To:
Date:
Thu, 14 Dec 2006 11:19:25 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
Have you already checked the loop device? Is the loop module
loaded (automatically)? Try to load the loop mod first.

J

Jaroslaw Polok wrote:
>> What does not work is
>>   gzip -cd initrd-2.6.9-42.0.3.ELsmp.img > xx
>>   mount xx /mnt/initrd -t ext2 -o loop
>> The error is:
>> mount: wrong fs type, bad option, bad superblock on /dev/loop0,
>>        or too many mounted file systems
>>        (could this be the IDE device where you in fact use
>>        ide-scsi so that sr0 or sda or so is needed?)
>>
>> What am I doing wrong?
> 
> Compressed initrd is not recognized as a filesystem:
> 
> # file initrd.img
> initrd.img: gzip compressed data, from Unix, max compression
> 
> Kernel does not support compressed filesystem images...
> (this would be very time/space -inefficient: for compressions
> like gzip all the image would have to be decompressed
> into memory: this is what happens with initrd on boot)
> 
> There are compressed filesystems (read-only!) alike
> cramfs or squashfs .. but that's another story.
> (actually second stage install images for SL are cramfs,
> initrd cannot be cramfs as cramfs driver is compiled as a
> module and loaded .. from initrd .. on the other hand
> initrd may be gzip-compressed or not: both formats will be
> useable)
> 
> Cheers
> 
> Jarek
> 

ATOM RSS1 RSS2