Opened 2 years ago
Closed 2 years ago
#17958 closed bug (fixed)
DriveSetup and checkfs /boot - bad work
Reported by: | kim1963 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta4 |
Component: | Kits/Storage Kit | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
https://discuss.haiku-os.org/t/drivesetup-and-checkfs-boot-bad-work/12517
DiskDeviceJobQueue::Execute(): executing job: N8BPrivate12SetStringJobE
DiskDeviceJobQueue::Execute(): executing job failed: Operation not supported
Attachments (8)
Change History (19)
comment:1 by , 2 years ago
by , 2 years ago
Attachment: | photo_2022-09-27_14-30-42.jpg added |
---|
by , 2 years ago
Attachment: | screenshot423.png added |
---|
by , 2 years ago
Attachment: | screenshot428.png added |
---|
comment:2 by , 2 years ago
The bug is reproduced on any night build 64 bits after updating packages - see the screenshot423.
follow-up: 4 comment:3 by , 2 years ago
again: please include information about what the issue is, how you reproduce it, what your haiku revision is etc.
I have no idea what your screenshots are supposed to show
comment:4 by , 2 years ago
Replying to nephele:
again: please include information about what the issue is, how you reproduce it, what your haiku revision is etc.
I have no idea what your screenshots are supposed to show
hrev 56465 and 56475 and 56480 -
Welcome to the Haiku shell.
~> uname -a Haiku shredderNEW 1 hrev56480 Sep 27 2022 06:06:40 x86_64 x86_64 Haiku ~> checkfs /boot
88500 nodes checked, 0 blocks not allocated, 0 blocks already set, 0 blocks could be freed
files 79831 directories 6305 attributes 1320 attr. dirs 1000 indices 44
direct block runs 105942 (77.77 ГБ) indirect block runs 19039 (in 770 array blocks, 36.94 ГБ) double indirect block runs 9952 (in 15 array blocks, 38.88 МБ)
DiskDeviceJobQueue::Execute(): executing job: N8BPrivate12SetStringJobE DiskDeviceJobQueue::Execute(): executing job failed: Operation not supported ~>
by , 2 years ago
Attachment: | screenshot438.png added |
---|
comment:5 by , 2 years ago
Description: | modified (diff) |
---|
follow-up: 7 comment:6 by , 2 years ago
Component: | - General → Kits/Storage Kit |
---|
Probably a consequence of https://cgit.haiku-os.org/haiku/commit/?id=e3d5904751dc8285b14e25ed815aeb6637f8d944
Could you please provide a syslog with the kernel file systems scan?
by , 2 years ago
Attachment: | screenshot441.png added |
---|
comment:7 by , 2 years ago
Replying to korli:
Probably a consequence of https://cgit.haiku-os.org/haiku/commit/?id=e3d5904751dc8285b14e25ed815aeb6637f8d944
Could you please provide a syslog with the kernel file systems scan?
hrev56460 work fine
by , 2 years ago
Attachment: | syslog56460.txt added |
---|
by , 2 years ago
Attachment: | syslog56480.txt added |
---|
comment:8 by , 2 years ago
Thanks. It looks like the intel map has no name, and this is a BPartition too. Checking BPartition::ContainsFileSystem() might be an idea.
742 KERN: device 0: /dev/disk/nvme/0/raw 743 KERN: media status: No error 744 KERN: device flags: 2 745 KERN: offset: 0 746 KERN: size: 250059350016 (238475.179 MB) 747 KERN: content size: 250059350016 748 KERN: block size: 512 749 KERN: physical block size: 512 750 KERN: child count: 1 751 KERN: index: -1 752 KERN: status: 0 753 KERN: flags: 5 754 KERN: volume: -1 755 KERN: disk system: partitioning_systems/intel/map/v1 756 KERN: name: <NULL> 757 KERN: content name: <NULL> 758 KERN: type: <NULL> 759 KERN: content type: Intel Partition Map 760 KERN: params: <NULL> 761 KERN: content params: <NULL> 762 KERN: partition 1: /dev/disk/nvme/0/0 763 KERN: offset: 32768 764 KERN: size: 250059161600 (238475 MB) 765 KERN: content size: 250059161600 766 KERN: block size: 2048 767 KERN: physical block size: 512 768 KERN: child count: 0 769 KERN: index: 0 770 KERN: status: 0 771 KERN: flags: 2 772 KERN: volume: -1 773 KERN: disk system: file_systems/bfs/v1 774 KERN: name: <NULL> 775 KERN: content name: HaikuNVME 776 KERN: type: Be File System 777 KERN: content type: Be File System 778 KERN: params: type = 235 ; active = 1 779 KERN: content params: <NULL> 780 KERN: Identified boot partition by partition offset.
by , 2 years ago
Attachment: | screenshot445.png added |
---|
comment:10 by , 2 years ago
If we have no partitions and try to create one, what happens?
Can we format partitions?
Do we have a spare thumb drive for testing?
comment:11 by , 2 years ago
Milestone: | Unscheduled → R1/beta4 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Fixed in hrev56500.
This is not helpfull at all, please include information about what the issue is, how you reproduce it, what your haiku revision is etc.