On 04/28/2015 01:10 PM, Nio Wiklund wrote:
This is interesting:-)
- Was the system transferred to the pendrive with Unetbootin? Did you
activate persistence? Why should things be written to sdb1 (unless we
are talking about writing the files for persistence for example log
files, .bash_history etc).
- What would happen with a system transferred with the Startup Disk
Creator alias usb-creator-gtk (maybe with and without persistence)?
- What would happen for you with a system transferred with mkusb? (maybe
with and without persistence (using a casper-rw partition in another
drive)). This is what I have been using while isotesting Vivid without
finding any problems with overwritten or otherwise damaged systems in
the pendrive.
-o-
I think you have found a bug. If you tell us also the version of
Unetbootin(?), Lubuntu Vivid desktop or Lubuntu Vivid alternate? 32-bit
or 64-bit? Maybe we need some other critical data too. Then we can
repeat your test-case.
Nio:
The pendrive (USB drive) was created with unetbootin on Lubuntu 14.04
(current). The version info (from Synaptic package manager) is:
585-2ubuntu1. I had 4000 megabytes of persistent space on it.
I originally tried creating the USB drive using
usb-creator-gtk
but the USB drive it created did not boot, so (given the large number of
times I've been 'burned' by that application), I vowed never to use it
again.
If the problem occurs shutting down the live USB system, what package
would it be against?
The problem appears to be easy to reproduce.
Simply create a bootable USB drive using unetbootin from an ubuntu 15.04
ISO, then boot to it, and use it to install a system. When shutting
down the USB drive system, the problem will occur, and it will not boot
after that.
In fact, when I mount the drive on my system after that, it is mounted
read-only.
--
Sincerely,
Aere
--
Lubuntu-users mailing list
Lubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
