-
Senior Member
registered user
If you are running this on a KNOPPIX system, I would like to believe that you will have these :-
Code:
$ ls -al /dev/cloop*
lrwxrwxrwx 1 root root 6 2010-08-30 23:14 /dev/cloop -> cloop0
brw-rw---- 1 root disk 240, 0 2010-08-30 23:14 /dev/cloop0
brw-rw---- 1 root disk 240, 1 2010-08-30 23:14 /dev/cloop1
brw-rw---- 1 root disk 240, 2 2010-08-30 23:14 /dev/cloop2
brw-rw---- 1 root disk 240, 3 2010-08-30 23:14 /dev/cloop3
brw-rw---- 1 root disk 240, 4 2010-08-30 23:14 /dev/cloop4
brw-rw---- 1 root disk 240, 5 2010-08-30 23:14 /dev/cloop5
brw-rw---- 1 root disk 240, 6 2010-08-30 23:14 /dev/cloop6
brw-rw---- 1 root disk 240, 7 2010-08-30 23:14 /dev/cloop7
For whatever reasons if you don't have them, then you manually create them :-
# mknod /dev/cloop1 b 240 1
You shouldn't be using /dev/cloop or /dev/cloop0 because that's already been used by KNOPPIX.
Yes, if the image is good, you shouldn't get any errors when you loop mount your new compressed image. But I still would like to believe that chances of a bad burn is higher. You should do a 'knoppix testcd'.
Cheers
-
kl522, I appreciate your help with this. I get the same results you show with the ls command. My point was I know cloop1 is there but for whatever reason I get errors on the ioctl so I was checking if it was already being used. The first unused cloop is cloop1, as I'm sure you suspected, but it's not working.
I tried the bootfrom=<iso path> but that just booted directly from the knoppix live cd for some reason and didn't verify the iso.
booting with testcd gives me the following:
All files OK.
>>> Starting in Live-Mode. <<<
>>> Please do not remove medium until shutdown! <<<
/init: line 693: /bin/mount: Input/output error
/init: exec: line 742: /sbin/init: Input/output error
from here it just hangs indefinitely. This has happened on the last two images I've built and burned.
I tried to find the /init file but can't seem to view it anywhere in my "master" file structure.
-
Senior Member
registered user
Originally Posted by
frankp
the losetup command gives me a "bad file descriptor" error...
ioctl: LOOP_SET_FD: Bad file descriptor
Yes, it shows that you have a bad compressed image to start with.
I simply take a normal file and do a losetup on it, I get the same error :-
Code:
# cd /tmp
# cp /etc/hosts hosts
# losetup -r /dev/cloop1 hosts
ioctl: LOOP_SET_FD: Bad file descriptor
This happens when I run this command from the / directory. If I run it from anywhere else, I get
KNOPPIX: No such file or directory
You must path the command to the right directory/file, eg :-
# losetup -r /dev/cloop1 /some_path_some_where/knx/master/KNOPPIX/KNOPPIX
I find it strange that your working copy of KNOPPIX is resided in /KNOPPIX. In any case, you have to know what it resides, and substitute the correct path for it.
But whatever it is, if you have issued the command pointing to the correct KNOPPIX compressed image, the conclusion is that you have an invalid compressed image. You back to review your steps again.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Apple MacBook Air 13" 3.2GHz i7 Turbo - BIG SUR - 8GB RAM 512GB SSD - WARRANTY
$299.00
A-Tech 8GB DDR3 1600 PC3-12800 Laptop SODIMM 204-Pin Memory RAM PC3L DDR3L 1x 8G
$13.99
Micron 8GB DDR4 1Rx16 PC4-3200AA Laptop RAM Memory MTA4ATF1G64HZ-3G2E2
$10.00
8GB PC3L-12800S 1600MHz SODIMM DDR3 RAM | Grade A
$12.00
HyperX FURY DDR3 8GB 16GB 32GB 1600 MHz PC3-12800 Desktop RAM Memory DIMM 240pin
$15.90
G.SKILL Trident Z Neo (For AMD Ryzen) 16GB (2x8GB)DDR4 3600 (PC4 28800)Memory
$65.00
Team T-FORCE VULCAN Z 32GB (2 x 16GB) PC RAM DDR4 3200 (PC4 25600) Memory
$54.99
Team T-FORCE VULCAN Z 16GB (2 x 8GB) 288-Pin PC RAM DDR4 3200 (PC4 25600) Intel
$33.99
Kingston HyperX FURY DDR3 8GB 16GB 32G 1600 1866 1333 Desktop Memory RAM DIMM
$38.95
Hynix 64GB DDR4-3200 RDIMM HMAA8GR7AJR4N-XN HMAA8GR7CJR4N-XN Server Memory RAM
$129.99