1

Topic: Device or resource busy

I faced up with this firstly at Lubuntu and now at antiX:

An error occurred while applying the operations.

See the details for more information.

IMPORTANT
If you want support, you need to provide the saved details!
See http://gparted.org/save-details.htm for more information.

The details:

GParted 0.19.0 --enable-libparted-dmraid --enable-online-resize
Libparted 3.2
Delete /dev/sdb1 (unknown, 7.47 GiB) from /dev/sdb  00:00:01    ( SUCCESS )     calibrate /dev/sdb1  00:00:00    ( SUCCESS )     path: /dev/sdb1
start: 2048
end: 15663103
size: 15661056 (7.47 GiB) 

delete partition  00:00:01    ( SUCCESS ) 

========================================
Create Primary Partition #1 (fat32, 7.47 GiB) on /dev/sdb  00:00:01    ( ERROR )     create empty partition  00:00:00    ( SUCCESS )     path: /dev/sdb1
start: 2048
end: 15663103
size: 15661056 (7.47 GiB) 

clear old file system signatures in /dev/sdb1  00:00:00    ( SUCCESS )     write 68.00 KiB of zeros at byte offset 0  00:00:00    ( SUCCESS ) 
write 4.00 KiB of zeros at byte offset 67108864  00:00:00    ( SUCCESS ) 
write 4.00 KiB of zeros at byte offset 8018456576  00:00:00    ( SUCCESS ) 
flush operating system cache of /dev/sdb  00:00:00    ( SUCCESS ) 

set partition type on /dev/sdb1  00:00:01    ( SUCCESS )     new partition type: fat32 

create new fat32 file system  00:00:00    ( ERROR )     mkfs.fat -F32 -v -I -n " " /dev/sdb1     mkfs.fat 3.0.27 (2014-11-12)

mkfs.fat: unable to open /dev/sdb1: Device or resource busy

Any idea?

2

Re: Device or resource busy

It appears that in between creating the partition and formatting it, the operating system remounted the partition.  This causes the partition to be busy and hence the format fails.

The most likely cause is that GParted was unable to lock the disk devices to prevent this occurring.

Many bugs have been fixed since GParted 0.19.0.  We recommend using the latest version.  The best way to use GParted is to boot from live media, such as GParted Live.