Hello, I have this configuration:
Lenovo Ideapad 700-15ISK
(in BIOS:
Boot mode -> Legacy support
Boot Priority -> Legacy first)
Intel Core i-7
NVMe Samsung SSD 970PRO 1TB
Win 7 Pro X64
Veracrypt 1.23-Hotfix-2
The disk is divided into 2 parts: 297 and 656 gigabytes.
When creating a hidden OS, the program copies the current OS into a hidden partition. This copying is completed, the system speaker beeps and the message is displayed:
"Copying completed.
Write error: 128 Drive: 0 Sector: 0
Enter password for hidden system: "
After entering the password, the hidden OS is loaded and a message is displayed (translation via Google translator from Russian):
ERROR: unknown status.
(If you inform us of a related error, include information in the report: AfterWMInitTasks:10114)
!!!
UPD. Replaced Samsung ssd on Sata disk Western Digital 1TB. Copying the hidden system was completed without any problems. Does this mean that VeraCrypt does not support NVMe Samsung SSD 970PRO 1TB?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After analysis, the root cause of the issue is that there was a failure while updating the MBR sector on the SSD disk and the error code (128 = 80h) means that there was a timeout when the BIOS was sending the data to the SSD disk.
This error is surprising especially that that we were able to write a large number of data before. Moreover, the current code already retries the write operation 5 times in case of failure so this does not help with the timeout issue. I suspect that it has to do with failure of BIOS to handle writing 512 bytes sectors on disks that operate natively on 4096 bytes sectors.
It is difficult to fix such problems because they are more related to the BIOS compatibility with the SSD drive and VeraCrypt has no hand in it. That being said, I can try to implement a workaround by writing 4096 bytes of data at one go instead of the 512 bytes needed.
It possible for you to test if I share a build of beta version of 1.24? This is the only way for me to check if the modification works or not.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I reuploaded the installer for 1.24-Beta0 because there was a missing file in it. Please re-download it and re-install it if you already used the previous installer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Wow, thanks Mounir! Amazing! Not having at your disposal hardware for the test, the first time you correctly identified the problem and eliminated it!) I checked it several times in a row with different parameters. Now everything is working fine, the problem has been fixed. Thanks again for the quick response and help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I have this configuration:
Lenovo Ideapad 700-15ISK
(in BIOS:
Boot mode -> Legacy support
Boot Priority -> Legacy first)
Intel Core i-7
NVMe Samsung SSD 970PRO 1TB
Win 7 Pro X64
Veracrypt 1.23-Hotfix-2
The disk is divided into 2 parts: 297 and 656 gigabytes.
When creating a hidden OS, the program copies the current OS into a hidden partition. This copying is completed, the system speaker beeps and the message is displayed:
"Copying completed.
Write error: 128 Drive: 0 Sector: 0
Enter password for hidden system: "
http://https://i.ibb.co/MpncD2m/photo-2018-12-16-22-44-14.jpg
After entering the password, the hidden OS is loaded and a message is displayed (translation via Google translator from Russian):
ERROR: unknown status.
(If you inform us of a related error, include information in the report: AfterWMInitTasks:10114)
http://https://i.ibb.co/tLBQYf6/photo-2018-12-16-22-44-21.jpg
I ask for help. Google didn't solve the problem. :(
Last edit: Aleks 2018-12-16
!!!
UPD. Replaced Samsung ssd on Sata disk Western Digital 1TB. Copying the hidden system was completed without any problems. Does this mean that VeraCrypt does not support NVMe Samsung SSD 970PRO 1TB?
Thank you for this detailed report.
After analysis, the root cause of the issue is that there was a failure while updating the MBR sector on the SSD disk and the error code (128 = 80h) means that there was a timeout when the BIOS was sending the data to the SSD disk.
This error is surprising especially that that we were able to write a large number of data before. Moreover, the current code already retries the write operation 5 times in case of failure so this does not help with the timeout issue. I suspect that it has to do with failure of BIOS to handle writing 512 bytes sectors on disks that operate natively on 4096 bytes sectors.
It is difficult to fix such problems because they are more related to the BIOS compatibility with the SSD drive and VeraCrypt has no hand in it. That being said, I can try to implement a workaround by writing 4096 bytes of data at one go instead of the 512 bytes needed.
It possible for you to test if I share a build of beta version of 1.24? This is the only way for me to check if the modification works or not.
Hello, thanks for the quick reply. It would be great to test the new version. Ready to receive the file by mail or in any way convenient for you.
Last edit: Aleks 2018-12-19
will also test
I have uploaded the installer for version 1.24-Beta0 which contains the workaround for the SSD issue to the nightly builds folder.
Thank you in advance for your feedback.
Last edit: Enigma2Illusion 2018-12-19
I reuploaded the installer for 1.24-Beta0 because there was a missing file in it. Please re-download it and re-install it if you already used the previous installer
Wow, thanks Mounir! Amazing! Not having at your disposal hardware for the test, the first time you correctly identified the problem and eliminated it!) I checked it several times in a row with different parameters. Now everything is working fine, the problem has been fixed. Thanks again for the quick response and help.