WriteFile fails for > 4700 blocks (SD card raw write / Window)

Question

I am writing / reading raw data on a SD card. The code for writing is working up to approx. 4700 blocks and fails after this limit. Here is the code:

   //Data to be written
   uint8_t* sessions;
   sessions = (uint8_t *) malloc(2048*sizeof(uint8_t));
   unsigned int i;
   for(i=0;i<(2048*sizeof(uint8_t));i++) sessions[i]=8;

   DWORD dwWrite;

   HANDLE hDisk=CreateFileA("\\\\.\\K:",  // drive to open = SD CARD
            GENERIC_WRITE,                // access to the drive
            FILE_SHARE_READ | // share mode
            FILE_SHARE_WRITE,
            NULL,             // default security attributes
            OPEN_EXISTING,    // disposition
            FILE_FLAG_NO_BUFFERING,               // file attributes
            NULL);            // do not copy file attributes


   if(hDisk==INVALID_HANDLE_VALUE) 
   {
      CloseHandle(hDisk);
      printf("ERROR opening the file !!! ");
   }

   DWORD dwPtr = SetFilePointer(hDisk,10000*512,0,FILE_BEGIN); //4700 OK 

   if (dwPtr == INVALID_SET_FILE_POINTER) // Test for failure
   {
     printf("CANNOT move the file pointer !!! ");
   }

   //Try using this structure but same results: CAN BE IGNORED
   OVERLAPPED osWrite      = {0,0,0};
   memset(&osWrite, 0, sizeof(osWrite));
   osWrite.Offset = 10000*512;                //4700 OK
   osWrite.hEvent = CreateEvent(FALSE, FALSE, FALSE, FALSE);

   if( FALSE ==  WriteFile(hDisk,sessions,2048,&dwWrite,&osWrite) ){
       printf("CANNOT write data to the SD card!!! %lu",dwWrite);
   }else{
       printf("Written %lu on SD card",dwWrite);
   }

   CloseHandle(hDisk);

The issue is with the function "Writefile" (windows.h). If the number of block is less than 4700. everything is fine (data are written on the SD card) but if the block number is let's say 5000 or 10000, the function fails "Written 0".

Notice that without FILE_FLAG_NO_BUFFERING, no way to open the drive (SD card). The "OVERLAPPED" is a failed attempt to make it works, not using it (WriteFile(hDisk,sessions,2048,&dwWrite,NULL) )leads to the same behaviour. "SetFilePointer" works also for blocks higher than 4700. Have tested as well 2 different SD cards. I am on Windows 10.

Any hint as to what is happening?

Thank you for your input

Do you really want to write to logical drive (partition on SD card) and not physical drive (SD card itself)? — Andrey Turkin, May 23 '17 at 16:05

score 2 · Accepted Answer · edited Jun 20 '20 at 09:12

From the documentation for WriteFile:

A write on a volume handle will succeed if the volume does not have a mounted file system, or if one of the following conditions is true:

The sectors to be written to are boot sectors.

The sectors to be written to reside outside of file system space.

You have explicitly locked or dismounted the volume by using FSCTL_LOCK_VOLUME or FSCTL_DISMOUNT_VOLUME.

The volume has no actual file system. (In other words, it has a RAW file system mounted.)

You are able to write to the first couple of megabytes because (for historical reasons) the file system doesn't use that space. In order to write to the rest of the volume, you'll first have to lock the volume using the FSCTL_LOCK_VOLUME control code.

Thank you very much. That's make it. – Amar May 25 '17 at 07:32 — Amar, May 25 '17 at 07:32

score 0 · Answer 2 · answered May 23 '17 at 18:32

0

You should pass Null as the 3rd parameter of SetFilePointer, lpDistanceToMoveHigh, unless you are using the higher order 32 bits of a 64-bit address. Also, if you are not using the OVERLAPPED structure, make sure to pass Null to WriteFile for that parameter.

Also, be sure that you are not having any overflows for the data types you are using. And, be mindful of the addressing limitations of the system you are working on.

MSDN WriteFile
MSDN SetFilePointer

answered May 23 '17 at 18:32

Nathan Smith

13
6

op in own code and pass 0 as the 3rd parameter of `SetFilePointer`. also when used `OVERLAPPED` the `SetFilePointer` become absolute senseless and have no any effect. this not explain error. need begin with result of `GetLastError` after write fail – RbMm May 23 '17 at 18:41
After reading [Do you use null or 0 for null pointers in c++](https://stackoverflow.com/questions/176989/do-you-use-null-or-0-zero-for-pointers-in-c), I agree there is no difference in functionality of the code. The rest of my answer are hints of things to check as requested by the question. – Nathan Smith May 23 '17 at 21:19
SetFilePointer: works for me if third parameter is 0 or NULL. WriteFIle: yes, last parameter is NULL without OVERLAPPED (I have removed the OVERLAPPED structure). Thanks for your time – Amar May 25 '17 at 07:36

WriteFile fails for > 4700 blocks (SD card raw write / Window)

2 Answers2