casper umount segmentation fault

Bug #147117 reported by Jones D. Le on 2007-09-30
Affects Status Importance Assigned to Milestone
casper (Ubuntu)

Bug Description

Binary package hint: casper

I tested out the 20070928 Gutsy LiveUSB with persistent mode enabled. When I reboot my USB Flash, I encountered this error:

Please note: I followed this tutorial:

* Umounting local filesystem
  umount2: Device or resource busy
  umount: /cdrom busy - remounted read only
  Segmentation fault

* casper is resyncing snapshots and caching reboot files
  /etc/rc6.d/casper: 103: file: not found
  /etc/rc6.d/casper: 103: file: not found
  Please remove the disc and close the tray (if any) then press ENTER:

There are 2 errors here: the umount script and the casper failed to locate 'file'
I dont know details to report for bug fixing

waxhell (waxhell) wrote :

I can verify this bug in Gutsy release.

I don't get the resync bugs, but I definitely get the segfaults. I also may have some problems in properly writing back the files to the casper-rw partition.

Followed the directions on the ubuntu wiki.

This may be a duplicate of bug 125702.

Nathan Handler (nhandler) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in casper:
status: New → Incomplete
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in casper:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers