Blog
- Home
- Blog
Can't read from the source file or disk - Fix it Now ?
This article covers how to fix "can't read from the source file or disk" error.
Basically, this error triggers when trying to copy certain files to or from an external hard disk.
Many users have reported that they got "Can't read from the source file or disk" error message while copying, deleting or moving files from one location to another.
To fix Error Message: Can't read from the source file or disk:
1. Restart the PC
If you can't read from the source file or disk while copying in Windows 10, and this happens for the first time, try restarting the computer (do not turn off and on, just restart).
Rebooting helps the computer deal with such errors on its own and returns it to an adequate working state.
2. Check the file name
Changing the file name is justified when the file was created in one OS, and its use occurs in another. You may not be able to read from the source file or disk while deleting after using this file on the command line. If this is your situation, be sure to rename the file properly and restart the computer after that.
3. Try to open the file on another PC
Try to do the same as in method 2, but on another PC. Better yet, if it will be a completely different OS (for example, you have Windows installed, then look for a computer with a Mac, etc.).
This will help get rid of any conflicts between the file and the computer, which can happen quite often.
4. Use chkdsk to fix bad sectors
The free chkdsk utility usually handles such errors with ease.
SQL Server divide by zero error encountered - Fix it Now ?
This article covers methods to resolve resolve error 'SQL Server divide by zero error encountered'. This error is caused by performing a division operation wherein the denominator or the divisor is 0. This error is not encountered when the denominator or divisor is NULL because this will result to a NULL value.
Many client applications or drivers provide a default value of ARITHABORT is OFF.
The different values might force SQL Server to produces a different execution plan, and it might create performance issues.
You should also match the setting similar to a client application while troubleshooting the performance issues.
The source file names are larger than is supported by the file system
This article covers methods to resolve Windows error "The source file names are larger than is supported by the file system". Most Windows users encounter this issue when trying to copy or delete a file on the computer and they may receive an error message saying Source Path Too Long with the explanation of the source file name(s) are larger than is supported by the file system.
This Windows error error happens mainly because one or more files that are kept in a series of subfolders that have long names, but Windows only allows 258 characters at most in the folder path subfolder.
This will prevent you from moving the files or folders that are saved in this folder.
To fix this windows error, try the following:
Delete the File/Folder by Bypassing the Recycle Bin
You know that when you delete files from your computer, these files will be first moved to the Recycle Bin and they will stay there until you delete them permanently.
i. Click on the file or folder that is bothered by the Source Path Too Long error.
ii. Press the SHIFT and Delete buttons at the same time to permanently delete the file or folder.
Drupal 406 error - Fix it Now ?
This article covers methods to resolve Drupal 406 error.
There are many errors that you may see as you visit different websites across the web.
One of the more common ones is the 406 – Not Acceptable error.
Cause for Drupal 406 error:
In regards to a site on your hosting account, the cause of the 406 error is usually due to a mod_security rule on the server.
Mod_security is a security module in the Apache web server that is enabled by default on all hosting accounts.
If a site, page, or function violates one of these rules, server may send the 406 Not Acceptable error.
To prevent Drupal 406 Not acceptable error:
Mod_security can be turned off. You can also disable specific ModSecurity rules or disable ModSecurity for each domain individually.
If you would like mod_security disabled you can disable mod_security via our Modsec manager plugin in cPanel.
Disk full due to large System Volume Information Folder on Windows
This article covers how to access System Volume Information Folder and clear up the disk space.
Basically, the disk full warning in windows can also happen due to the large System Volume Information Folder.
What is System Volume Information Folder in Windows?
1. WindowsImageBackup —system restore points on desktop Windows versions or System State backups made using Windows Server Backup (wbadmin) in server OSs;
2. The contents of Indexing Service database used for fast file search (including Outlook search);
3. Distributed Link Tracking Service database;
4. Disk snapshots made by Volume Shadow Copy, which can be used to recover older versions of files. For each snapshot, a separate file is created with a long ID as a name;shadow copy files on system volume information folder
5. NTFS disk quota settings;
6. Base and chunks of the Data Deduplication service;
7. DFS Replication database (dfsr.db);
8. WPSettings.dat file – created by the storage service (StorSvc);
9. The USB drives will also store an IndexerVolumeGuid file that defines the unique disk label used by the Windows Search service;
10. AppxProgramDataStaging, AppxStaging – Windows UWP app backups (it can be used for recovery after removal).
Make Sure the File is an NTFS Volume and isn't in a Compressed Folder or Volume
This article covers methods to resolve Windows error "Make Sure the File is an NTFS Volume and isn't in a Compressed Folder or Volume" for our customers.
The first thing you should do to isolate the error is to change the path of the downloaded ISO file.
Sometimes, the error is triggered by the address of the ISO file for some reason in which case moving the file to another drive solves the problem.
Therefore, try changing the volume in which the ISO file is stored to fix your error.
Causes of this Windows error:
This error is not something new, however, there was a certain thing that made it trigger the most.
Following are the factors that usually cause it —
1. Windows 10 security update.
For most of the users, the error came into being after the release of KB4019472 Windows 10 update which happened to be a security update. This update made the error emerge for most of the users.
2. Location of ISO file.
In some cases, the error can be due to the location or path of the downloaded ISO file. In such a scenario, you will have to change the location.
