ioctl error on BLKRRPART: Device or resource busy

[anchep Yang]

Hi Marc

When I use version 4.0.6 to make the boot disk on linux  mint 20.3,

 use ./install.sh , 

display this error:

### Writing 'esos-4.0.6_z.img.tar.bz2' to '/dev/sdb'; this may take a while...
0+162031 records in
0+162031 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 322.654 s, 26.6 MB/s

### It appears the image was successfully written to disk (no errors reported)!

### Large installation target detected; adding the 'esos_data' file system...
blockdev: ioctl error on BLKRRPART: Device or resource busy
blockdev: ioctl error on BLKRRPART: Device or resource busy

but 4.0.4 is OK, not display this error.

boot disk: INTEL SSD 545S SERIES 256G

system : linux mint 20.3

[Marc Smith]

There haven't been many changes to this file recently:
https://github.com/quantum/esos/commits/4.x.x/install.sh

Perhaps it's just chance (timing) it is giving that error? You may
want to check if your Linux distro has any type of auto-mount'ing when
it sees new block devices / file systems and disable that.

--Marc

> --
> You received this message because you are subscribed to the Google Groups "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to esos-users+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/a11e6ca1-ddcc-44d2-86bc-cad56b46006an%40googlegroups.com.

[anchep Yang]

I was turn off the removable option , but the partition is still auto show on the file manager. so I decompress the img file , use diskgen(disk tools) write the img file to the Intel SSD disk. 

I'm trying this on my computer now.

Is this method possible？

[Marc Smith]

Yeah, that's probably okay... just writing the image out like what 'dd' does.

--Marc

> To view this discussion on the web visit https://groups.google.com/d/msgid/esos-users/885ec7a9-886f-4f59-b9bc-e70ee6fd081bn%40googlegroups.com.