File Corruption on Copy Issue
-
@jim9500 said in File Corruption on Copy Issue:
I've got an HP DL360 G8 hooked up to 3 D2600s / 30TB Raid 10 / P822 / 30 mil files / Windows Server 2012.
So obvious concerns.... Windows itself isn't the best for storage, but it's okay. But Windows 2012 is a decade old. Like, seriously. Nothing wrong with using Windows when it is the right tool for the job. But there's no case where it is the right tool for the job and are you willing to run an ancient, unsupported version. If you are going to commit to Windows, commit to it and keep it up to date. If you are even considering the possibility of letting it stay on an old version stop, you've proven that Windows is wrong for you and move to something that you can maintain better.
Which also brings up the question... how old were the missing patches on this old machine?
-
These were the updates installed - after reboot issue went away & hasn't come back
2021-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems KB5004956
Windows Malicious Software Removal Tool X64 - v5.91 KB890830
2021-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.2, 4.7, 4.7.1, 4.8 for Windows Server 2012 for x64 KB5004230
2021-04 Servicing Stack Update for Windows Server 2012 for x64-based Systems KB5001401
Update for Windows Server 2012 KB3102429
Intel - LAN (Server), Other hardware - Intel(R) 10 Gigabit CX4 Dual Port Server Adapter
2021-01 Security Update for Windows Server 2012 for X64-based Systems KB4535680 -
@jim9500 said in File Corruption on Copy Issue:
These were the updates installed - after reboot issue went away & hasn't come back
2021-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems KB5004956
Windows Malicious Software Removal Tool X64 - v5.91 KB890830
2021-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.2, 4.7, 4.7.1, 4.8 for Windows Server 2012 for x64 KB5004230
2021-04 Servicing Stack Update for Windows Server 2012 for x64-based Systems KB5001401
Update for Windows Server 2012 KB3102429
Intel - LAN (Server), Other hardware - Intel(R) 10 Gigabit CX4 Dual Port Server Adapter
2021-01 Security Update for Windows Server 2012 for X64-based Systems KB4535680None of those would point specifically to something that might be a problem. But several of them obviously could be, including the Intel driver one.
-
@scottalanmiller said in File Corruption on Copy Issue:
@jim9500 said in File Corruption on Copy Issue:
These were the updates installed - after reboot issue went away & hasn't come back
2021-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems KB5004956
Windows Malicious Software Removal Tool X64 - v5.91 KB890830
2021-07 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.2, 4.7, 4.7.1, 4.8 for Windows Server 2012 for x64 KB5004230
2021-04 Servicing Stack Update for Windows Server 2012 for x64-based Systems KB5001401
Update for Windows Server 2012 KB3102429
Intel - LAN (Server), Other hardware - Intel(R) 10 Gigabit CX4 Dual Port Server Adapter
2021-01 Security Update for Windows Server 2012 for X64-based Systems KB4535680None of those would point specifically to something that might be a problem. But several of them obviously could be, including the Intel driver one.
Right the network driver was updated.
I did not follow did he apply the updates and reboot? Or did the updates get applied and the reboot was pending, which he then did? -
@jaredbusch said in File Corruption on Copy Issue:
updates get applied and the reboot was pending,
Updates were applied and reboot was pending on the network driver. Starting to think this was the issue, even though I don't understand how or why it would have caused it.
-
@jim9500 said in File Corruption on Copy Issue:
Updates were applied and reboot was pending on the network driver. Starting to think this was the issue, even though I don't understand how or why it would have caused it.
Network driver... copying files across a network.. Nope cannot see it..
Or did I misunderstand the copy process? Was it all local?
-
@jaredbusch From one folder on the share to another folder on the share from a client computer. Was reproducible on specific directories before restart. Copying same files down to a networked computer locally - then back up to the share resulted in legitimate copy.
-
@jim9500 said in File Corruption on Copy Issue:
@jaredbusch said in File Corruption on Copy Issue:
updates get applied and the reboot was pending,
Updates were applied and reboot was pending on the network driver. Starting to think this was the issue, even though I don't understand how or why it would have caused it.
That's a definitely likely situation. Drivers getting updated but not reloaded means that what is on the disk and what is in RAM do not match and there might be an attempt to load something from disk later and get a conflict.
-
@jim9500 said in File Corruption on Copy Issue:
@jaredbusch From one folder on the share to another folder on the share from a client computer. Was reproducible on specific directories before restart. Copying same files down to a networked computer locally - then back up to the share resulted in legitimate copy.
Yup, that's network. So the network driver was definitely in use during the process. So while we are just guessing, it's a very rational place to start to guess at placing blame.
-
@scottalanmiller Really appreciate the input. Didn't know if it was possible for chkdsk to not pick up corruption issues or it was something mid flight. Intel drivers seems to make the most sense.
-
@jim9500 said in File Corruption on Copy Issue:
Didn't know if it was possible for chkdsk to not pick up corruption issues
Chkdsk can pick up certain types of file corruption, which you did not have. You had a network issue, which is completely different. At no time was any file corrupted. The original file stayed pristine. The new file was written flawlessly. Neither file was corrupt.
-
@jim9500 said in File Corruption on Copy Issue:
it was something mid flight. Intel drivers seems to make the most sense.
It WAS mid-flight. That's known. What is a guess is that the driver is at fault. But I'd say that it is pretty likely.
