Opened 10 years ago

Closed 10 years ago

#306 closed defect (worksforme)

Mondoarchive crashing on Fedora 10

Reported by: jgribbin Owned by: bruno
Priority: normal Milestone: 2.2.9
Component: mondo Version: 2.2.7
Severity: normal Keywords:
Cc:

Description

I am having trouble getting Mondo running on my laptop.

The computer crashes in the process of building CDs. Normally on CD1, but once I found a command line that got it through CD-9, crashing on 10.

The Mondo & Mini packages I got from Mondo's FTP site, the Fedora 10 subdirectory.

The buffer & afio were not available either from my distribution or the F10 directory on Mondo's FTP site, but I found the source RPMs on Mondo's Fedora-Extras directory which I compiled and installed.

The latest command line I've tried, after booting in Single User Mode and 'SELINUX=0' is:

bash#mondoarchive -Oc 24 -9 -d ATAPI:1,0,0 -s 700m -g

It makes it all the way to: 'backing up file system'. Then at about CDR 1: 63%, it crashes. In a manner that's like some flipped the power switch. The laptop completely shuts off, instantly (no shutdown, just off).

Laptop is a Toshiba Satellite A75 w/ P4 1GHz & 1.5 GB ram

[jimg@jimstoshiba ~]$ wodim --devices wodim: Overview of accessible drives (1 found) :


0 dev='/dev/scd0' rwrw-- : 'TOSHIBA' 'DVD-ROM SD-R2512'


[jimg@jimstoshiba ~]$ wodim -scanbus scsibus1:

1,0,0 100) 'TOSHIBA ' 'DVD-ROM SD-R2512' '1420' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *

[jimg@jimstoshiba ~]$

Attachments (1)

mondoarchive.log (104.9 KB) - added by jgribbin 10 years ago.

Download all attachments as: .zip

Change History (14)

Changed 10 years ago by jgribbin

comment:1 Changed 10 years ago by bruno

  • Status changed from new to assigned

Would you mind testing with mondo 2.2.8 beta + mindi 2.0.5 (nearly final) available at http://ftp.mondorescue.org/test/fedora/10 ?

Also Do you have any /proc mounted again (for a chroot feature) ? When a process with recent kernels does a cat /proc/kcore it now creates the same problem as the one you're seing (Cf: https://qa.mandriva.com/show_bug.cgi?id=46523) as I reported on my distro.

Also use -d /dev/scd0 instead of ATAPI:...

comment:2 Changed 10 years ago by bruno

Please try the new beta packages I made for Fedora 10 at http://ftp.mondorescue.org/test/fedora/10 as revision [2133] should anyway fix the potential /proc problem.

comment:3 Changed 10 years ago by jgribbin

Sorry I didn't get back to you faster, you got caught in my spam.

Also want to apologize for entering the bug twice, was still trying to get the hang of things.

At any rate, I tried installing the copies of mondo & mindi from your /test/fedora/10 ftp site. I also went ahead and installed the buffer package as opposed to the one I compiled. I also used '-d /dev/scd0' as opposed to 'ATAPI:'. Crashed in the same manner at about the same point, during the build of CD1.

I didn't understand what you're asking me about /proc. Mandriva's Bugzilla site denies that bug exists. Well, it was denying it. It comes up now.

I'm enough of a newbie in this department that I don't quite follow the significance, but mtab shows:

/proc /proc proc rw 0 0

So I assume this means /proc is mounted, at least in init 5. Is this what you're asking about /proc ?

comment:4 Changed 10 years ago by jgribbin

BTW - I don't know if it's the proper way to test it, but I tried 'cat /proc/kcore' from a terminal window. It seemed to finish OK, although the terminal window was not usable due to the odd characters it received. Nothing crashed though.

comment:5 Changed 10 years ago by bruno

  • Milestone changed from 2.2.8 to 2.2.9

I meant /proc may be mounted multiple times. And the version of mondo you tried was just excluding the main one, not the second, and I had a problem with latest Mandriva kernels with reading in another /proc. That's why I asked, but that doesn't seem to be your case.

What gives on your system:

which cdrecord which dvdrecord cdrecord dev=/dev/scd0 -atip dvdrecord dev=/dev/scd0 -atip cdrecord -scanbus which growisofs

Did you already tried the -eject switch to those commands ? Could it cause the issue ? Same question with the -waiti param ? Could you try with the option -m ?

comment:6 Changed 10 years ago by jgribbin

[jimg@jimstoshiba ~]$ cdrecord --version Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd Wodim 1.1.8

dvdrecord is same as cdrecord

[jimg@jimstoshiba ~]$ cdrecord dev=/dev/scd0 -atip Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'TOSHIBA ' Identification : 'DVD-ROM SD-R2512' Revision : '1420' Device seems to be: Generic mmc2 DVD-ROM. wodim: Cannot load media with this drive! wodim: Try to load media by hand. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R wodim: Cannot load media with this drive! wodim: Try to load media by hand. wodim: Cannot load media. [jimg@jimstoshiba ~]$

[jimg@jimstoshiba ~]$ dvdrecord dev=/dev/scd0 -atip
is line-for-line the same as cdrecord. My drive will only play DVDs, it won't record them.

[jimg@jimstoshiba ~]$ cdrecord --scanbus scsibus1:

1,0,0 100) 'TOSHIBA ' 'DVD-ROM SD-R2512' '1420' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *

[jimg@jimstoshiba ~]$

[jimg@jimstoshiba ~]$ growisofs --version

  • growisofs by <appro@…>, version 7.1, front-ending to mkisofs: mkisofs 2.01 is not what you see here. This line is only a fake for too clever

GUIs and other frontend applications. In fact, this program is: genisoimage 1.1.8 (Linux) [jimg@jimstoshiba ~]$

[jimg@jimstoshiba ~]$ $ sudo /usr/sbin/mondoarchive -eject -Oc 24 -9 -d /dev/scd0 -s 700m -g

resulted in 'invalid option'

[jimg@jimstoshiba ~]$ sudo /usr/sbin/mondoarchive -waiti -Oc 24 -9 -d /dev/scd0 -s 700m -g Initializing... See /var/log/mondoarchive.log for details of backup run. Checking sanity of your Linux distribution Done. Please specify only one media type Errors were detected in the command line you supplied. Please review the log file - /var/log/mondoarchive.log Segmentation fault [jimg@jimstoshiba ~]$

[jimg@jimstoshiba ~]$ $ sudo /usr/sbin/mondoarchive -m -Oc 24 -9 -d /dev/scd0 -s 700m -g

Resulted in the usual crash during the build of CD1

By the way - What does the '-m' switch do? I couldn't find any documentation for it with any of the programs involved. As to -waiti & -eject, it never occurred to me to start trying cdrecord switches as I wasn't making it to the point of CDs being burned. It appears to be dying during the CD build process.

Maybe I'm not following how you want me to try those switches?

If it makes any difference, I do burn CDs fairly regularly. Both before and after trying Mondo.

I think my install is a fairly conservative, close to stock F10. About the only stuff I've added is some stuff to allow me to watch commercial DVD movies any play a couple of codecs Fedora doesn't allow for. Mondo and Cinelerra are about as far afield as I've gone.

comment:7 Changed 10 years ago by bruno

So if you just have CD/DVD *readers* how do you think mondo can *write* media with them ? How do you burn regularly media with reader only ?

Create ISO images instead (option -i not -d)

comment:8 follow-up: Changed 10 years ago by jgribbin

My CD-Rom device is read-only w/ DVDs. It reads & writes CD-Rs just fine.

I'm using the -d switch to specify the CD writer device. Without that I get:

[jimg@jimstoshiba ~]$ sudo /usr/sbin/mondoarchive -m -Oc 24 -9 -s 700m -g Initializing... See /var/log/mondoarchive.log for details of backup run. Checking sanity of your Linux distribution Done. Fatal error... If you are using the 2.6.x kernel, please specify the CD-R(W) device. ---FATALERROR--- If you are using the 2.6.x kernel, please specify the CD-R(W) device.

-- Jim

comment:9 in reply to: ↑ 8 Changed 10 years ago by bruno

Replying to jgribbin:

My CD-Rom device is read-only w/ DVDs. It reads & writes CD-Rs just fine.

Ok understood.

So could you use the -i option to see if it's working without interaction with the burner. THen you could use the -A option to pass to mondoarchive your own burning command instead of the one it's using, if this what what is causing the issue (which I believe as it crashes around the time it should burn the first media).

comment:10 follow-up: Changed 10 years ago by jgribbin

It doesn't seem to like the -i option Maybe I'm not using it correctly?

Also, I was under the impression that I wasn't getting to the point that it was attempting to burn a CD. I looked to me the it was failing about 65% of the way through building the ISO image.

[jimg@jimstoshiba ~]$ sudo /usr/sbin/mondoarchive -m -i -Oc 24 -9 -d /dev/scd0 -s 700m -g [sudo] password for jimg: Initializing... See /var/log/mondoarchive.log for details of backup run. Checking sanity of your Linux distribution Done. Please specify only one media type Errors were detected in the command line you supplied. Please review the log file - /var/log/mondoarchive.log Segmentation fault [jimg@jimstoshiba ~]$

On a related note ... I have a spare laptop around. It's a Thinkpad A31P, 1.8 GHz P4 & 1 GB ram. Kinda/sorta similar.

I did a clean install of F10. Just a pretty basic desktop install, which is was I did on this Toshiba to begin with, and let it do it's updates.

Using the same command-line, Mondo seems to work fine. I didn't do a full back-up, just wanted to see that it made it through the 1st CD. It will take me a few days in my spare time, but I intend to do what I did to the Toshiba one step at a time and see if something causes Mondo to fail.

comment:11 in reply to: ↑ 10 Changed 10 years ago by bruno

Replying to jgribbin:

It doesn't seem to like the -i option Maybe I'm not using it correctly?

Also, I was under the impression that I wasn't getting to the point that it was attempting to burn a CD. I looked to me the it was failing about 65% of the way through building the ISO image.

THat would be important to know for usre ! Tat's why I'd like you to try to just generate ISOs to see if even without burning it's crashing the same way.

[jimg@jimstoshiba ~]$ sudo /usr/sbin/mondoarchive -m -i -Oc 24 -9 -d /dev/scd0 -s 700m -g

Remove the -c

On a related note ... I have a spare laptop around. It's a Thinkpad A31P, 1.8 GHz P4 & 1 GB ram. Kinda/sorta similar.

I did a clean install of F10. Just a pretty basic desktop install, which is was I did on this Toshiba to begin with, and let it do it's updates.

Using the same command-line, Mondo seems to work fine. I didn't do a full back-up, just wanted to see that it made it through the 1st CD. It will take me a few days in my spare time, but I intend to do what I did to the Toshiba one step at a time and see if something causes Mondo to fail.

So it could really be linked to either your HW or your FS layout.

comment:12 Changed 10 years ago by bruno

Hello,

Any news on this BR ?

comment:13 Changed 10 years ago by bruno

  • Resolution set to worksforme
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.