From: Henry N. <Hen...@Ar...> - 2008-05-19 23:44:02
|
Harald Weidner wrote: >>> colinux:~# cat /dev/cobd2 >>> cat: /dev/cobd2: No such device > > [...] > >> If not, run the coLinux debugger to see more about problems an the >> windows detailed error message. Run the debugger: >> colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml >> Than try to read one block. >> Stop the debugger. Open the file debug.xml with IE or notepad. Typicaly >> at the end you should see the error from block device read and the >> Windows internal error code. > > The according messages are: > > - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" > timestamp="00000016.3900969652" local_index="668" facility="0" > function="co_os_file_block_get_size" line="212" level="10" > driver_index="802"> > <string>device \Device\Harddisk0\Partition4</string> > </log> > - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" > timestamp="00000016.3900971984" local_index="669" facility="0" > function="co_os_file_block_detect_size_harddisk" line="154" level="10" > driver_index="803"> > <string>fail status C000000E</string> > </log> The translated error message from include/ddk/ntstatus.h: STATUS_NO_SUCH_DEVICE ((NTSTATUS)0xC000000EL) That means the ZwDeviceIoControlFile(..., IOCTL_DISK_GET_LENGTH_INFO, ...) does not work. That's harmless. > - <log module="colinux-driver" file="src/colinux/os/winnt/kernel/block.c" > timestamp="00000016.3900972192" local_index="670" facility="0" > function="co_os_file_block_detect_size_binary_search" line="99" level="3" > driver_index="804"> > <string>size is zero</string> > </log> coLinux can copen the devie but can't ead any? Is the device locked? Is the device opened by Windows perhaps? Please try to read a block with the windows variant of dd: dd.exe if=\Device\Harddisk0\Partition4 of=foo bs=512 count=1 Try the official names "\\?\Device\Harddisk0\Partition4" or "\\?\Device\HarddiskVolume4", as you have seen from dd --list. -- Henry N. |