Menu
▾
▴
[coLinux-devel] [ colinux-Bugs-2899010 ] scsi disk disconnects while creating an ext3 filesystem
|
From: SourceForge.net <no...@so...> - 2009-11-20 13:09:30
|
Bugs item #2899010, was opened at 2009-11-17 12:43 Message generated for change (Comment added) made by peter_kuznetsov You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2899010&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: scsi disk disconnects while creating an ext3 filesystem Initial Comment: I'm trying to make a mkfs.ext3 /dev/sda1 , while sda is scsi0=\Device\Harddisk2\Partition0 , an 8 GB USB Flash Pen drive. Before mkfs ends, the linux console starts complaining with lots of lines like: sd:0:0:0:0: rejecting I/O to offline device and after stop, /sda is no longer visible. Tried with the 20091115 snapshot. ---------------------------------------------------------------------- Comment By: Peter Kuznetsov (peter_kuznetsov) Date: 2009-11-20 15:09 Message: Please, read about "scsiX=..." parameter in "colinux-daemon.txt" more carefully: ... <path to image file> can be a raw disk drive, with format "\\.\PhysicalDriveX", where X starts with 0 for first harddisk. Be carefully with these configs, you risk datas on your drive C:. Don't mount a partition that is in use on windows side! ... "\\.\PhysicalDriveX", but not "\\.\PhysicalDriveX\PartitionY". Peter. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-11-20 14:31 Message: Article "HOW TO: Create Multiple Partitions by Using the Bmpart.exe Tool in Automated Deployment Services" (http://support.microsoft.com/?scid=kb%3Ben-us%3B821303&x=14&y=11 ) describes only input parameters for Bmpart.exe: "The DeviceName PARAMETER, \device\harddisk0\partition0, refers to the whole hard disk", not the structure of the hard disk. Bmpart.exe can extract the whole hard disk NAME "\device\harddisk0" from the string "\device\harddisk0\partition0". What way and why it will be done "mkfs.ext3"? This program has no idea that somewhere on the NT-side you made a mistake in the parameters of another program, "colinux-daemon.exe". Peter. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-11-20 13:05 Message: I know, Peter. I didn't say otherwise. Read again my message. I'm only stating that, in Windows block device nomenclature, ...\Partition0 is the whole disk I don't like it that way, and would rather prefer \Device\HarddiskN as the whole disk, but ask MS why is it like that. If you don't belive it, ok. quote: "The DeviceName parameter, \device\harddisk0\partition0, refers to the whole hard disk." (taken from http://support.microsoft.com/?scid=kb%3Ben-us%3B821303&x=14&y=11 ) ---------------------------------------------------------------------- Comment By: Peter Kuznetsov (peter_kuznetsov) Date: 2009-11-19 16:17 Message: Each Harddisk has only one Master Boot Record (512 byte sector at the very beging of the disk with partition table at the end of the MBR) . Each partion has own boot sector, also 512 bytes, but wihout partition table. Please read documentation, for example http://en.wikipedia.org/wiki/Master_boot_record Peter. ---------------------------------------------------------------------- Comment By: German Salvador (germansalvador) Date: 2009-11-19 10:02 Message: As far as I know, \Device\HarddiskN\Partition0 refers to the whole device, including MBR and all partitions. I'm, using it like that in other tool without problems for a long time. I need access to the MBR because I need to repartition the device. About the other comment, I had a normal usage pattern while mkfs'ing the disk, I opened other windows, change active focus, etc. I didn't did any heavy task, but I was neither frozen while it worked. The Flash disk didn't had associated any drive letter, either. German ---------------------------------------------------------------------- Comment By: Peter Kuznetsov (peter_kuznetsov) Date: 2009-11-17 19:34 Message: Just now I've noticed the error in your parameter: scsi0=\Device\Harddisk2\Partition0 <== scsi0 is disk with Master Boot Record, it is NOT partition. When you run 'mkfs.ext3 /dev/sda1', you are trying to use /dev/sda1 as "the partition of of the partition", not as the partition of of the disk. Your should use scsi0=\Device\Harddisk2 (without '\Partition0) Peter. ---------------------------------------------------------------------- Comment By: Peter Kuznetsov (peter_kuznetsov) Date: 2009-11-17 18:02 Message: Before 20091115 snapshot I've had the similar error. With 20091115 everything works. But you and me have different preconditions: My case Your case Image on hard drive USB pen drive Only while switching NT processes ??? When I've tested new SVN revision r1293, have tried only "simple" magic: 1. Open "Process Explorer" window. 2. While 'mkfs' working, mouse clicked at "Process Explorer" and back at "colinux-console-nt". For previous revision with this two conditions the error was reproduced. With last revision - not. If you want somebody to reproduce this error, please write, what have you exactly did while 'mkfs.ext3' worked? I mean your activity with mouse, keyboard, or other user interface input devices, which coLinux console was used and so on. Some NT processes may block (lock) devices for it's "individual use" and it is erroneus to work with the drive or partition at this time from coLinux. So your "magic" may be much complicated than my. Then I can check three USB Flash Drives of various vendors: 4, 8, and 32 Gb. Peter. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2899010&group_id=98788 |
