Bug 1213

Summary:	No boot Live version of USB Stick
Product:	Mageia	Reporter:	Hermes Laws <hermeslaws>
Component:	Release (media or process)	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, pterjan
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Hermes Laws 2011-05-08 16:34:59 CEST

Description of problem:
https://forums.mageia.org/en/viewtopic.php?f=7&t=216

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. tried on oracle virtual Box 
2. tried on 4GB and 16GB stick formated as ZIP and as HDD
3.


"bio too big device loop0 (2>0)
squashfs error: squashfs_read_data failed to read 0x0
squashfs_super_block

Freeing unused kernel: unable to read 552k freed
"

Ahmad Samir 2011-05-10 20:04:32 CEST

CC: (none) => mageia, pterjan

Comment 1 Olivier Blin 2011-05-10 20:18:54 CEST

How did you copy the live to USB stick?

Comment 2 Hermes Laws 2011-05-20 19:28:15 CEST

hey i think i tried it with the fedora usb creator, also with dd for windows.

Now i got the RC working on the main hdd under windows bootloader.


Im sorry i havnt answered early, tried some other Distro (Linux) but now im back,

maybe i get the same error when the new live version is available i will try again.

Manuel Hiebel 2011-08-23 18:26:17 CEST

Keywords: (none) => NEEDINFO

Comment 3 Manuel Hiebel 2011-10-25 11:39:16 CEST

Hello, have you test with the Mageia 1 ?

Comment 4 Manuel Hiebel 2011-12-09 23:14:47 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD