Boot issues for unknown reason?

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
oparilames
Level 1
Level 1
Posts: 23
Joined: Fri Apr 05, 2019 12:38 pm

Boot issues for unknown reason?

Post by oparilames » Sun Sep 15, 2019 7:06 pm

Hey guys, can someone help me with this?
I'm not very experienced and would like to boot again ...

Image

User avatar
Spearmint2
Level 16
Level 16
Posts: 6878
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Boot issues for unknown reason?

Post by Spearmint2 » Sun Sep 15, 2019 7:38 pm

All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

oparilames
Level 1
Level 1
Posts: 23
Joined: Fri Apr 05, 2019 12:38 pm

Re: Boot issues for unknown reason?

Post by oparilames » Sun Sep 15, 2019 8:30 pm

Still get the message.

Couldn't get size: 0xB00...e
MODSIGN: Couldn't get UEFI dB list
[drm:construct [amdpgu]] *ERROR* construct: Invalid Connector Object from Adapter Service for connector index:1! Type 0 expected 3
drm:construct [amdpgu]] *ERROR* construct: Invalid Connector Object from Adapter Service for connector index:2! Type 0 expected 3
drm:construct [amdpgu]] *ERROR* construct: Invalid Connector Object from Adapter Service for connector index:3! Type 0 expected 3
kdf kdf: error getting iommu info. Is the iommu enabled?
kdf kdf: Error initializing iommuv2
kdf kdf: device 1002:15d8 NOT added due to errors



My system was working. But before this appeared I had trouble accessing my internal SSD. It told me it were only readable which was really odd because 5 minutes ago I was using the system normal. But then, when I came back from a break and wanted to save I file I got this strange message.

User avatar
Spearmint2
Level 16
Level 16
Posts: 6878
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Boot issues for unknown reason?

Post by Spearmint2 » Sun Sep 15, 2019 8:45 pm

maybe something is wrong with the SSD drive. It can't see it's size, can't access in the UEFI (EFI Partition on drive?)
I don't think there's anything I can do about it, other than suggest to boot a LIVE Mint DVD and see if it can access the SSD and view files on it.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

oparilames
Level 1
Level 1
Posts: 23
Joined: Fri Apr 05, 2019 12:38 pm

Re: Boot issues for unknown reason?

Post by oparilames » Tue Sep 17, 2019 6:06 am

So I started from a live USB flash drive and it worked. I was also able to open files in my home directory on the SSD. I was also able to create, edit and load a text file on my SSD´s desktop directory.
Strangely when I tried to use time shift to recover and old backup it said everything went fine but the error persists.
System.png
Here is my /var/boot.log

I know about the strange identifier for the partitions but it was ever since I have this machine.

User avatar
Spearmint2
Level 16
Level 16
Posts: 6878
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Boot issues for unknown reason?

Post by Spearmint2 » Tue Sep 17, 2019 11:12 am

Did you chance something in the BIOS? Has your date/time settings changed by themselves recently, indicating a loss of power to motherboard's BIOS battery, the CR2032 coin battery? From what I see for similar messages, it seems some virtualization switch in the BIOS changed.

https://us.informatiweb.net/tutorials/i ... -bios.html

https://itstillworks.com/how-to-enable- ... 10392.html

This doesn't look promising. Having the odd "orphaned inode" on your storage device (drive) isn't too bad, but this seems excessive.
It then does it again later, probably newer orphaned inodes.

Maybe running fsck on the drive will clear up the inodes.

http://www.linux-kvm.org/page/How_to_as ... T-d_in_KVM



/dev/nvme0n1p5: recovering journal
/dev/nvme0n1p5: Clearing orphaned inode 920278 (uid=0, gid=0, mode=040700, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920279 (uid=0, gid=0, mode=041777, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920306 (uid=0, gid=0, mode=040700, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920307 (uid=0, gid=0, mode=041777, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920302 (uid=0, gid=0, mode=040700, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920303 (uid=0, gid=0, mode=041777, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920276 (uid=0, gid=0, mode=040700, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920277 (uid=0, gid=0, mode=041777, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920274 (uid=0, gid=0, mode=040700, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 920275 (uid=0, gid=0, mode=041777, size=4096)
/dev/nvme0n1p5: Clearing orphaned inode 6426446 (uid=0, gid=0, mode=0100600, size=0)
/dev/nvme0n1p5: Clearing orphaned inode 6426445 (uid=0, gid=0, mode=0100600, size=65536)
/dev/nvme0n1p5: Clearing orphaned inode 8913963 (uid=1000, gid=1000, mode=0100644, size=32768)
/dev/nvme0n1p5: Clearing orphaned inode 262946 (uid=7, gid=7, mode=0100600, size=0)
/dev/nvme0n1p5: Clearing orphaned inode 270775 (uid=0, gid=0, mode=0100600, size=21238)
/dev/nvme0n1p5: Clearing orphaned inode 270773 (uid=0, gid=0, mode=0100600, size=75098)
/dev/nvme0n1p5: Clearing orphaned inode 270760 (uid=0, gid=4, mode=0100640, size=6145)
/dev/nvme0n1p5: Clearing orphaned inode 270526 (uid=102, gid=4, mode=0100640, size=10092585)
/dev/nvme0n1p5: Clearing orphaned inode 270527 (uid=102, gid=4, mode=0100640, size=1245995)
/dev/nvme0n1p5: Clearing orphaned inode 270619 (uid=102, gid=4, mode=0100640, size=55729)
/dev/nvme0n1p5: Clearing orphaned inode 262525 (uid=0, gid=0, mode=0100644, size=35815)
/dev/nvme0n1p5: Clearing orphaned inode 8913775 (uid=1000, gid=1000, mode=0100600, size=340)
/dev/nvme0n1p5: Clearing orphaned inode 8914266 (uid=1000, gid=1000, mode=0100644, size=5037)
/dev/nvme0n1p5: Clearing orphaned inode 8912919 (uid=1000, gid=1000, mode=0100600, size=9384)
/dev/nvme0n1p5: Clearing orphaned inode 14811144 (uid=0, gid=0, mode=0100600, size=2)
/dev/nvme0n1p5: Clearing orphaned inode 14812646 (uid=0, gid=0, mode=0100644, size=1212)
/dev/nvme0n1p5: Clearing orphaned inode 8913773 (uid=1000, gid=1000, mode=0100644, size=5037)
/dev/nvme0n1p5: Clearing orphaned inode 8913018 (uid=1000, gid=1000, mode=0100644, size=5037)
/dev/nvme0n1p5: Clearing orphaned inode 8916615 (uid=1000, gid=1000, mode=0100644, size=5037)
/dev/nvme0n1p5: Clearing orphaned inode 6422541 (uid=0, gid=0, mode=0100600, size=0)
/dev/nvme0n1p5: clean, 747091/17367040 files, 6569964/69468160 blocks

then later in logs;
Didn't it already do this?!


Starting Hold until boot process finishes up...
Starting Light Display Manager...
[[0;32m OK [0m] Started Login Service.
/dev/nvme0n1p5: recovering journal
/dev/nvme0n1p5: Clearing orphaned inode 6426459 (uid=0, gid=0, mode=0100600, size=0)
/dev/nvme0n1p5: Clearing orphaned inode 6426453 (uid=0, gid=0, mode=0100600, size=65536)
/dev/nvme0n1p5: Clearing orphaned inode 8917697 (uid=1000, gid=1000, mode=0100644, size=32768)
/dev/nvme0n1p5: Clearing orphaned inode 8916921 (uid=1000, gid=1000, mode=0100600, size=268)
/dev/nvme0n1p5: Clearing orphaned inode 8917632 (uid=1000, gid=1000, mode=0100644, size=32768)
/dev/nvme0n1p5: Clearing orphaned inode 262517 (uid=0, gid=4, mode=0100640, size=4639)
/dev/nvme0n1p5: Clearing orphaned inode 264202 (uid=102, gid=4, mode=0100640, size=9932800)
/dev/nvme0n1p5: Clearing orphaned inode 264125 (uid=102, gid=4, mode=0100640, size=1204224)
/dev/nvme0n1p5: Clearing orphaned inode 262563 (uid=102, gid=4, mode=0100640, size=56481)
/dev/nvme0n1p5: Clearing orphaned inode 13762578 (uid=0, gid=0, mode=0100644, size=30560)
/dev/nvme0n1p5: Clearing orphaned inode 8917520 (uid=1000, gid=1000, mode=0100600, size=712)
/dev/nvme0n1p5: Clearing orphaned inode 8912942 (uid=1000, gid=1000, mode=0100644, size=12288)
/dev/nvme0n1p5: Clearing orphaned inode 8916052 (uid=1000, gid=1000, mode=0100644, size=5955)
/dev/nvme0n1p5: Clearing orphaned inode 8912945 (uid=1000, gid=1000, mode=0100600, size=18089)
/dev/nvme0n1p5: Clearing orphaned inode 8917065 (uid=1000, gid=1000, mode=0100644, size=5880)
/dev/nvme0n1p5: Clearing orphaned inode 8913072 (uid=1000, gid=1000, mode=0100644, size=5264)
/dev/nvme0n1p5: Clearing orphaned inode 13762574 (uid=0, gid=0, mode=0100644, size=30536)
/dev/nvme0n1p5: Clearing orphaned inode 12464653 (uid=0, gid=0, mode=0100644, size=279334)
/dev/nvme0n1p5: Clearing orphaned inode 8914266 (uid=1000, gid=1000, mode=0100644, size=5264)
/dev/nvme0n1p5: Clearing orphaned inode 8914309 (uid=1000, gid=1000, mode=0100644, size=32768)
/dev/nvme0n1p5: Clearing orphaned inode 8913859 (uid=1000, gid=1000, mode=0100600, size=340)
/dev/nvme0n1p5: Clearing orphaned inode 8913077 (uid=1000, gid=1000, mode=0100644, size=5037)
/dev/nvme0n1p5: Clearing orphaned inode 8913079 (uid=1000, gid=1000, mode=0100644, size=5037)
/dev/nvme0n1p5: Clearing orphaned inode 8912948 (uid=1000, gid=1000, mode=0100644, size=5037)
/dev/nvme0n1p5: clean, 753658/17367040 files, 6780937/69468160 blocks
[[0;32m OK [0m] Started Load/Save RF Kill Switch Status.
[[0;32m OK [0m] Started Show Plymouth Boot Screen.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

oparilames
Level 1
Level 1
Posts: 23
Joined: Fri Apr 05, 2019 12:38 pm

Re: Boot issues for unknown reason?

Post by oparilames » Tue Sep 17, 2019 1:11 pm

I remember there was an BIOS update quiet recently.
Thank you for your answer. I gonna try this.

Could it be a problem to use an adaptor to fit the battery charger into the socket? (EU to UK)

User avatar
Spearmint2
Level 16
Level 16
Posts: 6878
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: Boot issues for unknown reason?

Post by Spearmint2 » Tue Sep 17, 2019 1:26 pm

Could it be a problem to use an adaptor to fit the battery charger into the socket? (EU to UK)
I have no idea about that. When I lived 3 years in Greece they used 220v and I used a transformer to convert to USA 110, but the cycles were still 50 instead of 60. We had no real problems with lower cycles though for most uses, including the TV, but TV was also "overseas" model that did PAL, Secam, and some other, and had inbuilt transformers, so again, l Have no certain knowledge of the current situation since I was there in the 80's.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

Post Reply

Return to “Installation & Boot”