wh7qq Junior Member
  member is offline
Joined: Apr 2011 Gender: Male  Posts: 50 Location: Hawaii
|  | usb key efforts « Thread Started on Mar 26, 2012, 12:30am » | |
@Anthony
I've been totally unable to get Remastersys to make a usb key of the iso (SalineOS-1.4-AMD64.iso) and today had another go at it. Efforts with Remastersys would run a very short time and return with no files copied and no messages to indicate that nothing had happened. I then tried Code:| dd if=/home/xxxx/SalineOS-1.4-AMD64.iso of=/dev/sdb |
|
and was able to get it to work. It took quite a bit of time to write the iso. I was using a cheapie PNY 4G flash drive.
Paul
| |
|
Anthony Nordquist Administrator
     member is offline
![[homepage] [homepage]](http://images.proboards.com/new/buttons/www_sm.png) Joined: Dec 2010 Gender: Male  Posts: 1,338
|  | Re: usb key efforts « Reply #1 on Mar 26, 2012, 10:52am » | |
I can't imagine why, the Remastersys copy tool uses dd in just about that exact manner to create the USB key. The USB copy tool is being removed from 2.0, as since 1.6 I have included a great number of Thunar custom actions, one of which allows you to create bootable USB keys from Thunar.
Please open a root terminal and run this command: /usr/bin/remastersys-usb-key-copy-tool The output should show what is going wrong for you.
Alternatively, you can install the new Thunar custom actions and right click on your ISO file and select "Burn" Image To USB Drive.
You can get all these custom actions on any previous release of SalineOS by running the following command in a root terminal, keep in mind this will overwrite any Thunar custom actions you currently have set.
wget http://www.salineos.com/Scripts/customactions.run && chmod +x ./customactions.run && ./customactions.run
| |
|
wh7qq Junior Member
  member is offline
Joined: Apr 2011 Gender: Male  Posts: 50 Location: Hawaii
|  | Re: usb key efforts « Reply #2 on Mar 26, 2012, 3:57pm » | |
I ran from the console (as root) as suggested and the following error popped up when I tried to select the source (but the script carried on):Code:| (zenity:2452): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. |
|
This means absolutely nothing to my (absent) knowledge. When I continued, selected an iso file from the my Download directory and copied to the USB key, I got :
Code:Usage: umount -h | -V umount -a [-d] [-f] [-r] [-n] [-v] [-t vfstypes] [-O opts] umount [-d] [-f] [-r] [-n] [-v] special | node... 931+0 records in 931+0 records out 976224256 bytes (976 MB) copied, 9.54223 s, 102 MB/s |
|
AFAIK, my setup is pretty much plain generic i386 salineOS...I think 1.4. I have run it on two machines now with the same error message. Both are amd boxes, one with a Gigabyte Mobo and one with a Zotac. Nothing weird or different about either.
| |
|
Anthony Nordquist Administrator
     member is offline
![[homepage] [homepage]](http://images.proboards.com/new/buttons/www_sm.png) Joined: Dec 2010 Gender: Male  Posts: 1,338
|  | Re: usb key efforts « Reply #3 on Mar 26, 2012, 8:34pm » | |
The first error is unimportant, just another reason to use sudo on 2.0.
As far as the rest of the output, something is preventing the USB key from being unmounted. Try unmounting the USB key yourself and run the utility. Improving the Thunar custom action for copying images to USB drives (Which is simply forked off of the Remastersys copy tool) is on my to do list, I will see if I can't make this part more reliable.
| |
|