colinux-devel Mailing List for Cooperative Linux (Page 16)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

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 20:31

Message:
1. I am sorry. From MS docs I knows, that the disks are numbered from 0,
and partitions from 1. When I want to access entire disk, I newer use
"\PartitonY". So I've noticed word "partition",
and ignored its number :).

2. I tried to reproduce the error several times, using Flash Drives 4, 8
and 32 Gb, but did not succeed. The message "coscsi0: unable to open
device..." may indicate that the disk is used by another process. The drive
letter does not matter, because is the letter of the partition. The
NT-program can access entire disk as "\\.\PhysicalDriveX" and disk can be
locked. So it is very important to know what processes, system or not, are
running at NT-side when you started coLinux.

Peter.

----------------------------------------------------------------------

Comment By: German Salvador (germansalvador)
Date: 2009-11-20 18:49

Message:
About the bug:

I have tried using cobd0=\device\harddisk2\partition0 instead of scsi, and
it works ok. Only that then I can't access the partitions as cobd01 or
something like that. I think I can make a workaround using several
consecutive invocations to colinux:
- scsi0=... for creating the partitions
- several cobdX  for formatting and installing the data I need.

I'll try as soon as I can.

Thanks in advance,

And about \device\harddiskX\partition0 or not:

Peter,

I didn't used \\.\PhysicalDriveX\Partition0, but
\device\harddiskX\Partition0. It's not the same thing.

Anyway, I wanted to know if \device\harddiskX and
\device\harddiskX\partition0 are synonyms, but it doesn't seem like that:

With a new 8 GB flash pen and colinux using
scsi0=\device\harddisk2\partition0:

scsi0 : Cooperative Linux SCSI Adapter
scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI:
5
sd 0:0:0:0: [sda] 15646720 512-byte hardware sectors (8011 MB)
...
sd 0:0:0:0: [sda] 15646720 512-byte hardware sectors (8011 MB)
..
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk

colinux:~# fdisk -l
Disk /dev/sda: 8011 MB, 8011120640 bytes
247 heads, 62 sectors/track, 1021 cylinders
Units = cylinders of 15314 * 512 = 7840768 bytes
Disk identifier: 0x1ceab904

With, as suggested, scsi0=\device\harddisk2:

scsi0 : Cooperative Linux SCSI Adapter
scsi 0:0:0:0: Direct-Access     coLinux  CODISK           1.01 PQ: 0 ANSI:
5
coscsi0: unable to open device! rc: 1
coscsi0: unable to open device! rc: 1
coscsi0: unable to open device! rc: 1
coscsi0: unable to open device! rc: 1
sd 0:0:0:0: [sda] READ CAPACITY failed
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x00
sd 0:0:0:0: [sda] Sense not available.
...
sd 0:0:0:0: [sda] Attached SCSI disk

colinux:~# fdisk -l
colinux:~#

I  haven't tried with the \\.\PhysicalDriveX.. syntax, because the
previous version of the tool I'm making, wich is just a kind of dd but in
windows, uses \device\harddiskX\Partition0 for writting raw binary disk
images, with MBR and usually 4 partitions, and works fine.

References:
* From http://www.cygwin.com/cygwin-ug-net/using-specialnames.html

The new fixed POSIX names are mapped to NT internal devices as follows:
...
/dev/sda	        \device\harddisk0\partition0	(whole disk)
/dev/sda1	\device\harddisk0\partition1	(first partition)
...
/dev/sda15	\device\harddisk0\partition15	(fifteenth partition

So,

/dev/sda  is like \device\harddisk0\partition0
/dev/sda1 is like \device\harddisk0\partition1

The partition numbers start with 1, not with 0. In windows the partition0
is then reserved for the whole disk, wich is just what I need to access in
colinux

Germán

----------------------------------------------------------------------

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

2004	Jan (64)	Feb (530)	Mar (266)	Apr (580)	May (360)	Jun (161)	Jul (185)	Aug (164)	Sep (123)	Oct (160)	Nov (59)	Dec (84)
2005	Jan (156)	Feb (95)	Mar (124)	Apr (81)	May (79)	Jun (179)	Jul (35)	Aug (64)	Sep (56)	Oct (57)	Nov (18)	Dec (41)
2006	Jan (65)	Feb (37)	Mar (59)	Apr (73)	May (65)	Jun (27)	Jul (54)	Aug (76)	Sep (103)	Oct (23)	Nov (45)	Dec (29)
2007	Jan (41)	Feb (47)	Mar (61)	Apr (24)	May (14)	Jun (6)	Jul (23)	Aug (30)	Sep (16)	Oct (9)	Nov (53)	Dec (36)
2008	Jan (19)	Feb (49)	Mar (74)	Apr (21)	May (24)	Jun (5)	Jul (9)	Aug (53)	Sep (26)	Oct (23)	Nov (32)	Dec (19)
2009	Jan (47)	Feb (49)	Mar (39)	Apr (61)	May (28)	Jun (19)	Jul (12)	Aug (10)	Sep (31)	Oct (16)	Nov (60)	Dec (26)
2010	Jan (17)	Feb (9)	Mar (32)	Apr (11)	May (24)	Jun (33)	Jul (5)	Aug (2)	Sep (7)	Oct (8)	Nov (17)	Dec (7)
2011	Jan (12)	Feb (16)	Mar (2)	Apr (12)	May (5)	Jun (10)	Jul (3)	Aug (3)	Sep (2)	Oct (1)	Nov (17)	Dec (1)
2012	Jan (9)	Feb (9)	Mar (8)	Apr (4)	May (2)	Jun (1)	Jul (4)	Aug (8)	Sep (11)	Oct (1)	Nov (2)	Dec (2)
2013	Jan	Feb (7)	Mar (4)	Apr (10)	May	Jun	Jul	Aug	Sep	Oct	Nov (5)	Dec (3)
2016	Jan	Feb (2)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2023	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)

colinux-devel Mailing List for Cooperative Linux (Page 16)

Run Linux on Windows or other OSes, natively.

colinux-devel — Cooperative Linux development mailing list