Opened 20 years ago

Closed 20 years ago

#927 closed defect (worksforme)

Can't auto create loop devices

Reported by: hongfengwbw@… Owned by: lfs-book@…
Priority: lowest Milestone:
Component: Book Version: SVN
Severity: normal Keywords:
Cc:

Description

lfs Version: LFS-BOOK-SVN-20041017 kernel config: CONFIG_BLK_DEV_LOOP=y I use fellow command: #mount -o loop /data/FC3-test3-i386-disc1.iso /mnt mount: could not find any device /dev/loop#

Thanks.

Change History (7)

comment:1 by kpfleming@…, 20 years ago

My systems have /dev/loopN devices as expected, running unstable from about two weeks ago (same as testing except for the hotplug package, at least as relates to this problem).

Does your system have any /dev/loopN devices? If not, do you have the loop device driver compiled into your kernel, as a module, or neither?

comment:2 by hongfengwbw@…, 20 years ago

No loop* devices in /dev directory. kernel have compiled loop devices.


I try command: # cat /proc/devices 180 usb Block devices:

2 fd 3 ide0 7 loop

...... #mknod /dev/loop0 b 7 0 #mknod /dev/loop1 b 7 3 #mount -o loop /data/FC3-test3-i386-disc1.iso /mnt the command is ok. LFS Version: LFS-BOOK-SVN-20041017 Thanks.

comment:3 by hongfengwbw@…, 20 years ago

Version: TESTINGSVN

comment:4 by jeremy@…, 20 years ago

Checked both LFS-Unstable 20040831 and 20041014 systems, and /dev/loop* devices are definately created. Please look at the contents of your /sys/block directory, and see if you have the entries there for the loop devices. Also run:

dmesg | grep loop

and ensure you see a line similar to: loop: loaded (max 8 devices)

comment:5 by hongfengwbw@…, 20 years ago

Yes,I run command: #dmesg |grep loop Calibratig delay loop ... 4767.74 BogoMIPS loop: loaded (max 8 devices) # ls /sys/block fd0 hda hdc loop0 loop1 loop2 ...... but I run command: #ls -l /dev/ |grep loop |wc -l 0


Other devices no problem. LFS-Version:LFS-BOOK-SVN-20041017 Thanks!

comment:6 by jeremy@…, 20 years ago

OK. Have you made any modifications to your udev configuration files at all? I've found that if you have a syntax error anywhere in your udev config files, udevstart will silently fail to create device nodes. That's all I can think of, because we can not duplicate your problem at all.

comment:7 by jeremy@…, 20 years ago

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.