palimpsest cannot recognize NTFS volumes that it previously created upon RAID arrays

Bug #695611 reported by Tim Kuechler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-disk-utility (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: gnome-disk-utility

Ubuntu 10.10
gnome-disk-utility: 2.30.1-2

Steps to reproduce:

1) Use mdadm to create a RAID array. Example:

Mount four unpartitioned, unformatted disks the do this:

sudo mdadm --create --verbose /dev/md0 --metadata 1.2 --level=10 --raid-devices=4 /dev/sdb /dev/sdc /dev/sdd /dev/sde

2) Open palimpsest and format /dev/mdo as a volume (no partition table) and as an NTFS volume)

3) Mount /dev/mdo using "name" and using palimsest to mount it. (it mounts at /media/name)

4) Make the following entry in /etc/mdadm/mdadm.conf:

ARRAY /dev/md0 level=raid10 num-devices=4 metadata=01.02 name=ubuntu-server:0 UUID=c60eb2ea:6a911abf:75743422:12ffb49d

5) Make a mount entry in /etc/fstab for example:

UUID=23559D7F45CD5191 /media/bliss ntfs rw,utf8,uid=iceman,gid=iceman,umask=077 0 0

6) Reboot

7) When the system comes back up open palimpsest and notice that the partition map for /dev/mdo is hooped. Also palimsest no longer seems to know that /dev/md0 is mounted.

Please see the detailed description of this issue in the following forum thread. I am the forum member icestation.

http://ubuntuforums.org/showthread.php?t=1610861

Revision history for this message
Tim Kuechler (d-launchpad-net-icezebra-dfgh-net) wrote :

I later installed

ntfsprogs:
  Installed: 2.0.0-1ubuntu4

This did not help. Also, from the thread mentioned in the original bug report, this problem is affecting at least 2 people.

Revision history for this message
Tim Kuechler (d-launchpad-net-icezebra-dfgh-net) wrote :
Revision history for this message
Tim Kuechler (d-launchpad-net-icezebra-dfgh-net) wrote :
Download full text (3.6 KiB)

Screenshot showing palimpsest after system is shutdown and restarted.

1) Array auto started at reboot from /etc/mdadm/mdadm.conf using:

ARRAY /dev/md0 level=raid10 num-devices=4 metadata=01.02 name=ubuntu-server:0 UUID=c60eb2ea:6a911abf:75743422:12ffb49d

2) Array auto mounted at reboot from /etc/fstab entry:

UUID=23559D7F45CD5191 /media/bliss ntfs rw,utf8 0 0

Note that palimpsest unaware that array is mounted and has read the /dev/md0 partition table incorrectly (there isn't one, but palimpsest assumes there is one)

OUTPUT from /proc/mdstat:

cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid10 sdc[1] sde[3] sdb[0] sdd[2]
      3907028864 blocks super 1.2 64K chunks 2 near-copies [4/4] [UUUU]

unused devices: <none>

OUTPUT from mdadm:

mdadm --detail /dev/md0
mdadm: metadata format 01.02 unknown, ignored.
/dev/md0:
Version : 01.02
Creation Time : Sun Dec 26 11:35:44 2010
Raid Level : raid10
Array Size : 3907028864 (3726.03 GiB 4000.80 GB)
Used Dev Size : 3907028864 (3726.03 GiB 4000.80 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Tue Dec 28 07:30:23 2010
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0

Layout : near=2, far=1
Chunk Size : 64K

Name : ubuntu-server:0 (local to host ubuntu-server)
UUID : c60eb2ea:6a911abf:75743422:12ffb49d
Events : 24

Number Major Minor RaidDevice State
0 8 16 0 active sync /dev/sdb
1 8 32 1 active sync /dev/sdc
2 8 48 2 active sync /dev/sdd
3 8 64 3 active sync /dev/sde

OUTPUT from parted:

parted -l
Model: ATA HDS722580VLAT20 (scsi)
Disk /dev/sda: 82.3GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 1049kB 78.9GB 78.9GB primary ext4 boot
 2 78.9GB 82.3GB 3398MB extended
 5 78.9GB 82.3GB 3398MB logical linux-swap(v1)

Error: /dev/sdb: unrecognised disk label

Error: /dev/sdc: unrecognised disk label

Error: /dev/sdd: unrecognised disk label

Error: /dev/sde: unrecognised disk label

Model: Linux Software RAID Array (md)
Disk /dev/md0: 4001GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number Start End Size File system Flags
 1 0.00B 4001GB 4001GB ntfs

OUTPUT from ntsinfo (ntsprogs installed)

ntfsinfo -m /dev/md0
Volume Information
Name of device: /dev/md0
Device state: 11
Volume Name: bliss
Volume State: 1
Volume Version: 3.1
Sector Size: 512
Cluster Size: 4096
Volume Size in Clusters: 976757215
MFT Information
MFT Record Size: 1024
MFT Zone Multiplier: 1
MFT Data Position: 24
MFT Zone Start: 0
MFT Zone End: 122094655
MFT Zone Position: 4
Current Position in First Data Zone: 122094655
Current Position in Second Data Zone: 0
LCN of Data Attribute for FILE_MFT: 4
FILE_MFTMirr Size: 4
LCN of Data Attribute for File_MFTMirr: 488378607
Size of Attribute Definition Table: 2560
FILE_Bitmap Information
FILE_Bitmap MFT Record ...

Read more...

Revision history for this message
Tim Kuechler (d-launchpad-net-icezebra-dfgh-net) wrote :

Screen shot from second user "hickimau", also reports same issue. Note that the Meta data version of the RAID array is 1.2. This is the same version as the RAID array that is reported in this bug. Also, according to the forum thread referenced above, the underlying disk hardware is the same model : WD20EARS (SATA 2TB 5400 RPM Western Digital "Green" Drives)

Also Note that palimpsest reports the same partition sizes in both post-reboot screen shots (this one and the one above) with the exception of the second "free" block.

Common parameters in the two configurations:

Disk Hardware (WD20EARS)
NTFS File system
RAID Array metadata version

Differing parameters:

RAID Array size: (2TB vs 4TB)
RAID Array disk count: (2 vs 4)
RAID Array mode: (RAID1 vs RAID10)
RAID ARRAY Base Disk Formatting (Partition tables on each base disk vs NO partition tables on each base disk)

Revision history for this message
Tim Kuechler (d-launchpad-net-icezebra-dfgh-net) wrote :

parted and mdadm output from second user "hickimau":

Output from parted:
> parted -l
Model: ATA ST340014A (scsi)
Disk /dev/sda: 40.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 514MB 513MB primary ext3 boot
2 514MB 2563MB 2049MB primary linux-swap(v1)
3 2563MB 10.7GB 8096MB primary ext3
4 10.7GB 40.0GB 29.4GB primary ext3

Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 2000GB 2000GB RAID: bunker raid

Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sdc: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 2000GB 2000GB RAID: bunker raid

Model: Unknown (unknown)
Disk /dev/md0: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 2000GB 2000GB ntfs

output from mdadm:
>mdadm --detail /dev/md0
/dev/md0:
Version : 01.02
Creation Time : Sun Oct 31 12:38:57 2010
Raid Level : raid1
Array Size : 1953514414 (1863.02 GiB 2000.40 GB)
Used Dev Size : 3907028828 (3726.03 GiB 4000.80 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Nov 1 10:29:21 2010
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Name : :bunker
UUID : 14727e62:c865a027:912026d6:0655d074
Events : 32
Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 17 1 active sync /dev/sdb1

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version. Thanks in advance and sorry for the late response.

Changed in gnome-disk-utility (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-disk-utility (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-disk-utility (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.