mkbootdisk : Unknown file type (unallocated)

Hitboxx · 03-03-2007, 07:37 PM

Hi Guys

Here's the error

Code:

[shrikant@shricore64 ~]$ sudo /sbin/mkbootdisk --iso --device boot.iso `uname -r`
Unknown file type (unallocated) /tmp/mkbootdisk.iF4551/.. - ignoring and continuing.

Here's my fstab

Code:

LABEL=/                 /                       ext3    defaults        1 1
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
LABEL=/home             /home                   ext3    defaults        1 2
proc                    /proc                   proc    defaults        0 0
sysfs                   /sys                    sysfs   defaults        0 0
LABEL=/usr              /usr                    ext3    defaults        1 2
/dev/hdc7               swap                    swap    defaults        0 0
LABEL=SWAP-hdc7         swap                    swap    defaults        0 0
/dev/hda1		/media/win_system	vfat	auto,noexec,quiet,umask=0000 0 0
/dev/hda5		/media/win_software	vfat	auto,noexec,quiet,umask=0000 0 0
/dev/hda6		/media/win_media	vfat	auto,noexec,quiet,umask=0000 0 0
/dev/hda7		/media/win_games	vfat	auto,noexec,quiet,umask=0000 0 0
/dev/hda8		/media/win_backup	vfat	auto,noexec,quiet,umask=0000 0 0
/dev/hdc10		/media/win_misc1	vfat	auto,noexec,quiet,umask=0000 0 0
/dev/hdc11		/media/win_misc2	vfat	auto,noexec,quiet,umask=0000 0 0
/dev/hdc2		/media/win_misc3	vfat	auto,noexec,quiet,umask=0000 0 0

I'm bothered about those swap lines, I think I should remove the first line. Is this the cause of the problem above?

Need advice
Thanks

PS : 'boot.iso' does get created but I'm not sure if it'll work.

Lenard · 03-04-2007, 12:19 PM

The error (really a warning message) is not caused by both fstab swap entries, but you are correct you only need one of them. Deleting either one should work but you want to use swapon/swapoff after making the change.

The created boot.iso is OK and will work to boot the system. If your worried then take a look at the iso file, for example;

sudo /bin/mount -t iso9660 boot.iso /mnt -o loop

The warning message is a bug and is known, it just has not been fixed yet. You will see it even if you are really root and as the message shows it can be ignored.

Hitboxx · 03-05-2007, 07:22 AM

Yes thank you for that and boot.iso is fine.