Menu

#11 problems writing to physical discs

closed
nobody
None
5
2005-02-20
2005-02-18
No

I'm trying to get colinux to create a FS on a raw
partition.
the problem is that any attempt made at writing to the
disk causes colinux to generate (non fatal) error
(printed in the console I used to start colinux, see
bottom for exerpts)
I have no problem accessing the whole disk (gentoo
fdisk works a charm)
access to partitions, of any type, seems to not work at
all though.

errors I got:
mounting (no flags):
((output from the daemon))
end_request: I/O error, dev cobd1, sector 0
Buffer I/O error on device cobd1, logical block 0
lost page write due to I/O error on cobd1

unmounting (no flags):
end_request: I/O error, dev cobd1, sector 0
Buffer I/O error on device cobd1, logical bloc
lost page write due to I/O error on cobd1

mkreiserfs (or any other raw write to the disk)
<...>
end_request: I/O error, dev cobd1, sector 2097152
end_request: I/O error, dev cobd1, sector 2097153
end_request: I/O error, dev cobd1, sector 2097154
end_request: I/O error, dev cobd1, sector 2097155
end_request: I/O error, dev cobd1, sector 2097156

cp (onto mounted cobd1):
<...>
end_request: I/O error, dev cobd1, sector 98400
Buffer I/O error on device cobd1, logical block 12300
lost page write due to I/O error on cobd1
end_request: I/O error, dev cobd1, sector 106600
Buffer I/O error on device cobd1, logical block 13325
lost page write due to I/O error on cobd1
<...>
end_request: I/O error, dev cobd1, sector 118376
end_request: I/O error, dev cobd1, sector 118384
end_request: I/O error, dev cobd1, sector 118392
end_request: I/O error, dev cobd1, sector 118400
<...>

same thing happens for any other disk, except cobd3,
cobd4, cobd5 were I have two files and the entire disk
mounted respectively.

build details:
Cooperative Linux Daemon, 0.6.2
Compiled on Sat Feb 5 10:19:28 2005

had same problem using 0.6.2rc6 (Oct '04)

Discussion

  • Anonymous

    Anonymous - 2005-02-18
     
  • Anonymous

    Anonymous - 2005-02-18

    Logged In: YES
    user_id=1221649

    sorry,ment 0.6.2 pre 6 (i think... replaced the version
    though... its the one that (was?) linked as the official
    version.

     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    Don't use colinux devices with partitioned devices. coLinux
    block device isn't partition aware. Set-up coLinux devices
    1 per partition.

     
  • Anonymous

    Anonymous - 2005-02-20

    Logged In: YES
    user_id=1221649

    i did, but any write attempt fils, and then i stumbled
    accross the /Device/Hardisk/Partition0 so i added that, and
    it works no problem ^__^.
    Also, i have a UFS partition adde to the devices, (I played
    around with darwin, yay! cept it dosent have a driver I need
    for my wlan...) and colinux recognises that one... maybee
    i'lltry and use that one for the install...

     
  • George P Boutwell

    • status: open --> closed
     
  • Anonymous

    Anonymous - 2005-02-22

    Logged In: YES
    user_id=1221649

    tracked down the problem, seems to be an issue accessing
    partitions created using the Windos NT built-in Partition
    Manager. Just hijaked my Darwin Partition wich wasn't
    working for me cause i couldn't get the network driver i
    needed *grrr*
    Yay boot straped one linux system from inside windos... now
    to download and install 95 system dependencies ^^

     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    Interesting... Where these partitions logical (created in
    the extended partition) or primary partitions? Not sure why
    Windows NT Partition Manager should be a problem. Something
    to look into I guess.

     

Log in to post a comment.