#15195 closed bug (duplicate)
Panic get boot partitions failed
| Reported by: | HAL | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | - General | Version: | R1/beta1 |
| Keywords: | boot, fails, kdl | Cc: | HAL |
| Blocked By: | #15330 | Blocking: | |
| Platform: | x86-64 |
Description
After updating to hrev53282 x86_64 and rebooting Haiku goes into KDL just after the middle icon. The summary of this bug is the first line of the KDL. If I reboot and select all the debug options it still does a KDL on next boot. Going back to my previous Haiku version hrev53233 x86_64, booting is good. I got a backtrace from KDL which I will upload from my camera when I reboot to Linux. I also got the old syslog that records the failed boot.
Attachments (10)
Change History (28)
by , 5 years ago
| Attachment: | previous_syslog added |
|---|
by , 5 years ago
| Attachment: | 100_1011.JPG added |
|---|
comment:1 by , 5 years ago
haiku-r1~beta1_hrev52295_129-1-x86_64.hpkg
Well, this is not a syslog from hrev53282. Are you sure you uploaded the right file?
comment:2 by , 5 years ago
No I am unsure of the update hrev version number. When I made the bug report I had booted into another Haiku beta1. How do I tell what version from the syslog of other mounted Haiku partition?
comment:3 by , 5 years ago
Well, without the syslog from the failed boot, we can't possibly determine what the bug is.
by , 5 years ago
| Attachment: | syslog.old added |
|---|
comment:4 by , 5 years ago
The hrev number in the report, I am uncertain that it was what I was testing. It was from Software Updater on the 21st July, yesterday. Where can I find the hrev from another Haiku mounted partition? I have just uploaded the syslog old. I hope that is the correct one.
comment:5 by , 5 years ago
This also contains no errors, the system appears to have booted successfully.
comment:6 by , 5 years ago
Well somehow I have lost the correct syslog. In debug settings the option to show previous boot syslog was checked.
comment:7 by , 5 years ago
I did a reboot to try and create a new syslog but none was created. It still went to KDL. Is that the reason no new syslog.
comment:9 by , 5 years ago
comment:10 by , 5 years ago
The images you attached do not contain a panic message. It looks like you entered "Display previous syslog" menu in the bootloader and took pics of it. Please provide pictures of syslog which end with panic.
comment:11 by , 5 years ago
I booted again until it KDL'd then typed syslog. I took pictures of all pages. There are 18. Do I attach them all or just the last?
comment:14 by , 5 years ago
At least we have some error now: KDiskDeviceManager::InitialDeviceScan() failed: Bad data
comment:15 by , 5 years ago
I think KDiskDeviceManager:InitialDeviceScan() failed: Bad data, is cause from updating the OS with Software Updater. Not necessarily from Software Updater itself but doing it this way instead of overwriting the Haiku install with the latest Haiku from USB stick. Just overwriting from USB stick, after install I can boot with no KDL at middle progress boot icon. This seems to be the common cure for quite a few problems of what seem like different bugs, that I cannot remember all, in the past. So is this a bug with Software Updater or indirectly stems from it? The "Bad data" is this some corruption caused when updating with SoftwareUpdater?
comment:16 by , 5 years ago
| Blocked By: | 15330 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Actually that error was also the cause of #15330, which was since fixed.
comment:17 by , 5 years ago
Why was my bug report here marked as duplicate when it was reported before #15330? I find with many of my reports marked duplicate when I have reported before the same bug.
comment:18 by , 5 years ago
Usually we close as duplicates in favor of the earliest opened, but if it is later discovered that an already-fixed issue has a still-open duplicate, we close it as a duplicate of the now-fixed bug, no matter older or newer.
backtrace