[opensuse] curious studiowriter problem
Hello, I just got a curious problem. Some time ago I used studio writer to write a network install cd to an usb flash key. Nothing wrong in this (I could install a netbook with it). Just now I needed this key to hold scanned images. My HP all in one can scan and store directly on such a key. Of course the printer do not know other than fat system. I * removed the only partition on the key with fdisk. YaST can't (because parted can't). This is a small partition, the cd image itself. then I created a new 900Mb partition (it's a 1Gb key) with yast and still with yast formatted it with fat. I could with no problem use it on the HP printer/copier and write there my jpegs I can read them on the printer (if ever I wanted to print them) But if I plug the device in my 12.1, I get two devices, one "generic usb", the other openSUSE-Net and the last mounts and shows the net cd file list (and the file are there, I can read them, at least part of them - not tried all) To read my images, I had to umount this net iso and manually mount /dev/sde1 - after that it reads without problem in Dolphin. looks like there are two content tables (and the images are small, so most disk sectors are not overwritten) I wonder why I had this result. Is it necessary to post a bugzilla ? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 15 Jan 2012 19:10:42 +0100 jdd-gmane <jdd@dodin.org> wrote:
Hello,
I just got a curious problem.
Some time ago I used studio writer to write a network install cd to an usb flash key. Nothing wrong in this (I could install a netbook with it).
Just now I needed this key to hold scanned images. My HP all in one can scan and store directly on such a key.
Of course the printer do not know other than fat system.
I
* removed the only partition on the key with fdisk. YaST can't (because parted can't). This is a small partition, the cd image itself.
then I created a new 900Mb partition (it's a 1Gb key) with yast and still with yast formatted it with fat.
I could with no problem use it on the HP printer/copier and write there my jpegs
I can read them on the printer (if ever I wanted to print them)
But if I plug the device in my 12.1, I get two devices, one "generic usb", the other openSUSE-Net and the last mounts and shows the net cd file list (and the file are there, I can read them, at least part of them - not tried all)
To read my images, I had to umount this net iso and manually mount /dev/sde1 - after that it reads without problem in Dolphin.
looks like there are two content tables (and the images are small, so most disk sectors are not overwritten)
I wonder why I had this result. Is it necessary to post a bugzilla ?
thanks jdd
Hi Run fdisk -l it will probably show a p1 partition, delete all the partitions with fdisk and re-run YaST partitioner over it again to recover. -- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.1 (x86_64) Kernel 3.1.0-1.2-desktop up 2 days 23:32, 4 users, load average: 0.17, 0.17, 0.33 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 15/01/2012 19:15, Malcolm a écrit :
Run fdisk -l it will probably show a p1 partition, delete all the partitions with fdisk and re-run YaST partitioner over it again to recover.
it's what I did in the fisrt place. studiowriter is necessary to have a bootable usb device, that's why I suspect some strange behavior :-) thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, January 15, 2012 12:44:36 PM jdd-gmane wrote:
Le 15/01/2012 19:15, Malcolm a écrit :
Run fdisk -l it will probably show a p1 partition, delete all the partitions with fdisk and re-run YaST partitioner over it again to recover.
it's what I did in the fisrt place.
studiowriter is necessary to have a bootable usb device, that's why I suspect some strange behavior :-)
dd if=/dev/zero of=/dev/<usb_stick> After that there will be nothing from previous content. Just be careful, it will zero anything you tell it is of (output file).
thanks jdd
-- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 16/01/2012 04:14, Rajko M. a écrit :
After that there will be nothing from previous content. Just be careful, it will zero anything you tell it is of (output file).
sure, I know that. I only wondered if this is a bug of writer, because I don't think ordinary user can use dd without risk. Or may be YaST? there should be a friendly way of reinitializing a key after writer use thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Mon, 16 Jan 2012, jdd-gmane wrote:
Le 16/01/2012 04:14, Rajko M. a écrit :
After that there will be nothing from previous content. Just be careful, it will zero anything you tell it is of (output file).
sure, I know that.
I only wondered if this is a bug of writer, because I don't think ordinary user can use dd without risk.
Or may be YaST? there should be a friendly way of reinitializing a key after writer use
I think the problem is, that you left the MBR bootcode in place which still called the cd-image (by sector). So, try dd if=/dev/zero of=/dev/sdX bs=1 count=446 that will zero out the bootcode, but leave the partition table as it is. HTH, -dnh -- Trying to make bits uncopyable is like trying to make water not wet. The sooner people accept this, and build business models that take this into account, the sooner people will start making money again. -- Bruce Schneier -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/01/2012 01:50, David Haller a écrit :
I think the problem is, that you left the MBR bootcode in place which still called the cd-image (by sector). So, try
dd if=/dev/zero of=/dev/sdX bs=1 count=446
that will zero out the bootcode, but leave the partition table as it is.
you are probably right. I can't try it now (not at home). Do you know a way to do this with YaST? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Tue, 17 Jan 2012, jdd-gmane wrote:
Le 17/01/2012 01:50, David Haller a écrit :
I think the problem is, that you left the MBR bootcode in place which still called the cd-image (by sector). So, try
dd if=/dev/zero of=/dev/sdX bs=1 count=446
that will zero out the bootcode, but leave the partition table as it is.
you are probably right. I can't try it now (not at home). Do you know a way to do this with YaST?
Nope. Yast and other tools can write "generic bootcode", but not zero-out the 446 Bytes. Just replace /dev/sdX by the device-name of the stick (it can be /dev/disk/by-path/ not by-label though ;) -dnh -- Calvin: People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. Hobbes: Isn't your pants' zipper supposed to be in the front? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
David Haller -
jdd-gmane -
Malcolm -
Rajko M.