[CLOSED]diskdrake crash with RAID structure left on disk

This forum is dedicated to advanced help and support :

Ask here your questions about advanced usage of Mageia. For example you may post here all your questions about network and automated installs, complex server configurations, kernel tuning, creating your own Mageia mirrors, and all tasks likely to be touchy even for skilled users.

[CLOSED]diskdrake crash with RAID structure left on disk

Postby mailedfist » Jun 5th, '12, 23:46

I have been ignoring this issue for months but was hoping that it may be resolved in Mageia 2. Sadly not, so I thought I'd post on the forum again in case anyone has any bright ideas.

I was running software RAID 1 but decided I wanted to go to hardware instead, so installed a hardware RAID card which works fine. However, the software RAID controller still has one RAID drive connected. I can't tell it that it is no longer RAID without completely reformatting the disk, which I don't want to do, so it complains there is a RAID structure on the disk on each boot, but that's no big deal. What is a big deal is that diskdrake crashes so I can't use the nice GUI I've used for the last umpteen years to manage my partitions. :(
Code: Select all
ERROR: jmicron: wrong # of devices in RAID set "jmicron_JRAID" [1/2] on /dev/sdb
ERROR: jmicron: wrong # of devices in RAID set "jmicron_JRAID" [1/2] on /dev/sdb
INTERNAL ERROR: unknown device sdb1
MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/devices.pm:186
devices::entry() called from /usr/lib/libDrakX/devices.pm:201
devices::make() called from /usr/lib/libDrakX/fs/type.pm:275
fs::type::call_blkid() called from /usr/lib/libDrakX/fs/type.pm:283
fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/fsedit.pm:271
fsedit::get_hds() called from /usr/sbin/diskdrake:74
Last edited by mailedfist on Jun 24th, '14, 00:31, edited 1 time in total.
Mandrake->Mandriva->Mageia starting in 2003. I really dislike another well-known distro starting with U.
mailedfist
 
Posts: 102
Joined: Sep 11th, '11, 21:28

Re: diskdrake crash with RAID structure left on disk

Postby wintpe » Jun 7th, '12, 00:21

Fdisk -l will help us, also what did use use to create the raid, the bios or a util.

Regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1204
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: diskdrake crash with RAID structure left on disk

Postby mailedfist » Jun 7th, '12, 20:28

As I recall, I just connected the second drive and switched the RAID controller BIOS into RAID 1 mode.

/dev/sda has never been RAID.
/dev/sdb was half of a RAID 1, and is still connected to the same controller.
/dev/sdc is hardware RAID 1.

Sorry that the fdisk ouput is so verbose - even the normal drive gets special treatment for some reason (and always has done):

Code: Select all
[root@fast mark]# fdisk -l

Disk /dev/sda: 400.1 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders, total 781422768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2e2c2e2c

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63    41945714    20972826    7  HPFS/NTFS/exFAT
/dev/sda2        41945715   745303544   351678915    f  W95 Ext'd (LBA)
/dev/sda5        41945778    83891429    20972826    7  HPFS/NTFS/exFAT
/dev/sda6        83891493   125837144    20972826    7  HPFS/NTFS/exFAT
/dev/sda7       175510188   237504959    30997386   83  Linux
/dev/sda8       448181433   469499624    10659096   83  Linux
/dev/sda9       125837208   175510124    24836458+  82  Linux swap / Solaris
/dev/sda10      237505023   448181369   105338173+  83  Linux
/dev/sda11      469499688   489452354     9976333+  82  Linux swap / Solaris
/dev/sda12      489452418   497838284     4192933+   7  HPFS/NTFS/exFAT
/dev/sda13      497838348   540780029    21470841    7  HPFS/NTFS/exFAT
/dev/sda14      540780093   583721774    21470841    7  HPFS/NTFS/exFAT
/dev/sda15      583721838   712563074    64420618+  83  Linux
/dev/sda16      712563138   728933309     8185086    7  HPFS/NTFS/exFAT
/dev/sda17      728933373   745303544     8185086   83  Linux

Partition table entries are not in disk order

Disk /dev/sdb: 400.1 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders, total 781422768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8313e26f

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63    42042104    21021021    7  HPFS/NTFS/exFAT                                       
/dev/sdb2        42042105   488359934   223158915    5  Extended                                               
/dev/sdb5        42042168    84276989    21117411    7  HPFS/NTFS/exFAT                                       
/dev/sdb6        84277053   126656459    21189703+  83  Linux                                                 
/dev/sdb7       126656523   208989584    41166531   83  Linux                                                 
/dev/sdb8       208989648   368129474    79569913+  83  Linux                                                 
/dev/sdb9       368129538   488359934    60115198+   7  HPFS/NTFS/exFAT                                       
                                                                                                               
Disk /dev/sdc: 500.0 GB, 500028145664 bytes                                                                   
255 heads, 63 sectors/track, 60791 cylinders, total 976617472 sectors                                         
Units = sectors of 1 * 512 = 512 bytes                                                                         
Sector size (logical/physical): 512 bytes / 512 bytes                                                         
I/O size (minimum/optimal): 512 bytes / 512 bytes                                                             
Disk identifier: 0x8313e26f                                                                                   
                                                                                                               
   Device Boot      Start         End      Blocks   Id  System                                                 
/dev/sdc1   *          63    42042104    21021021    7  HPFS/NTFS/exFAT                                       
/dev/sdc2        42042105   803523104   380740500    5  Extended                                               
/dev/sdc5        42042168    84276989    21117411    7  HPFS/NTFS/exFAT                                       
/dev/sdc6        84277053   126656459    21189703+  83  Linux                                                 
/dev/sdc7       126656523   208989584    41166531   83  Linux                                                 
/dev/sdc8       208989648   368129474    79569913+  83  Linux                                                 
/dev/sdc9       368129538   488359934    60115198+   7  HPFS/NTFS/exFAT                                       
/dev/sdc10      488359998   803523104   157581553+  83  Linux

Disk /dev/mapper/nvidia_fbabbeci: 400.1 GB, 400088432640 bytes
255 heads, 63 sectors/track, 48641 cylinders, total 781422720 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2e2c2e2c

                      Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbeci1   *          63    41945714    20972826    7  HPFS/NTFS/exFAT
/dev/mapper/nvidia_fbabbeci2        41945715   745303544   351678915    f  W95 Ext'd (LBA)
/dev/mapper/nvidia_fbabbeci5        41945778    83891429    20972826    7  HPFS/NTFS/exFAT
/dev/mapper/nvidia_fbabbeci6        83891493   125837144    20972826    7  HPFS/NTFS/exFAT
/dev/mapper/nvidia_fbabbeci7       175510188   237504959    30997386   83  Linux
/dev/mapper/nvidia_fbabbeci8       448181433   469499624    10659096   83  Linux
/dev/mapper/nvidia_fbabbeci9       125837208   175510124    24836458+  82  Linux swap / Solaris
/dev/mapper/nvidia_fbabbeci10      237505023   448181369   105338173+  83  Linux
/dev/mapper/nvidia_fbabbeci11      469499688   489452354     9976333+  82  Linux swap / Solaris
/dev/mapper/nvidia_fbabbeci12      489452418   497838284     4192933+   7  HPFS/NTFS/exFAT
/dev/mapper/nvidia_fbabbeci13      497838348   540780029    21470841    7  HPFS/NTFS/exFAT
/dev/mapper/nvidia_fbabbeci14      540780093   583721774    21470841    7  HPFS/NTFS/exFAT
/dev/mapper/nvidia_fbabbeci15      583721838   712563074    64420618+  83  Linux
/dev/mapper/nvidia_fbabbeci16      712563138   728933309     8185086    7  HPFS/NTFS/exFAT
/dev/mapper/nvidia_fbabbeci17      728933373   745303544     8185086   83  Linux

Partition table entries are not in disk order

Disk /dev/mapper/nvidia_fbabbecip1: 21.5 GB, 21476173824 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41945652 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

                         Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbecip1p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/mapper/nvidia_fbabbecip1p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/mapper/nvidia_fbabbecip1p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/mapper/nvidia_fbabbecip1p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order
omitting empty partition (6)
Partition 6 is deleted

Disk /dev/mapper/nvidia_fbabbecip2: 360.1 GB, 360119208960 bytes
255 heads, 63 sectors/track, 43782 cylinders, total 703357830 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x034804b0

                         Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbecip2p1              63    41945714    20972826    7  HPFS/NTFS/exFAT
/dev/mapper/nvidia_fbabbecip2p2        41945715    83891429    20972857+   5  Extended
/dev/mapper/nvidia_fbabbecip2p5        41945778    83891429    20972826    7  HPFS/NTFS/exFAT

Disk /dev/mapper/nvidia_fbabbecip5: 21.5 GB, 21476173824 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41945652 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

                         Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbecip5p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/mapper/nvidia_fbabbecip5p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/mapper/nvidia_fbabbecip5p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/mapper/nvidia_fbabbecip5p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order

Disk /dev/mapper/nvidia_fbabbecip6: 21.5 GB, 21476173824 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41945652 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

                         Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbecip6p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/mapper/nvidia_fbabbecip6p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/mapper/nvidia_fbabbecip6p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/mapper/nvidia_fbabbecip6p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order

Disk /dev/mapper/nvidia_fbabbecip7: 31.7 GB, 31741323264 bytes
255 heads, 63 sectors/track, 3858 cylinders, total 61994772 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/nvidia_fbabbecip8: 10.9 GB, 10914914304 bytes
255 heads, 63 sectors/track, 1326 cylinders, total 21318192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/nvidia_fbabbecip9: 25.4 GB, 25432533504 bytes
255 heads, 63 sectors/track, 3091 cylinders, total 49672917 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/nvidia_fbabbecip10: 107.9 GB, 107866289664 bytes
255 heads, 63 sectors/track, 13113 cylinders, total 210676347 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/nvidia_fbabbecip11: 10.2 GB, 10215765504 bytes
255 heads, 63 sectors/track, 1241 cylinders, total 19952667 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/nvidia_fbabbecip12: 4293 MB, 4293563904 bytes
255 heads, 63 sectors/track, 521 cylinders, total 8385867 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

                          Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbecip12p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/mapper/nvidia_fbabbecip12p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/mapper/nvidia_fbabbecip12p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/mapper/nvidia_fbabbecip12p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order

Disk /dev/mapper/nvidia_fbabbecip13: 22.0 GB, 21986141184 bytes
255 heads, 63 sectors/track, 2672 cylinders, total 42941682 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

                          Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbecip13p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/mapper/nvidia_fbabbecip13p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/mapper/nvidia_fbabbecip13p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/mapper/nvidia_fbabbecip13p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order

Disk /dev/mapper/nvidia_fbabbecip14: 22.0 GB, 21986141184 bytes
255 heads, 63 sectors/track, 2672 cylinders, total 42941682 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

                          Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbecip14p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/mapper/nvidia_fbabbecip14p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/mapper/nvidia_fbabbecip14p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/mapper/nvidia_fbabbecip14p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order

Disk /dev/mapper/nvidia_fbabbecip15: 66.0 GB, 65966713344 bytes
255 heads, 63 sectors/track, 8019 cylinders, total 128841237 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/nvidia_fbabbecip16: 8381 MB, 8381528064 bytes
255 heads, 63 sectors/track, 1018 cylinders, total 16370172 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2052474d

This doesn't look like a partition table
Probably you selected the wrong device.

                          Device Boot      Start         End      Blocks   Id  System
/dev/mapper/nvidia_fbabbecip16p1   ?     6579571  1924427647   958924038+  70  DiskSecure Multi-Boot
/dev/mapper/nvidia_fbabbecip16p2   ?  1953251627  3771827541   909287957+  43  Unknown
/dev/mapper/nvidia_fbabbecip16p3   ?   225735265   225735274           5   72  Unknown
/dev/mapper/nvidia_fbabbecip16p4      2642411520  2642463409       25945    0  Empty

Partition table entries are not in disk order

Disk /dev/mapper/nvidia_fbabbecip17: 8381 MB, 8381528064 bytes
255 heads, 63 sectors/track, 1018 cylinders, total 16370172 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/jmicron_JRAID: 250.0 GB, 250047627264 bytes
255 heads, 63 sectors/track, 30399 cylinders, total 488374272 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8313e26f

                    Device Boot      Start         End      Blocks   Id  System
/dev/mapper/jmicron_JRAID1   *          63    42042104    21021021    7  HPFS/NTFS/exFAT
/dev/mapper/jmicron_JRAID2        42042105   488359934   223158915    5  Extended
/dev/mapper/jmicron_JRAID5        42042168    84276989    21117411    7  HPFS/NTFS/exFAT
/dev/mapper/jmicron_JRAID6        84277053   126656459    21189703+  83  Linux
/dev/mapper/jmicron_JRAID7       126656523   208989584    41166531   83  Linux
/dev/mapper/jmicron_JRAID8       208989648   368129474    79569913+  83  Linux
/dev/mapper/jmicron_JRAID9       368129538   488359934    60115198+   7  HPFS/NTFS/exFAT

Disk /dev/mapper/jmicron_JRAIDp1: 21.5 GB, 21525525504 bytes
255 heads, 63 sectors/track, 2616 cylinders, total 42042042 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

                       Device Boot      Start         End      Blocks   Id  System
/dev/mapper/jmicron_JRAIDp1p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/mapper/jmicron_JRAIDp1p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/mapper/jmicron_JRAIDp1p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/mapper/jmicron_JRAIDp1p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order
Warning: ignoring extra data in partition table 6
Warning: ignoring extra data in partition table 6
Warning: ignoring extra data in partition table 6
Warning: invalid flag 0xffff of partition table 6 will be corrected by w(rite)

Disk /dev/mapper/jmicron_JRAIDp2: 228.5 GB, 228514728960 bytes
255 heads, 63 sectors/track, 27782 cylinders, total 446317830 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

                       Device Boot      Start         End      Blocks   Id  System
/dev/mapper/jmicron_JRAIDp2p1              63    42234884    21117411    7  HPFS/NTFS/exFAT
/dev/mapper/jmicron_JRAIDp2p2        42234885    84614354    21189735    5  Extended
/dev/mapper/jmicron_JRAIDp2p5        42234948    84614354    21189703+  83  Linux
/dev/mapper/jmicron_JRAIDp2p6   ?   126849239   126849237  2147483647+  ff  BBT

Disk /dev/mapper/jmicron_JRAIDp5: 21.6 GB, 21624228864 bytes
255 heads, 63 sectors/track, 2628 cylinders, total 42234822 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/jmicron_JRAIDp6: 21.7 GB, 21698256384 bytes
255 heads, 63 sectors/track, 2637 cylinders, total 42379407 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/jmicron_JRAIDp7: 42.2 GB, 42154527744 bytes
255 heads, 63 sectors/track, 5124 cylinders, total 82333062 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/jmicron_JRAIDp8: 81.5 GB, 81479591424 bytes
255 heads, 63 sectors/track, 9905 cylinders, total 159139827 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/jmicron_JRAIDp9: 61.6 GB, 61557963264 bytes
255 heads, 63 sectors/track, 7483 cylinders, total 120230397 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2052474d

This doesn't look like a partition table
Probably you selected the wrong device.

                       Device Boot      Start         End      Blocks   Id  System
/dev/mapper/jmicron_JRAIDp9p1   ?     6579571  1924427647   958924038+  70  DiskSecure Multi-Boot
/dev/mapper/jmicron_JRAIDp9p2   ?  1953251627  3771827541   909287957+  43  Unknown
/dev/mapper/jmicron_JRAIDp9p3   ?   225735265   225735274           5   72  Unknown
/dev/mapper/jmicron_JRAIDp9p4      2642411520  2642463409       25945    0  Empty

Partition table entries are not in disk order
Mandrake->Mandriva->Mageia starting in 2003. I really dislike another well-known distro starting with U.
mailedfist
 
Posts: 102
Joined: Sep 11th, '11, 21:28

Re: diskdrake crash with RAID structure left on disk

Postby wintpe » Jun 7th, '12, 22:30

Im sorry your just going to have to take a hit on this, buy a usb external drive, back it up and

Reformat.

Its just not worth the agro, and you possibly need a backup device anyway.

And theres a risk that not backing it up and converting could loose your data

Its just not worth it.

Regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1204
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: diskdrake crash with RAID structure left on disk

Postby mailedfist » Jun 7th, '12, 23:15

I backup to LTO tape once a week. Getting the data back isn't the problem.
The issue is that, despite trying on-and-off for months, I cannot get my machine to boot straight to the HW RAID drive - grub doesn't support it. Hence, /boot has to be on one of the other drives and it is currently on the one which was SW RAID. Every time I try and move it to the other one, this stupid mapper nonsense comes into play and it changes the drive IDs and stops with a kernel panic.

I'll stick with no diskdrake for now until I can get a clear 72 hours or so to do battle with grub again. My next machine will not have a JMicron disk controller - I want /dev/sd* to be what it says, not some silly other name!
Mandrake->Mandriva->Mageia starting in 2003. I really dislike another well-known distro starting with U.
mailedfist
 
Posts: 102
Joined: Sep 11th, '11, 21:28

Re: diskdrake crash with RAID structure left on disk

Postby wintpe » Jun 8th, '12, 01:30

re hw raid not supported,

can you let us know what hw raid you are using.

and for example does it have its own boot rom/config rom.

have you set in the bios of the computer to boot from other rather than sata or cdrom.

I ask this as many a raid/slot in additional harddisk controller have i used and never have i not been able to boot from it

unless its one of those joke raids.

regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1204
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: diskdrake crash with RAID structure left on disk

Postby mailedfist » Jun 8th, '12, 22:16

Its a HighPoint 622.

lspci gives
04:00.0 RAID bus controller: HighPoint Technologies, Inc. Device 0622 (rev 01)

The kernel copes with it fine using dkms. The machine BIOS quite happily starts grub from it, but grub gives up when it is loading linux.

All I have to do is move /boot to another drive and change the BIOS to boot from that. grub then loads the kernel fine, and it then recognises the RAID drive and the rest of the linux filesystem runs from the RAID array with no problems.
Mandrake->Mandriva->Mageia starting in 2003. I really dislike another well-known distro starting with U.
mailedfist
 
Posts: 102
Joined: Sep 11th, '11, 21:28

Re: diskdrake crash with RAID structure left on disk

Postby wintpe » Jun 9th, '12, 01:52

I had one of those rocketraids from highpoint, alot of money and damm useless.

still got it and dont use it.

so i understand you point of view.

with modern CPU's software raid is just as good, where i work we use software riad on all the SUN Microsystems systems and it does not affect there performance at all, you can get a free version of veritas volume manager that will manage a limited set of luns.

or you can use one of the many opensource mirroring software.

just use a standard disk controller.

alternatively the 3ware controllers are good, there proper raid, and if your PC is PCI-X bus there realy cheap on ebay, i got a 12 channel sata for about £50 for my file server I think its a 9660.

just some ideas

regards peter, and sorry i could not help you solve it.
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1204
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: diskdrake crash with RAID structure left on disk

Postby mailedfist » Jun 12th, '12, 00:14

No problem Peter, thanks for the input.

Apologies for the delay in responding, but I have a bigger problem at the moment. My 4 year old motherboard has decided to develop a fault. I got a kernel panic in the middle of editing in libreoffice (not something I would expect) and now I sometimes don't get as far as POST beep or, if I do, it locks up at various points before getting into grub. So, this thread will be paused for a while until I either find the dry joint/broken track/loose connection or bite the bullet and buy a new board.
Mandrake->Mandriva->Mageia starting in 2003. I really dislike another well-known distro starting with U.
mailedfist
 
Posts: 102
Joined: Sep 11th, '11, 21:28

Re: diskdrake crash with RAID structure left on disk

Postby wintpe » Jun 12th, '12, 13:29

ok, i know this is off thread, but since you have not started a new one.

1:check that the cpu to heatsink is a good connection and that the fan is running and clear of dust.

2: if you can remove a dimm and run with one then swap that if it still does it.

memory and overheating cpu are the most common cause of system failure on the mb, disk bad blocks are probably the highest cause.

regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1204
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: diskdrake crash with RAID structure left on disk

Postby mailedfist » Jun 24th, '12, 21:06

This thread is likely to never be completed - the motherboard on the PC in question appears to be dead.

In answer to the previous suggestions relating to that, no (measured) part of the system has ever been above 45 Celsius. I've never (in my 30 years plus of working with computers) known memory stop a machine from doing POST, and as far as disk doing it - no way, Jose. However, the symptoms are entirely consistent with failing capacitors and it turns out that the motherboard in question is prone to capacitor issues (wish I'd know four years ago that they were fitting ultra-cheap electrolytics!). It has progressed from intermittent to permanent. I'm not a happy bunny.

When I get the replacement machine up and running, I'll see whether I can reproduce the thread topic problem but I suspect it was entirely related to the JMicron RAID controller which does not exist on the HP. :(
Mandrake->Mandriva->Mageia starting in 2003. I really dislike another well-known distro starting with U.
mailedfist
 
Posts: 102
Joined: Sep 11th, '11, 21:28

Re: diskdrake crash with RAID structure left on disk

Postby martinw » Jun 30th, '12, 19:24

Having just replaced my motherboard, I've encountered the same problem with a disk that was long ago part of a RAID array. The command
Code: Select all
dmraid -rE

fixed it for me. Note that unless you specify a device path, all discovered RAID structures will be removed - so go carefully!
martinw
 
Posts: 608
Joined: May 14th, '11, 10:59


Return to Advanced support

Who is online

Users browsing this forum: No registered users and 1 guest