A TPM error (7) occurred attempting to read a pcr value
up vote
7
down vote
favorite
I had tried a command (I do not remember it) with the terminal of Ubuntu, and the computer shut down. Now when I boot it, it says :-
[ 4.562057] ACPI PCC probe failed.
[ 4.615205 tpm_tis 00:05: A TPM error (7) occurred attempting to read a pcr value
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootargw
Busybox v1.21.1 (ubuntu 1:1.21.0-1ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(Initramfs)
boot init
add a comment |
up vote
7
down vote
favorite
I had tried a command (I do not remember it) with the terminal of Ubuntu, and the computer shut down. Now when I boot it, it says :-
[ 4.562057] ACPI PCC probe failed.
[ 4.615205 tpm_tis 00:05: A TPM error (7) occurred attempting to read a pcr value
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootargw
Busybox v1.21.1 (ubuntu 1:1.21.0-1ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(Initramfs)
boot init
similar question (same error message) addressed in http://unix.stackexchange.com/questions/305719/a-tpm-error-7-occurred-attempting-to-read-a-pcr-value-in-centos
– Bryan Crosby
Feb 15 '17 at 6:02
I had the same issue and just throw an answer here.
– pa4080
Jun 2 '17 at 9:13
add a comment |
up vote
7
down vote
favorite
up vote
7
down vote
favorite
I had tried a command (I do not remember it) with the terminal of Ubuntu, and the computer shut down. Now when I boot it, it says :-
[ 4.562057] ACPI PCC probe failed.
[ 4.615205 tpm_tis 00:05: A TPM error (7) occurred attempting to read a pcr value
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootargw
Busybox v1.21.1 (ubuntu 1:1.21.0-1ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(Initramfs)
boot init
I had tried a command (I do not remember it) with the terminal of Ubuntu, and the computer shut down. Now when I boot it, it says :-
[ 4.562057] ACPI PCC probe failed.
[ 4.615205 tpm_tis 00:05: A TPM error (7) occurred attempting to read a pcr value
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootargw
Busybox v1.21.1 (ubuntu 1:1.21.0-1ubuntu1) built in shell (ash)
Enter 'help' for a list of built-in commands.
(Initramfs)
boot init
boot init
edited Nov 21 '16 at 17:27
Gautam Vashisht
1,79011120
1,79011120
asked Nov 21 '16 at 16:15
G. Hansel
36113
36113
similar question (same error message) addressed in http://unix.stackexchange.com/questions/305719/a-tpm-error-7-occurred-attempting-to-read-a-pcr-value-in-centos
– Bryan Crosby
Feb 15 '17 at 6:02
I had the same issue and just throw an answer here.
– pa4080
Jun 2 '17 at 9:13
add a comment |
similar question (same error message) addressed in http://unix.stackexchange.com/questions/305719/a-tpm-error-7-occurred-attempting-to-read-a-pcr-value-in-centos
– Bryan Crosby
Feb 15 '17 at 6:02
I had the same issue and just throw an answer here.
– pa4080
Jun 2 '17 at 9:13
similar question (same error message) addressed in http://unix.stackexchange.com/questions/305719/a-tpm-error-7-occurred-attempting-to-read-a-pcr-value-in-centos
– Bryan Crosby
Feb 15 '17 at 6:02
similar question (same error message) addressed in http://unix.stackexchange.com/questions/305719/a-tpm-error-7-occurred-attempting-to-read-a-pcr-value-in-centos
– Bryan Crosby
Feb 15 '17 at 6:02
I had the same issue and just throw an answer here.
– pa4080
Jun 2 '17 at 9:13
I had the same issue and just throw an answer here.
– pa4080
Jun 2 '17 at 9:13
add a comment |
3 Answers
3
active
oldest
votes
up vote
3
down vote
I got this error and it was because I had two hard drive with the same UUID.
The error I got on boot up was:
A TPM error (7) occurred attempting to read a pcr value
I went searching the BIOS, nonmodeset
on kernel line, etc because the error message was not very informative.
To see if you have this issue, boot to a command prompt and issue:
blkid -o list
and see if you have UUID's that are the same.
Apparently what I had done was clone a partition and forgot to reset the UUID.
You need to check the file system and then set the UUID - here is an example:
fsck -y /dev/sda1
tune2fs /dev/sda1 -U cfe9f84d-a454-4e46-97bb-6f1f18fcb427
WOW. What are the chances?
– Nonny Moose
Nov 17 at 0:49
add a comment |
up vote
2
down vote
First of all TPM is:
Trusted Platform Module (TPM) is an international standard for a
secure cryptoprocessor, which is a dedicated microprocessor designed
to secure hardware by integrating cryptographic keys into devices.
In practice a TPM can be used for various different security
applications such as secure boot and key storage.
TPM is naturally supported only on devices that have TPM hardware
support. If your hardware has TPM support but it is not showing up, it
might need to be enabled in the BIOS settings.
1. So if you do not need use the TPM feature you can disable it via the BIOS settings. I have a machine with Phoenix BIOS and these settings are placed within the Security section.
2. Also you can ignore the TPM feature through the Ubuntu settings. Just type this command:
echo "blacklist tpm_tis" | sudo tee -a /etc/modprobe.d/tpm_tis.conf
Where the command tee -a
will append the echoed line (blacklist tpm_tis
) into the end of /etc/modprobe.d/tpm_tis.conf
or will create the file if it's doesn't exists.
3. Sources and other solutions:
- ArchWiki: Trusted Platform Module
- A TPM error (6) occurred attempting to read a pcr value
- A tpm error (7) occurred attempting to read a pcr value in centos
add a comment |
up vote
0
down vote
This error can be corrected as follows. It occurs when there is an error in the superblocks of the hard disk. Boot with a live CD or bootable USB with any Linux distribution, you can use KDE Partition Manager or GParted. Check and repair the partitions you have, executing the following command; e2fsck -f -y -v /dev/sdX
(replace X with the desired partition letter). Reboot with sudo reboot
.
New contributor
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
I got this error and it was because I had two hard drive with the same UUID.
The error I got on boot up was:
A TPM error (7) occurred attempting to read a pcr value
I went searching the BIOS, nonmodeset
on kernel line, etc because the error message was not very informative.
To see if you have this issue, boot to a command prompt and issue:
blkid -o list
and see if you have UUID's that are the same.
Apparently what I had done was clone a partition and forgot to reset the UUID.
You need to check the file system and then set the UUID - here is an example:
fsck -y /dev/sda1
tune2fs /dev/sda1 -U cfe9f84d-a454-4e46-97bb-6f1f18fcb427
WOW. What are the chances?
– Nonny Moose
Nov 17 at 0:49
add a comment |
up vote
3
down vote
I got this error and it was because I had two hard drive with the same UUID.
The error I got on boot up was:
A TPM error (7) occurred attempting to read a pcr value
I went searching the BIOS, nonmodeset
on kernel line, etc because the error message was not very informative.
To see if you have this issue, boot to a command prompt and issue:
blkid -o list
and see if you have UUID's that are the same.
Apparently what I had done was clone a partition and forgot to reset the UUID.
You need to check the file system and then set the UUID - here is an example:
fsck -y /dev/sda1
tune2fs /dev/sda1 -U cfe9f84d-a454-4e46-97bb-6f1f18fcb427
WOW. What are the chances?
– Nonny Moose
Nov 17 at 0:49
add a comment |
up vote
3
down vote
up vote
3
down vote
I got this error and it was because I had two hard drive with the same UUID.
The error I got on boot up was:
A TPM error (7) occurred attempting to read a pcr value
I went searching the BIOS, nonmodeset
on kernel line, etc because the error message was not very informative.
To see if you have this issue, boot to a command prompt and issue:
blkid -o list
and see if you have UUID's that are the same.
Apparently what I had done was clone a partition and forgot to reset the UUID.
You need to check the file system and then set the UUID - here is an example:
fsck -y /dev/sda1
tune2fs /dev/sda1 -U cfe9f84d-a454-4e46-97bb-6f1f18fcb427
I got this error and it was because I had two hard drive with the same UUID.
The error I got on boot up was:
A TPM error (7) occurred attempting to read a pcr value
I went searching the BIOS, nonmodeset
on kernel line, etc because the error message was not very informative.
To see if you have this issue, boot to a command prompt and issue:
blkid -o list
and see if you have UUID's that are the same.
Apparently what I had done was clone a partition and forgot to reset the UUID.
You need to check the file system and then set the UUID - here is an example:
fsck -y /dev/sda1
tune2fs /dev/sda1 -U cfe9f84d-a454-4e46-97bb-6f1f18fcb427
edited Oct 10 '17 at 12:07
answered Oct 9 '17 at 19:00
Carl Moser
312
312
WOW. What are the chances?
– Nonny Moose
Nov 17 at 0:49
add a comment |
WOW. What are the chances?
– Nonny Moose
Nov 17 at 0:49
WOW. What are the chances?
– Nonny Moose
Nov 17 at 0:49
WOW. What are the chances?
– Nonny Moose
Nov 17 at 0:49
add a comment |
up vote
2
down vote
First of all TPM is:
Trusted Platform Module (TPM) is an international standard for a
secure cryptoprocessor, which is a dedicated microprocessor designed
to secure hardware by integrating cryptographic keys into devices.
In practice a TPM can be used for various different security
applications such as secure boot and key storage.
TPM is naturally supported only on devices that have TPM hardware
support. If your hardware has TPM support but it is not showing up, it
might need to be enabled in the BIOS settings.
1. So if you do not need use the TPM feature you can disable it via the BIOS settings. I have a machine with Phoenix BIOS and these settings are placed within the Security section.
2. Also you can ignore the TPM feature through the Ubuntu settings. Just type this command:
echo "blacklist tpm_tis" | sudo tee -a /etc/modprobe.d/tpm_tis.conf
Where the command tee -a
will append the echoed line (blacklist tpm_tis
) into the end of /etc/modprobe.d/tpm_tis.conf
or will create the file if it's doesn't exists.
3. Sources and other solutions:
- ArchWiki: Trusted Platform Module
- A TPM error (6) occurred attempting to read a pcr value
- A tpm error (7) occurred attempting to read a pcr value in centos
add a comment |
up vote
2
down vote
First of all TPM is:
Trusted Platform Module (TPM) is an international standard for a
secure cryptoprocessor, which is a dedicated microprocessor designed
to secure hardware by integrating cryptographic keys into devices.
In practice a TPM can be used for various different security
applications such as secure boot and key storage.
TPM is naturally supported only on devices that have TPM hardware
support. If your hardware has TPM support but it is not showing up, it
might need to be enabled in the BIOS settings.
1. So if you do not need use the TPM feature you can disable it via the BIOS settings. I have a machine with Phoenix BIOS and these settings are placed within the Security section.
2. Also you can ignore the TPM feature through the Ubuntu settings. Just type this command:
echo "blacklist tpm_tis" | sudo tee -a /etc/modprobe.d/tpm_tis.conf
Where the command tee -a
will append the echoed line (blacklist tpm_tis
) into the end of /etc/modprobe.d/tpm_tis.conf
or will create the file if it's doesn't exists.
3. Sources and other solutions:
- ArchWiki: Trusted Platform Module
- A TPM error (6) occurred attempting to read a pcr value
- A tpm error (7) occurred attempting to read a pcr value in centos
add a comment |
up vote
2
down vote
up vote
2
down vote
First of all TPM is:
Trusted Platform Module (TPM) is an international standard for a
secure cryptoprocessor, which is a dedicated microprocessor designed
to secure hardware by integrating cryptographic keys into devices.
In practice a TPM can be used for various different security
applications such as secure boot and key storage.
TPM is naturally supported only on devices that have TPM hardware
support. If your hardware has TPM support but it is not showing up, it
might need to be enabled in the BIOS settings.
1. So if you do not need use the TPM feature you can disable it via the BIOS settings. I have a machine with Phoenix BIOS and these settings are placed within the Security section.
2. Also you can ignore the TPM feature through the Ubuntu settings. Just type this command:
echo "blacklist tpm_tis" | sudo tee -a /etc/modprobe.d/tpm_tis.conf
Where the command tee -a
will append the echoed line (blacklist tpm_tis
) into the end of /etc/modprobe.d/tpm_tis.conf
or will create the file if it's doesn't exists.
3. Sources and other solutions:
- ArchWiki: Trusted Platform Module
- A TPM error (6) occurred attempting to read a pcr value
- A tpm error (7) occurred attempting to read a pcr value in centos
First of all TPM is:
Trusted Platform Module (TPM) is an international standard for a
secure cryptoprocessor, which is a dedicated microprocessor designed
to secure hardware by integrating cryptographic keys into devices.
In practice a TPM can be used for various different security
applications such as secure boot and key storage.
TPM is naturally supported only on devices that have TPM hardware
support. If your hardware has TPM support but it is not showing up, it
might need to be enabled in the BIOS settings.
1. So if you do not need use the TPM feature you can disable it via the BIOS settings. I have a machine with Phoenix BIOS and these settings are placed within the Security section.
2. Also you can ignore the TPM feature through the Ubuntu settings. Just type this command:
echo "blacklist tpm_tis" | sudo tee -a /etc/modprobe.d/tpm_tis.conf
Where the command tee -a
will append the echoed line (blacklist tpm_tis
) into the end of /etc/modprobe.d/tpm_tis.conf
or will create the file if it's doesn't exists.
3. Sources and other solutions:
- ArchWiki: Trusted Platform Module
- A TPM error (6) occurred attempting to read a pcr value
- A tpm error (7) occurred attempting to read a pcr value in centos
answered Jun 2 '17 at 9:08
pa4080
12.7k52359
12.7k52359
add a comment |
add a comment |
up vote
0
down vote
This error can be corrected as follows. It occurs when there is an error in the superblocks of the hard disk. Boot with a live CD or bootable USB with any Linux distribution, you can use KDE Partition Manager or GParted. Check and repair the partitions you have, executing the following command; e2fsck -f -y -v /dev/sdX
(replace X with the desired partition letter). Reboot with sudo reboot
.
New contributor
add a comment |
up vote
0
down vote
This error can be corrected as follows. It occurs when there is an error in the superblocks of the hard disk. Boot with a live CD or bootable USB with any Linux distribution, you can use KDE Partition Manager or GParted. Check and repair the partitions you have, executing the following command; e2fsck -f -y -v /dev/sdX
(replace X with the desired partition letter). Reboot with sudo reboot
.
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
This error can be corrected as follows. It occurs when there is an error in the superblocks of the hard disk. Boot with a live CD or bootable USB with any Linux distribution, you can use KDE Partition Manager or GParted. Check and repair the partitions you have, executing the following command; e2fsck -f -y -v /dev/sdX
(replace X with the desired partition letter). Reboot with sudo reboot
.
New contributor
This error can be corrected as follows. It occurs when there is an error in the superblocks of the hard disk. Boot with a live CD or bootable USB with any Linux distribution, you can use KDE Partition Manager or GParted. Check and repair the partitions you have, executing the following command; e2fsck -f -y -v /dev/sdX
(replace X with the desired partition letter). Reboot with sudo reboot
.
New contributor
edited Nov 17 at 0:47
karel
54.7k11119138
54.7k11119138
New contributor
answered Nov 16 at 23:05
Elvis
1
1
New contributor
New contributor
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f851975%2fa-tpm-error-7-occurred-attempting-to-read-a-pcr-value%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
similar question (same error message) addressed in http://unix.stackexchange.com/questions/305719/a-tpm-error-7-occurred-attempting-to-read-a-pcr-value-in-centos
– Bryan Crosby
Feb 15 '17 at 6:02
I had the same issue and just throw an answer here.
– pa4080
Jun 2 '17 at 9:13