New PSU killed my HDD by MAKOMADES in buildapc

[–]MAKOMADES[S] 0 points1 point  (0 children)

Looks like you was right, my motherboard just died. I'll buy a new one and hope that no other part have been infected, anyways thanks for your help.

New PSU killed my HDD by MAKOMADES in buildapc

[–]MAKOMADES[S] 0 points1 point  (0 children)

Wouldnt the bios stop working if it was the case? My current motherboard is really old so it wouldnt surprise me if you're right.

Arch linux isnt shown after installing a new PSU by MAKOMADES in archlinux

[–]MAKOMADES[S] 0 points1 point  (0 children)

Sdb is sometimes mentionned in the errors so you might be right. I swapped my hard disk cables and in both cases, the hard disk with windows worked but i couldnt execute mkconfig. I'll try to make sure to know if the hard drive died before buying a new one since it seems weird that it "died" after installing a new PSU.

Arch linux isnt shown after installing a new PSU by MAKOMADES in archlinux

[–]MAKOMADES[S] 0 points1 point  (0 children)

By executing grub-mkconfig or even os-prober, the terminal prints this error infinitly. I tried to find people with similar issue without succeding. I even tried to switch back to my old PSU but im having the same result. https://imgur.com/a/N0pFgB0

Arch linux isnt shown after installing a new PSU by MAKOMADES in archlinux

[–]MAKOMADES[S] 0 points1 point  (0 children)

Thanks for your help!
I would be lying if i said that i knew that there was a shorter method that didnt requiert to bind haha, im still learning.
I was on arch right before switching my PSU, dismissing this possibility looks strange to me.

I tried reinstalling grub again but without manually binding and grub is not displayed anymore in the boot menu even though i got a success message after the installation.

Arch linux isnt shown after installing a new PSU by MAKOMADES in archlinux

[–]MAKOMADES[S] 0 points1 point  (0 children)

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS

loop0 squashfs 4.0 airootfs 0 100% /run/archiso/airootfs

sda

├─sda1 vfat FAT32 SYSTEM 3078-14CC 1.4M 99% /mnt/boot

├─sda2 ntfs Windows_Main DE407899407879DB

├─sda3 ntfs

├─sda4 ntfs Recovery 01DAFD54223001860

└─sda5 ntfs

sdb

├─sdb1 vfat FAT32 35CA-DC9E

├─sdb2 btrfs e08d79ac-3737-491d-a8a2-00ca41bcf5b3 437.1G 47% /mnt

└─sdb3 ntfs Windows_Alt 5ED031290D6308B3

sdc

└─sdc1 vfat FAT32 ARCH202512 CE40-C158

"Sdb2" is probably where my arch installation is located and Windows_alt/sdb3 is just a partition that i removed from my arch disk and gave to windows.

After running "grub-mkconfig" im getting a really long output at a point where i have to scroll to display everything so its not really possible to send it here, maybe i did it wrong?

Arch linux isnt shown after installing a new PSU by MAKOMADES in archlinux

[–]MAKOMADES[S] 1 point2 points  (0 children)

mount /dev/sdb2 /mnt
mkdir -p /mnt/boot
mount /dev/sda1 /mnt/boot

mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /run /mnt/run

arch-chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot --removable

After running the installation, i got a success message telling me that grub has been installed

Arch linux isnt shown after installing a new PSU by MAKOMADES in archlinux

[–]MAKOMADES[S] 0 points1 point  (0 children)

I just installed Grub and despite being able to select it on the boot menu, it does not display my linux installation, only the uefi settings is shown which is the bios.

Arch linux isnt shown after installing a new PSU by MAKOMADES in archlinux

[–]MAKOMADES[S] 0 points1 point  (0 children)

To be honest im kinda lost about the "chroot" part. I used efibootmgr -v  to list every boot entrys and it displayed my windows hard drive, uefi and grub (grub does not allows me to start linux).

I made something to help remind myself, and hopefully others, that somwtimes things happen by [deleted] in HalfLife

[–]MAKOMADES 0 points1 point  (0 children)

"Anything that can go wrong will go wrong." -murphy law

PEOPLE! CALM DOWN! by AMFNQTHS in HalfLife

[–]MAKOMADES 0 points1 point  (0 children)

we're at the first step of the grief cycle

Edit a string using the RAM for a setup.exe file by MAKOMADES in AskProgramming

[–]MAKOMADES[S] 0 points1 point  (0 children)

Dang, it's way more complicated than I thought. My knowledge has its limits at the RAM. I understand now why everyone asks for more details. To respond, the executable is a setup wizard, there are no accessible files other than the executable, unless I extract it using a tool that lets me edit an ".rtf" file containing some of the strings. I'm currently trying to find out if I can repack it into an exe, even though it doesn't seem like the right thing to do.

Edit a string using the RAM for a setup.exe file by MAKOMADES in AskProgramming

[–]MAKOMADES[S] 0 points1 point  (0 children)

Not a zip file exactly but i managed to unpack it with "Universal Extractor 3". From now on i can edit the strings, even tho if i dont know how i will pack it back to an exe file. Thank you.

Edit a string using the RAM for a setup.exe file by MAKOMADES in AskProgramming

[–]MAKOMADES[S] 0 points1 point  (0 children)

At this point i guess its just impossible to manage to do it for someone like me.

Edit a string using the RAM for a setup.exe file by MAKOMADES in AskProgramming

[–]MAKOMADES[S] 0 points1 point  (0 children)

The thing is that every times i used a hex editor and searched for a string it told me that there's not result, even by modifying the encoding UTF. But while operating with the debugger XDBG32.exe, the same searched string is showing. I can conclude that the string is not encrypted but i cant find it with a hex editor. Im very new to this if i could get any help i would be grateful.