diff options
| author | Fuwn <[email protected]> | 2024-06-19 03:35:10 -0700 |
|---|---|---|
| committer | Fuwn <[email protected]> | 2024-06-19 03:35:16 -0700 |
| commit | 030b1ca0718720d125b29ca522ad5b3d39398aef (patch) | |
| tree | 4ddf29c3e78d2efa8a484d52d40ee2ebf7d1044a | |
| parent | feat(the_daily): add reference to part 2. of nvme troubles in part 1. (diff) | |
| download | locus-030b1ca0718720d125b29ca522ad5b3d39398aef.tar.xz locus-030b1ca0718720d125b29ca522ad5b3d39398aef.zip | |
fix(the_daily): update self references
| -rw-r--r-- | content/blogs/the_daily/blog.json | 4 | ||||
| -rw-r--r-- | content/blogs/the_daily/nvme_troubles_part_2.gmi | 9 |
2 files changed, 5 insertions, 8 deletions
diff --git a/content/blogs/the_daily/blog.json b/content/blogs/the_daily/blog.json index 1d50e22..c246c52 100644 --- a/content/blogs/the_daily/blog.json +++ b/content/blogs/the_daily/blog.json @@ -5,14 +5,14 @@ "description": null, "author": "Fuwn", "created": "2024. 06. 17.", - "last_modified": "2024. 06. 17.", + "last_modified": "2024. 06. 19.", "name": "NVMe Troubles Part 1." }, "nvme_troubles_part_2": { "description": null, "author": "Fuwn", "created": "2024. 06. 17.", - "last_modified": "2024. 06. 17.", + "last_modified": "2024. 06. 19.", "name": "NVMe Troubles Part 2." } } diff --git a/content/blogs/the_daily/nvme_troubles_part_2.gmi b/content/blogs/the_daily/nvme_troubles_part_2.gmi index 394607d..9c32c6d 100644 --- a/content/blogs/the_daily/nvme_troubles_part_2.gmi +++ b/content/blogs/the_daily/nvme_troubles_part_2.gmi @@ -1,13 +1,10 @@ +=> /blog/the_daily/nvme_troubles_part_1 Previous on The Daily: NVMe Troubles Part 1. + # NVMe Troubles Part 2. OK! I've managed to boot back into my Btrfs filesystem. The bitrot (I guess) is still present, but I don't mind. I think I'll end up moving my secondary OS over from my primary NVMe to my secondary NVMe, then create a NixOS install in-place of that partition, clone my essential files over from my primary NVMe's Arch install, and then nuke the Arch (Btrfs) partition for good. -Previous blog post in question: - -=> /blog/the_daily/nvme_troubles_part_1 NVMe Troubles Part 1. - => https://i.imgur.com/5WiE6Xs.png - => https://i.imgur.com/nyJ2IPN.png ## Addendum @@ -24,7 +21,7 @@ At this point, I gave up, as both the information on Windows' system failure scr Fast-forward about a day. I'd like to play Wuthering Waves, so I have to boot into my Windows install. Windows still doesn't work, so I have to fix that. -I got around to flashing the AtlosOS installation media to a spare USB and getting into the troubleshooting menu, and after attempting the automatic rescue, a load of command-line tools, and more guides, still, nothing could bring back my system. My final resort was to try the System Restore functionality of Windows. +I got around to flashing the AtlasOS installation media to a spare USB and getting into the troubleshooting menu, and after attempting the automatic rescue, a load of command-line tools, and more guides, still, nothing could bring back my system. My final resort was to try the System Restore functionality of Windows. I'll preface this segment by outright stating that I have not once ever had a successful interaction with the System Restore feature. I've had two instances where a Windows installed potentially could have been saved by one, but in neither case did the System Restore either help, or even work due to the System Restore point itself being corrupt. In the past, I have disabled this feature from the first available moment, as to not waste my time and "drive space". |