- Joined
- Aug 16, 2005
- Messages
- 25,879 (3.79/day)
- Location
- Alabama
| System Name | Rocinante |
|---|---|
| Processor | I9 14900KS |
| Motherboard | EVGA z690 Dark KINGPIN (modded BIOS) |
| Cooling | EK-AIO Elite 360 D-RGB |
| Memory | 64GB Gskill Trident Z5 DDR5 6000 @6400 |
| Video Card(s) | MSI SUPRIM Liquid X 4090 |
| Storage | 1x 500GB 980 Pro | 1x 1TB 980 Pro | 1x 8TB Corsair MP400 |
| Display(s) | Odyssey OLED G9 G95SC |
| Case | Lian Li o11 Evo Dynamic White |
| Audio Device(s) | Moondrop S8's on Schiit Hel 2e |
| Power Supply | Bequiet! Power Pro 12 1500w |
| Mouse | Lamzu Atlantis mini (White) |
| Keyboard | Monsgeek M3 Lavender, Akko Crystal Blues |
| VR HMD | Quest 3 |
| Software | Windows 11 |
| Benchmark Scores | I dont have time for that. |
Tonight was like any other. I came home cleaned the cat box started the dishes and re-heated some old pizza. I booted my PC and logged in. Ten minutes or so later my wife came home.
The back story is that for the life of my chrome has not been running correctly. What I thought was simply an under powered CPU I started to notice the lagginess in general.
My setup was as follows.
RAID 0 array with games and redirected user profile folders (music movies pictures etc). This array weighed in at 6TB and as an added bonus a 128GB ADATA SSD was used as cache.
Now continuing on with my story.
I was pretty sick of chrome jittering and thinking it might be related to my RAID I opened up Intel RST. The thought process was to start mitigating issues by disabling array cache so I could see if raw throughput helped the issue, maybe it was a bug with cacheing.
My wife has been interviewing internally at <big insurance> and today was one such event. I just so happened to have RST open when she walked into the room. She started explaining the process and her day and I became distracted. At this moment I misread the array CP and deactivated my main array.
My machine being linked via user profile to this array and the cache disk buffering that array immediately locked my system. After several minutes the machine started to respond and my heart was already sinking. RAID 0 failures in the industry are generally 100% data loss cases. I decided to try my luck.
Carefully I made sure no disk software was running and that I did not write or modify any contents. I disabled my Acceleration SSD and was careful NOT to reboot. I downloaded Testdisk and attempted to write back the partition scheme to see if I could get RST to redetect the array. However it would NOT. Thinking it was either.
A: RST config said this wasn't supposed to be an array so I wont see it
B: It was RAID 0 and it really is just gone.
I finally concluded a full destroy was in order. I opened up disk management and deleted and wiped all independent disks and rebuilt the array and cache.
The actual story begins
Up until this point I neglected to mention I keep backups. Attached via network share is a 8TB array living in my server that acts as my data dump. With Windows 10 and really windows in general a backup software is included. Now I am NOT blaming Windows 10 and on the contrary it may be a bug with all versions of the OS.
Now that is out of the way. I opened up my backup and restore panel. I rather like the new Windows 10 backup interface and I have had alot of success with Windows shadow copies in general since I have had to restore on my server before. I was ready for a nice experience. However after opening the panel I was greeted by the normal backup schedule disk selection and specified folder when I noticed an issue.
Even though my backup is scheduled to take place every hour for differencing the last backup date was 10/5. Angry but not terrible I click to start the restore, some is better than none. Thats when I started running into issues. The backup only saw 3 available files but indicated every directory. I double checked to make sure my drive letters were correct thinking the software was making a destination assumption and if my drives were wrong it would give me limited options. However everything appeared to be in order.
Frustrated and plagued by lack of time I dove head long into the issue disregarding pretty interfaces. I soon found out the problems went deeper. Via the options menu of the backup I saw that my entire drive was no longer on the list. Instead ONLY my user profile folders were shown. However this conflicted with the recovery console given that it could see the file structure just not restore.
Taking the red pill
With a backup and 2TB missing it was inconceivable for me to admit defeat so deeper into the rabbit hole I went. This time with control panels and pleasantly rude screens cast aside for the real deal. I accessed my network share and started looking at the backup structure raw. There I found my first clue. The backup name is reference by he PC name. However the PC name was NOT the same as my PC. In fact I remember changing my name shortly after the last build upgrade I received.
Moving along I stumbled across my data. However it was indeed only from the 5th and indeed was ONLY the user profile folders, which are incredibly important but still I was missing root level folders such as programs and other misc data. However after digging none could be found.
With the data digging complete I reluctantly started the manual transfer from my share to its proper location on my RAID array. the puzzle was still infuriating however and even deeper I went.
Show me yours
After the transfer began I opened event log and started cross checking references. I wanted to see if there were backup errors I was missing. However try as I might I could not for the life of me find any log indicating backups were failing unlike Server OSs which make it apparent, the logs for my backup just seemed to stop around 8PM on October 5th. Confused I looked in other sections in system and applications hoping I could find any reason why the backup feature would fail. After several minutes I found it, or rather THEM.
The log files generally hold some pretty basic information, regardless of issue or category type all logs generally hold your PC name. From shutdowns to updates to DCOM warning your machine name is a part of almost every log file windows generates. As I was digging for an error I found a pattern. On October 5th around quarter passed 7PM my logs showed a reboot and a name change. I like many others like adding personality to my machine and I remember renaming it before I needed to reboot for updates.
After that point in time my logs indicated the machine name change however my backups stopped working the following hour, with all the settings schedule and configuration intact the only clue was that the folder on the share in which my backups were held was named so after my computer before I renamed it.
I can only conclude given the evidence I found that Renaming your PC will break the backup procedure even if settings and config persist. However it is important to note I was not using the still available "Windows 7 backup" but the new Windows 10 backup via the "Settings" menu.
Moving forward I will be more vigilant with my backups since even those may not be safe and before it gets out of hand NO I am not interested in your thoughts of preferred backup software. I am well acquainted with mericum, Acronis, Paragon and god forbid backup exec and I may just switch too one of them again.
Check backups often and if you don't backup as I always have I recommend you look into it.
PS. she didn't get the position.
The back story is that for the life of my chrome has not been running correctly. What I thought was simply an under powered CPU I started to notice the lagginess in general.
My setup was as follows.
RAID 0 array with games and redirected user profile folders (music movies pictures etc). This array weighed in at 6TB and as an added bonus a 128GB ADATA SSD was used as cache.
Now continuing on with my story.
I was pretty sick of chrome jittering and thinking it might be related to my RAID I opened up Intel RST. The thought process was to start mitigating issues by disabling array cache so I could see if raw throughput helped the issue, maybe it was a bug with cacheing.
My wife has been interviewing internally at <big insurance> and today was one such event. I just so happened to have RST open when she walked into the room. She started explaining the process and her day and I became distracted. At this moment I misread the array CP and deactivated my main array.
My machine being linked via user profile to this array and the cache disk buffering that array immediately locked my system. After several minutes the machine started to respond and my heart was already sinking. RAID 0 failures in the industry are generally 100% data loss cases. I decided to try my luck.
Carefully I made sure no disk software was running and that I did not write or modify any contents. I disabled my Acceleration SSD and was careful NOT to reboot. I downloaded Testdisk and attempted to write back the partition scheme to see if I could get RST to redetect the array. However it would NOT. Thinking it was either.
A: RST config said this wasn't supposed to be an array so I wont see it
B: It was RAID 0 and it really is just gone.
I finally concluded a full destroy was in order. I opened up disk management and deleted and wiped all independent disks and rebuilt the array and cache.
The actual story begins
Up until this point I neglected to mention I keep backups. Attached via network share is a 8TB array living in my server that acts as my data dump. With Windows 10 and really windows in general a backup software is included. Now I am NOT blaming Windows 10 and on the contrary it may be a bug with all versions of the OS.
Now that is out of the way. I opened up my backup and restore panel. I rather like the new Windows 10 backup interface and I have had alot of success with Windows shadow copies in general since I have had to restore on my server before. I was ready for a nice experience. However after opening the panel I was greeted by the normal backup schedule disk selection and specified folder when I noticed an issue.
Even though my backup is scheduled to take place every hour for differencing the last backup date was 10/5. Angry but not terrible I click to start the restore, some is better than none. Thats when I started running into issues. The backup only saw 3 available files but indicated every directory. I double checked to make sure my drive letters were correct thinking the software was making a destination assumption and if my drives were wrong it would give me limited options. However everything appeared to be in order.
Frustrated and plagued by lack of time I dove head long into the issue disregarding pretty interfaces. I soon found out the problems went deeper. Via the options menu of the backup I saw that my entire drive was no longer on the list. Instead ONLY my user profile folders were shown. However this conflicted with the recovery console given that it could see the file structure just not restore.
Taking the red pill
With a backup and 2TB missing it was inconceivable for me to admit defeat so deeper into the rabbit hole I went. This time with control panels and pleasantly rude screens cast aside for the real deal. I accessed my network share and started looking at the backup structure raw. There I found my first clue. The backup name is reference by he PC name. However the PC name was NOT the same as my PC. In fact I remember changing my name shortly after the last build upgrade I received.
Moving along I stumbled across my data. However it was indeed only from the 5th and indeed was ONLY the user profile folders, which are incredibly important but still I was missing root level folders such as programs and other misc data. However after digging none could be found.
With the data digging complete I reluctantly started the manual transfer from my share to its proper location on my RAID array. the puzzle was still infuriating however and even deeper I went.
Show me yours
After the transfer began I opened event log and started cross checking references. I wanted to see if there were backup errors I was missing. However try as I might I could not for the life of me find any log indicating backups were failing unlike Server OSs which make it apparent, the logs for my backup just seemed to stop around 8PM on October 5th. Confused I looked in other sections in system and applications hoping I could find any reason why the backup feature would fail. After several minutes I found it, or rather THEM.
The log files generally hold some pretty basic information, regardless of issue or category type all logs generally hold your PC name. From shutdowns to updates to DCOM warning your machine name is a part of almost every log file windows generates. As I was digging for an error I found a pattern. On October 5th around quarter passed 7PM my logs showed a reboot and a name change. I like many others like adding personality to my machine and I remember renaming it before I needed to reboot for updates.
After that point in time my logs indicated the machine name change however my backups stopped working the following hour, with all the settings schedule and configuration intact the only clue was that the folder on the share in which my backups were held was named so after my computer before I renamed it.
I can only conclude given the evidence I found that Renaming your PC will break the backup procedure even if settings and config persist. However it is important to note I was not using the still available "Windows 7 backup" but the new Windows 10 backup via the "Settings" menu.
Moving forward I will be more vigilant with my backups since even those may not be safe and before it gets out of hand NO I am not interested in your thoughts of preferred backup software. I am well acquainted with mericum, Acronis, Paragon and god forbid backup exec and I may just switch too one of them again.
Check backups often and if you don't backup as I always have I recommend you look into it.
PS. she didn't get the position.
Last edited:
