1

Topic: Error resizing RAID0 partition

Trying to resize a gpt ntfs partition in uefi mode.
I am receiving a lot crap. First when gparted boots up it complains something about the alignment. gparted asks if it wants to fix it, I say yes, then I get two more windows with retry or ignore.

finally after all the ignores gparted pops up.

I tried to resize RAID0 gpt ntfs partition. I get this.

http://i.imgur.com/v141s8g.jpg
http://i.imgur.com/Xg7LRd3.jpg
http://i.imgur.com/Gmaw1lF.jpg
http://i.imgur.com/GNlo3EL.jpg
http://i.imgur.com/zqZMPvd.jpg

2

Re: Error resizing RAID0 partition

So your using firmware specified software raid, ISW (Intel Software RAID).  The integrity of the GPT on /dev/mapper/isw_bfbhfhbdjb_Volume0 is questionable.

1) Please check the RAID array and confirm all drives and volumes are OK?

2) Please confirm the version of GParted being used?  Latest is 0.23.0.

3) Please provide the output of the following commands:

sudo parted /dev/mapper/isw_bfbhfhbdjb_Volume0 print
sudo gdisk -l /dev/mapper/isw_bfbhfhbdjb_Volume0
sudo lsblk -o name,maj:min,rm,size,ro,type,fstype,label,mountpoint

3

Re: Error resizing RAID0 partition

mfleetwo wrote:

So your using firmware specified software raid, ISW (Intel Software RAID).  The integrity of the GPT on /dev/mapper/isw_bfbhfhbdjb_Volume0 is questionable.

1) Please check the RAID array and confirm all drives and volumes are OK?

2) Please confirm the version of GParted being used?  Latest is 0.23.0.

3) Please provide the output of the following commands:

sudo parted /dev/mapper/isw_bfbhfhbdjb_Volume0 print
sudo gdisk -l /dev/mapper/isw_bfbhfhbdjb_Volume0
sudo lsblk -o name,maj:min,rm,size,ro,type,fstype,label,mountpoint

1. Yea, everything is fine. Win7x64 is fine, runs just great under raid0. No problems at all. Just to be sure, how would I check to make sure everything is ok?

2. Using the latest.

3.

user@debian:~$ sudo parted /dev/mapper/isw_bfbhfhbdjb_Volume0 print
Warning: Not all of the space available to /dev/mapper/isw_bfbhfhbdjb_Volume0
appears to be used, you can fix the GPT to use all of the space (an extra 512
blocks) or continue with the current setting? 
Fix/Ignore?
user@debian:~$ sudo gdisk -l /dev/mapper/isw_bfbhfhbdjb_Volume0
GPT fdisk (gdisk) version 1.0.0

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/mapper/isw_bfbhfhbdjb_Volume0: 500130304 sectors, 238.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 0FA9583B-10A6-47D5-957F-63E1F8B2D408
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 500129758
Partitions will be aligned on 2048-sector boundaries
Total free space is 41963453 sectors (20.0 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          206847   100.0 MiB   EF00  EFI system partition
   2          206848          468991   128.0 MiB   0C01  Microsoft reserved ...
   3          468992       458168319   218.2 GiB   0700  Basic data partition
user@debian:~$
user@debian:~$ sudo lsblk -o name,maj:min,rm,size,ro,type,fstype,label,mountpoint
NAME   MAJ:MIN RM   SIZE RO TYPE   FSTYPE   LABEL                   MOUNTPOINT
sda      8:0    0 119.2G  0 disk   isw_raid                         
└─isw_bfbhfhbdjb_Volume0
       254:0    0 238.5G  0 dmraid                                  
sdb      8:16   0 119.2G  0 disk   isw_raid                         
├─sdb1   8:17   0   128M  0 part                                    
└─isw_bfbhfhbdjb_Volume0
       254:0    0 238.5G  0 dmraid                                  
sdc      8:32   0 931.5G  0 disk                                    
├─sdc1   8:33   0   128M  0 part                                    
├─sdc2   8:34   0 692.4G  0 part   ntfs     WD1 Storage             
└─sdc3   8:35   0   239G  0 part   ntfs     Network Drive Backup    
sdd      8:48   0 698.7G  0 disk                                    
└─sdd1   8:49   0 698.7G  0 part   ntfs     Toshiba1 Storage Backup 
sde      8:64   0  55.9G  0 disk                                    
├─sde1   8:65   0   128M  0 part                                    
└─sde2   8:66   0  55.8G  0 part   ntfs     Vertex2                 
sdf      8:80   1   7.4G  0 disk                                    
└─sdf1   8:81   1   7.4G  0 part   vfat                             /lib/live/mo
sr0     11:0    1  1024M  0 rom                                     
loop0    7:0    0 204.4M  1 loop   squashfs                         /lib/live/mo
user@debian:~$

Thank you for your time, I appreciate it.

4

Re: Error resizing RAID0 partition

In a virtual machine I created an ISW mirror pair RAID array using sdb and sdc.  I then tried to use GParted from the Live CD to partition it with a GPT and create a file system.

When starting GParted I got the following dialog, twice:

==== Libparted Warning ====
/!\ Not all of the space available to /dev/sdb appears to be
    used, you can fix the GPT to use all of the space (an
    extra 9208 blocks) or continue with the current settings?
                                          [  Fix  ][ Ignore ]

Once for /dev/sdb and once for /dev/sdc, the two physical drives on which the ISW mirror RAID array was created.

It appears that libparted is finding the GPT on the underlying disks of the RAID array and is probably offering to move it.  Allowing this to be fixed might well destroy the RAID array by moving the primary and/or backup GPT on those disks to the start and/or end of the disk, overwriting the metadata.

When trying to create a partition under GPT on the RAID array it failed at the point of creating the file system because the partition device /dev/mapper/isw_bbhghdaeaf_Volume01 didn't exist.

@MozillaUser1111

To report the status of the RAID array run these commands:

sudo dmraid -r
sudo dmrais -s

It appears that GParted is broken and not able partition firmware specified software RAID arrays.  It might even be dangerous to use.

5

Re: Error resizing RAID0 partition

user@debian:~$ sudo dmraid -r
/dev/sdb: isw, "isw_bhbgiccagc", GROUP, ok, 250069678 sectors, data@ 0
/dev/sda: isw, "isw_bhbgiccagc", GROUP, ok, 250069678 sectors, data@ 0
user@debian:~$ sudo dmrais -s
sudo: dmrais: command not found
user@debian:~$ sudo dmraid -s
*** Group superset isw_bhbgiccagc
--> Subset
name   : isw_bhbgiccagc_Samsung 840 PROS
size   : 500130304
stride : 64
type   : stripe
status : ok
subsets: 0
devs   : 2
spares : 0
user@debian:~$ 

6

Re: Error resizing RAID0 partition

I just tested creating a GPT partition table on an ISW FAKE RAID, and then creating a partition formatted with ext4 using GParted 0.23.0.

I did not receive any errors regarding space in the GPT, but the formatting of the ext4 partition failed because "/dev/mapper/isw_efjbbijhh_Vol01" did not exist.  Upon checking the /dev/mapper directory I discovered that the partition path was "/dev/mapper/isw_efjbbijhh_Vol0p1".  This is due to two different naming standards that were in use for dmraid FAKE RAID support and which version is supported in your particular libparted version.

You can use the libparted standard by configuring with the option "--enable-libparted-dmraid".  See https://git.gnome.org/browse/gparted/tree/README#n122

After rebuilding with configure option "--enable-libparted-dmraid", creating a new ext4 formatted partition worked for me.