cloop8: no such device
Forum: Apps
Topic: cloop8: no such device
started by: Felson
Posted by Felson on Jan. 31 2007,23:19
Are you only able to have 8 programs loaded from the unc & uci formats?
Posted by roberts on Jan. 31 2007,23:21
Only on very old versions of DSL.Current limit is 64
Posted by Felson on Jan. 31 2007,23:35
I thought I was useing 3.1 but now I wonder.... Where can I check the current version?
Posted by roberts on Jan. 31 2007,23:39
System Stats opening screen displays the version.
Posted by Felson on Feb. 01 2007,00:34
ok, then I am having a problem 
When I try and install the package using:
mydsl-load /mnt/sda1/apps/myapp.unc
I get
error: /dev/cloop8: no such device
If I look in /dev there are, as you said, 64 of them. If I look in the /KNOPPIX/dev/ they are also all still there. (Not linking to missing files)
Any ideas?
Posted by Felson on Feb. 01 2007,01:18
Just upgraded to 3.2 and I have the same problem.
Posted by roberts on Feb. 01 2007,01:55
I just loaded up 12 cloops and got bored so I stopped.What are your system specs? Free displays? Inodes?
I don't think anyone has tested on extremely low ram and what the limiting factors might be.
Posted by Felson on Feb. 01 2007,16:49
Here is what I can give you right off the bat:- I am useing a bootable USB key, built using embeded.
- The computer has 512MB ram.
- I load 4 UNCs and 1 UCI at bootup.
- bc.unc (convert from the dsl)
- gtk .unc
- xcalc.unc (Converted from the dsl)
- xtightvnc.unc (custom UNC. It is tightvnc instead of the "realVNC" that comes with DSL. I use it only because I can connect to alternate ports with it.)
- firefox-1.5.0.6.uci
I have been thinking of taking the 4 UNC files, and making 1 out of them, or at least bc, xcalc & xtightvnc. But, even though that is a good idea from the resource point of view, that does't really fix the main issue.
Here is some stuff from Proc that my be usefull.
cpuinfo
| Code Sample |
processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.60GHz stepping : 9 cpu MHz : 2593.568 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid bogomips : 5177.34 |
modules
| Code Sample |
soundcore 3428 0 (autoclean) mousedev 3832 0 (unused) hid 22372 0 (unused) input 3168 0 [mousedev hid] unionfs 68800 7 af_packet 13544 0 (autoclean) ntfs 50944 0 (autoclean) msdos 4684 0 (autoclean) nls_iso8859-1 2844 0 (autoclean) nls_cp437 4348 0 (autoclean) e100 50508 1 hw_random 2700 0 (unused) serial 52100 0 (autoclean) pcmcia_core 39840 0 thermal 6564 0 (unused) processor 8976 0 [thermal] fan 1568 0 (unused) button 2508 0 (unused) battery 5888 0 (unused) ac 1824 0 (unused) rtc 7036 0 (autoclean) cloop 8740 12 ieee1394 183076 0 usb-storage 61696 1 usb-uhci 21644 0 (unused) ehci-hcd 16392 0 (unused) usbcore 57600 1 [hid usb-storage usb-uhci ehci-hcd] ataraid 6180 0 ide-cd 28512 0 ide-scsi 8816 0 |
meminfo
| Code Sample |
total: used: free: shared: buffers: cached: Mem: 510271488 127819776 382451712 0 2789376 86188032 Swap: 0 0 0 MemTotal: 498312 kB MemFree: 373488 kB MemShared: 0 kB Buffers: 2724 kB Cached: 84168 kB SwapCached: 0 kB Active: 33856 kB Inactive: 69900 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 498312 kB LowFree: 373488 kB SwapTotal: 0 kB SwapFree: 0 kB |
Kinda nooobish of me, but I am unsure where to get the free inode count and the free displays. I don't think this system is extreemly low. It is only a couple of years old.
Posted by roberts on Feb. 01 2007,18:57
"USB Bootable key" is a red flag to me.What filesystem type? Are you running on fat?
Fat style filesystems do not support Unix permissions well.
Caution must be taken when using pendrives for constructing any kind of extensions.
Also what does fdisk -l display, is partition table not in numerical order? Many times, I see usb pendrives display partition table with partition not ending on proper boundaries.
What happens when you manually try to mount to say cloop60?
This will show if your devices are OK.
What does the "free cloop table", /etc/sysconfig/mydsl, show for position (line) 8?
Finally, it could be a specific unc that is causing your problem.
Posted by Felson on Feb. 01 2007,20:06
I will answer these as best I can, but My USB key is fat16 as you said, but I am useing a frugal type insatall, so the Key itself is only mounted as /cdrom/I formated it as a single fat16 partision.but, you are right. It does show boundry errors as well. Never could figure that out, since I used fdisk to make it in the first place.
When I try and mount on cloop60 (or any 8+) I get:
mount: /dev/cloop60: unknown device
So, since my cloop devs are bad, I tried.
> rm /dev/cloop8
> mknod /dev/cloop8 b 240 8
And I get the same error still (with 8 instead of 60 obviously)
Line 8 (and down) of the /etc/sysconfig/mydsl reads "free"
I thought about the UNCs in question before, and tried loading 8 random other unc/uci files with the same effect.
Posted by roberts on Feb. 01 2007,20:47
Sounds like a filesystem issue to me.I never run linux on fat. I do use fat pendrives for backup/restore but that is all.
And if, you are unpacking Linux onto fat, surely permission issues will occur.
Recently, an extension was submitted and the perms of all files were atypical.
I would suggest to correct the partition table and format to native Linux. That is why I provide the pendrive installation scripts within DSL
Posted by Felson on Feb. 01 2007,20:56
Thanks for all the help so far Roberts. You have been awesome. I will try and reinstall the key with ext2 since I no longer need it to be accessible by winblows. Will post the results either way incase anyone else has this problem.
Posted by Felson on Feb. 02 2007,01:11
Well, after 3 hours of trying, I can't get it to give me even the most basic bootloader (grub or otherwise) when the key is formated to ext2. If we aren't suposed to use FAT16 as the base file system on the key, why does the how-to say to do it that way? Or am I not understanding something?
Posted by jls legalize on Feb. 02 2007,01:39
| Quote |
| I would suggest to correct the partition table and format to native Linux. That is why I provide the pendrive installation scripts within DSL |
Your pendrive script doesn't format ext the pendrive.
legalize cannabis, etc.
Posted by roberts on Feb. 02 2007,01:50
Yeah, I can't remember everything.But the script does change the geometry and therefore avoids the tweaked, broken, bad partition table. A table that may be fine for Windows but appears with many error when viewed with fdisk -l in Linux.
I just tested a 512MB with a single partition using usbhdd script which is vfat (FAT!6) and am able to mount on cloop63
Perhaps the issue is/was the bad partition table.
Posted by Felson on Feb. 02 2007,02:08
Well, I am done for the day. I will try checking the drive geometry tomorow. Thanks for all your help guys. just in short,
sfdisk -l /dev/sda
retuens this
1019 cylinders, 5 heads, 50 sectors/track
which would be 254750 sectors total.
so should I be
1024/7/32?
or would
1019/10/25
be good still?
Posted by Felson on Feb. 02 2007,18:19
ok, I used 1019/10/25It still has the same problem it did before.
I will try it on a different computer, and see if that makes a diff.
Posted by knix on Aug. 17 2007,18:40
Sorry for posting a half-year-old thread...It might be a problem with the cloop.o-module in the minirt24.
I had the same trouble with the 3.4 "initrd version". It used to work in 3.3 with the "small" minirt24.gz
I diff'ed the contents of the 50MB and the "small" minirt24.gz and found different /modules/cloop.o. After replacing the cloop.o in the 50MB-minirt24 by the cloop.o from the "small" minirt24 it worked !! (at least on my machine)
The "good" cloop.o has 11655 bytes, the "bad-7-cloop-devices-only" has 11399 bytes.
Maybe the cloop.o can be replaced in the new initrd-version?
Maybe this fixes your problem?
Posted by roberts on Aug. 17 2007,19:20
Thanks for reminding me. I need to update that cloop module. Oh the joy of changing kernel and modules. Add to my todo list.
Posted by knix on Aug. 17 2007,19:33
...just for my interest: where is the "max # of cloops" wired? In the kernel config?thx (and please forget my other thread, sorry...)
Posted by roberts on Aug. 17 2007,20:02
The number of devices in DSL is 64, (0 .. 63).Also I use a table of size 64 to keep track of mounted uci/unc
But I actually compiled 128 into the cloop module.
I didn't want to use up too many i-nodes on low memory machines to create all 128 devices. Also, there was initially much concern when so many cloops were being used.
The table setup is initialized in /etc/init.d/dsl-config