Opened 2 years ago
Closed 2 years ago
#17673 closed bug (not reproducible)
Failed to initialize the disk (regression)
Reported by: | danboid | Owned by: | stippi |
---|---|---|---|
Priority: | critical | Milestone: | R1/beta4 |
Component: | Applications/DriveSetup | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
My Haiku box died in the last week or so so tonight I attempted to install haiku-master-hrev55961-x86_64-anyboot on an old i7 desktop machine, I'm pretty sure it pre-dates UEFI.
So I open DriveSetup, choose my HD/SSD (I've tried this with two different SATA disks, one a spinning rust HD and one a SSD) then I choose Initialize -> Intel Partition Map from the Disk menu then and choose to Continue and Write changes I get the error:
Failed to initialize the disk !
Error: Invalid Argument
If I try the same function again I get the error:
Failed to initialize the disk !
Error: Device/File/Resource busy.
Choosing Initialize -> GUID Partition Map instead has the same problem.
Attachments (1)
Change History (11)
comment:1 by , 2 years ago
comment:2 by , 2 years ago
If you start DriveSetup from Terminal is there any output when you Initialize intel partition map?
comment:3 by , 2 years ago
DiskDeviceJobQueue::Execute(): executing job: N8BPrivate15UninitializeJobE DiskDeviceJobQueue::Execute(): executing job failed: Invalid Argument DiskDeviceJobQueue::Execute(): executing job: N8BPrivate15UninitializeJobE DiskDeviceJobQueue::Execute(): executing job failed: Device/File/Resource busy
comment:4 by , 2 years ago
DiskDeviceJobQueue::Execute(): executing job: N8BPrivate15UninitializeJobE DiskDeviceJobQueue::Execute(): executing job failed: Invalid Argument DiskDeviceJobQueue::Execute(): executing job: N8BPrivate15UninitializeJobE DiskDeviceJobQueue::Execute(): executing job failed: Device/File/Resource busy
comment:5 by , 2 years ago
I can successfully initialize the same disk and install/boot Haiku on the same machine using beta3.
comment:6 by , 2 years ago
Milestone: | Unscheduled → R1/beta4 |
---|---|
Summary: | Failed to initilize the disk → Failed to initialize the disk (regression) |
comment:7 by , 2 years ago
I don't see any significant changes to DriveSetup, the Storage Kit, the kernel Disk Device Manager, the kernel partitioning systems, or the disk add-ons since early 2021 (i.e. before beta3) so this is kind of baffling.
comment:8 by , 2 years ago
Hello, can you test initializing as GPT partition table instead? Depending on if that works or not, we will better know where to look for the problem.
comment:9 by , 2 years ago
The machine I was using when I discovered this bug has since died but I've now got a new Haiku box and I was able to successfully initialize its disk so I think we can close this now.
I experienced a related issue today with trying to unmount Be partitions using the latest x64 nightly. Haiku wasn't letting me unmount a mounted Be partition and this prevented me initialising the disk. Is that a known bug or two?
comment:10 by , 2 years ago
Resolution: | → not reproducible |
---|---|
Status: | new → closed |
The machine I was using when I discovered this bug has since died but I've now got a new Haiku box and I was able to successfully initialize its disk so I think we can close this now.
Ok, then let's close this.
I experienced a related issue today with trying to unmount Be partitions using the latest x64 nightly. Haiku wasn't letting me unmount a mounted Be partition and this prevented me initialising the disk. Is that a known bug or two?
This happens when some application has a file open in that disk (for example if you have a Terminal tab pointing to it). It could also be Tracker generating image thumbnails in the background. In any case it's probably better to track this in a separate bug and we can close this one. Thanks for updating us.
Please provide a syslog after getting those errors.