On Friday 24 August 2007 14:16:47 Christoff van Zyl wrote:
> On Fri, 24 Aug 2007 12:02:29 +0000, Christoff van Zyl wrote:
> > On Fri, 24 Aug 2007 07:54:45 -0400, Frank Sweetser wrote:
> >> Christoff van Zyl wrote:
> >>> Hi all
> >>>
> >>> I am busy pulling my hair out of my head on this error, but no luck. I
> >>> am running Ubuntu 6.06.1 LTS with bacula -2.0.3 compiled from source.
> >>> Iwas wondering if anybody can help me on my mistake, I have googled
> >>> but no luck.
> >>>
> >>> Help would really be appreciated.
> >>>
> >>> Thanks
> >>> Christoff
> >>>
> >>>
> >>>  Creating the Initial RAM disk image....
> >>> Initial RAM disk contents will be 68136 KB
> >>> 68136+0 records in
> >>> 68136+0 records out
> >>> 69771264 bytes (70 MB) copied, 0.646026 seconds, 108 MB/s
> >>> /dev/loop2: No such file or directory
> >>> Could not stat /dev/loop2 --- No such file or directory
> >>
> >> Do you have a /dev/loop2 file on your system?
> >>
> >> tty/10 1004 erwin 07:54:02 $ ls -l /dev/loop2 | cat
> >> brw-r----- 1 root disk 7, 2 2007-08-01 13:23 /dev/loop2
> >
> > Thanks for the reply, only /dev/loop/. If I my ask what is the purpose of
> >  /dev/loop2?
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
>
> I have done the following:
>
> [EMAIL PROTECTED]:/dev# MAKEDEV -v loop
> create loop0    b 7 0 root:disk 0660
> create loop1    b 7 1 root:disk 0660
> create loop2    b 7 2 root:disk 0660
> create loop3    b 7 3 root:disk 0660
> create loop4    b 7 4 root:disk 0660
> create loop5    b 7 5 root:disk 0660
> create loop6    b 7 6 root:disk 0660
> create loop7    b 7 7 root:disk 0660
>
> But the is no /dev/loop* devices
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

I have stumbledon the following and got my loop devices, let see if the rescue 
disk will work.

[1] Background information

This (using MAKEDEV) was for a hoary system 
For a Dapper system the loop devices will disappear in the next reboot. 
This because dapper uses udev which creates devices in a much more dynamic way 
than it is done in hoary which uses devfs.

For dapper there are two ways to have all loop devices at bootup.
1) As recommended in /usr/share/doc/udev/README.gz:
  - It is recommended to use the /lib/udev/devices directory to place
    device nodes and symlinks in, which are copied to /dev at every boot.
    That way, nodes for broken subsystems or devices which can't be
    detected automatically by the kernel, will always be available.

So open a terminal and become root.
Go to the /lib/udev/devices/loop/ directory.
(A 'ls -l' shold show a device 0)

Create the new loop devices from 1 to 7 by typing:
mknod 1 b 7 1
mknod 2 b 7 2
mknod 3 b 7 3
mknod 4 b 7 4
mknod 5 b 7 5
mknod 6 b 7 6
mknod 7 b 7 7

Restart udev by typing:
/etc/init.d/udev restart

You now should see the new devices by typing:
ls -lR /dev/loop*


2) An entry in /etc/udev/links.conf

Start gedit as root, press <Alt>+<F2> and type:
sudo gedit /etc/udev/links.conf

Paste the following:

# hack to have loop devices from loop/0 to loop/7
M loop/1 b 7 1
M loop/1 b 7 1
M loop/2 b 7 2
M loop/3 b 7 3
M loop/4 b 7 4
M loop/5 b 7 5
M loop/6 b 7 6
M loop/7 b 7 7

Save the file.

Restart udev from a terminal by typing (as root):
/etc/init.d/udev restart

You now should see the new devices by typing:
ls -lR /dev/loop*

--
The information contained in this communication is confidential and may be 
legally privileged. It is intended solely for the use of the individual or 
entity to whom it is addressed. If you are not the intended recipient you are 
hereby notified that any disclosure, copying, distribution or any action taken 
or omitted in reliance on the contents of this information is strictly 
prohibited and may be unlawful. Whilst all reasonable steps are taken to ensure 
the accuracy and integrity of information and data transmitted electronically 
and to preserve the confidentiality thereof, the Berco Group and its associated 
business entities and/or units accept no liability or responsibility whatsoever 
if information or data is, for whatever reason, corrupted or does not reach its 
intended destination.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to