Failed to initialize the disk (regression)

[danboid]

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.

[diver]

Please provide a syslog after getting those errors.

[danboid]

Initialize disk syslog errors

[diver]

If you start DriveSetup from Terminal is there any output when you Initialize intel partition map?

[danboid]

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

[danboid]

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

[danboid]

I can successfully initialize the same disk and install/boot Haiku on the same machine using beta3.

[waddlesplash]

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.

[pulkomandy]

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.

[danboid]

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?

[pulkomandy]

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.

[elwood]

I have the same kind of issue. I'm on hrev58191, running on a 2011 iMac.

I booted from Haiku on my USB drive and I cannot initialize the internal Samsung SSD. See attached picture. Why?

Second thing to enhance, the error message says: Failed to initialize the disk ""! Is it possible to use the disk name in the double quotes?

When I try to do "unmount" on the volume on the SSD, it asks for confirmation and I selected "force unmount". Then it says: Could not unmount partition "Haiku". I don't know if it's a bug (I'm new to Haiku) but I presume the volume is not used as I booted from the USB drive.

[elwood]

screenshot of DriveSetup

[waddlesplash]

This is a different problem; the disk is indeed busy since it's currently mounted. Why it can't be unmounted is another matter separate from what this ticket is about. If the problem persists a new ticket should be opened.