・ Occurrence of cause When I installed the software that is Windows, the menu "Register for Windows service" appeared. Since the PC is under Active Directory, it says "Enter the password of an authorized user". Even though I entered the root password, it failed and was not accepted. From there, anomalies begin to appear. When I reboot and try to enter the password "Failed to trust this workstation with the primary domain" </ b> Display with. I can't even log in to Windows.
"Now I'm in trouble"
For the time being, I decided to rescue the necessary data via Linux.
・ Symptoms That's why Linux, which was loaded on USB, comes into play. (OS: Tails 4.12) I started Tails with USB and tried to look into the Windows HDD (sda2) from there, but at that time, the message Authentication Required appeared and I could not look into the Windows HDD ...! !!
After struggling for about 30 minutes, I was able to rescue the data safely, so I will write down how to do it.
·Solution
Press F2 on the boot screen (it may be F10 or F11 depending on the PC, press the start button and check the screen that appears for a moment) to the Tails startup screen.
On the "Welcome screen" when Tails opens, you can optionally set a root password, so set the password appropriately.
Under [Home]-[Persistent], create a text file with the following contents and save it as 10-local.rules.
10-local.rules
KERNEL=="sda2", ENV{UDISKS_IGNORE}="1"
KERNEL=="sdb2", ENV{UDISKS_IGNORE}="1"
KERNEL=="sdc1", ENV{UDISKS_IGNORE}="1"
(The name sda2 or sdb2 will differ depending on the person's situation, so please specify the name of the HDD you want to open.) The reason for saving it under Persistent is to keep it even if the power is turned off and restarted. (I'm talking about this assuming you've already created a Persistent Volume on Tails OS on USB)
Start [System Tools]-[Terminal] and type `` `sudo -i```. A password will be required. Enter the password set in step 3 to acquire root privileges!
In the terminal, move the text file created in 4. to the system area (directly under /etc/udev/rules.d </ b>).
mv /home/amnesia/Persistent/10-local.rules /etc/udev/rules.d
(The full path of the file you want to move mv The syntax you want to move is ``)
Press Enter and 10-local.rules should have moved from /home/amnesia/Persistent/ to /etc/udev/rules.d. (If you don't have root authority, you can't read or write to the system area, so I'm doing this purposely)
When 10-local.rules moves to the system area, you will be able to access the HDD that was rejected as Authentication Required </ b>.
Attach another external USB, copy all the contents of the HDD you want to save there, and finish!
Congratulations, congratulations: relaxed:
·point By writing the command "Read all HDDs!" In the Linux system area, access is forcibly enabled.
Does security come in if Active Directory is included? When I was excited to say, "There is USB Linux, come on, rescue me", but when I was hit by Authentication Required, I felt hopeless: tired_face:
Even in such a case, it can be said that it is a very useful technique when forcibly looking into the HDD and rescuing data. I can say with confidence.
Without this, I was at a loss.
However, if the HDD is physically damaged, this is not possible. But when you just can't log in due to a software error, like I've just experienced, you're the last savior.
The trust relationship of the domain is restored safely by copying the backup that was taken once a month as it is with the HDD </ b>. After that, write only the latest rescued data and the recovery is completed. (HDD backup for each OS shows its true value in such cases)
I rarely get these critical errors, but when I do, I'm terribly confused and upset. At that point, you won't be able to use your computer anymore.
It has become one of the most important techniques in my work.
As a memorandum, I will write it down.
Recommended Posts