[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#632867: RFP: multisystem -- tool to help creating multiboot USB drive



Thanks for immediate reaction ;-)

On Wed, 06 Jul 2011, frafa wrote:
> thank you to specify which version of debian and architecture is used ...
> and describe the problem

well -- I have pruned it already but ok -- reinstalled, mounted sdb1 (vfat) as
/media/sdb1, started (not as root, just myself, part of adm and floppy
groups, full access to /dev/sdb, sdb1 was found), validate lead to

EXIT="abort"
rm: cannot remove `/media/MULTISYSTEM/.multisystem-test': No such file or directory
./gui-detect.sh: line 372: /media/MULTISYSTEM/.multisystem-test: No such file or directory
cat: /media/MULTISYSTEM/.multisystem-test: No such file or directory

/media/MULTISYSTEM isn't there

N.B. Previously I have tried IIRC having just 1 partition and it tried to
     manipulate directly on /media//.multisystem-test

so decided to trick the system -- created it and owned to myself

now validate proceeded with just 1 puke

EXIT="abort"
rm: cannot remove `/media/MULTISYSTEM/.multisystem-test': No such file or directory

but dialog "Install grub2: /dev/sdb1" appeared -- cool -- clicked Ok

then selected pre-downloaded iso for multiarch Debian installer:
firmware-6.0.2.1-amd64-i386-netinst.iso

installation went "fine" besides few errors on creating the devices (I didn't
run as root for paranoid reasons)

cpio: dev/console: Cannot mknod: Operation not permitted
cpio: dev/null: Cannot mknod: Operation not permitted
30975 blocks


and installed into /media/MULTISYSTEM (which is just a directory on /) --
so redid all the above by mounting /dev/sdb1 as /media/MULTISYSTEM (I guess the
tool should be smart to reuse the mount point instead of demanding
/media/MULTISYSTEM)  -- installation seemed to go fine... 

tried to automagically run it from multisystem in VirtualBox: lead to a
new terminal with bulk of errors:

VBoxManage: error: Could not find a registered machine named 'multisystem'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.asOutParam())" at line 336 of file VBoxManageModifyVM.cpp
VBoxManage: error: Could not find an open hard disk with location '/home/yoh/.VirtualBox/multisystem.vmdk'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, pMedium.asOutParam())" at line 174 of file VBoxManageDisk.cpp
VBoxManage: error: Could not find a registered machine named 'multisystem'
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(VMName).raw(), machine.asOutParam())" at line 153 of file VBoxManageMisc.cpp
RAW host disk access VMDK file /home/yoh/.VirtualBox/multisystem.vmdk created successfully.
Virtual machine 'multisystem' is created and registered.
UUID: 7ae4709a-eee0-4122-914a-e71bdbad984b
Settings file: '/media/MIRRORS/VirtualBox/Machines/multisystem/multisystem.vbox'
 Press enter to continue 
Waiting for the VM to power on...
VM has been successfully started.

and VM failed to run due to unbootable drive (usb drive was not made anyhow
visible withing the VM)

tried with QEMU from multisystem which ran

qemu -no-acpi -boot c -usb -usbdevice disk:/dev/sdb -hda /dev/sdb -m 512

with the same success... tried to boot some laptop -- also didn't work --
so it seems that grub didn't install correctly... ok -- tried to do it
manually, although I guess it could be incorrect invocation:


$> grub-install --boot-directory=/media/MULTISYSTEM/boot /dev/sdb 
/usr/sbin/grub-setup: warn: Your embedding area is unusually small.  core.img won't fit in it..
/usr/sbin/grub-setup: warn: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub-setup: error: will not proceed with blocklists.

may be that was the reason which I've not spotted reported by multisystem... ?

btw -- it would be nice if all tmp files get nicely groupped under a directory
under /tmp instead of being scattered around it

-- 
=------------------------------------------------------------------=
Keep in touch                                     www.onerussian.com
Yaroslav Halchenko                 www.ohloh.net/accounts/yarikoptic



Reply to: