System no longer sees the second RAID array after upgrade from 12.1 to 12.2

mayavi · December 25, 2012, 12:59pm

I have just upgraded my working openSuSE 12.1 to 12.2.

Apart from issues with it repeatedly asking for the non-existent CD1 and screwing most of my graphics programs (including DeVeDe) so that I now have problems when I try to view certain file types;
But, the fixing of those graphics problems is currently a work in progress.

However, what is causing me considerable angst is the refusal of 12.2 to recognize my second (4TB) RAID array;
(Both RAID arrays are hardware RAID 6 arrays).

Disks reports that Device /dev/sdb1 (the second RAID array) is not in use ??? (12.1 originally had a permissions issue but that was easily sorted).
The main problem is that I have absolutely no idea how to make the system recognize that RAID array, I have tried a few things but to no avail

I should point out that when I was upgrading from 12.1 to 12.2 the installer crashed multiple times when it got to the stage of rewriting the Boot Loader.

I have the operating system is on a separate 500GB drive.

Any suggestions?
Thanks

robin_listas · December 25, 2012, 1:44pm

On 2012-12-25 13:06, mayavi wrote:
>
> I have just upgraded my working openSuSE 12.1 to 12.2.

What method?

Online upgrade
method
Offline upgrade
method

Or is it a fresh install?

> However, what is causing me considerable angst is the refusal of 12.2
> to recognize my second (4TB) RAID array;
> (Both RAID arrays are hardware RAID 6 arrays).

You could post the output of “fdisk -l” inside code tags

View this
thread for instructions

What do you mean by “not recognize”? Is the array not seen in fdisk, or
what? Show commands with output that demonstrate, please.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

mayavi · December 26, 2012, 4:05am

Whoops

The missing information is :-

The upgrade was by the Offline method.
The remainder of the information I can see but for reasons I don’t understand the system will (now) not allow me to cut and paste in a terminal panel :’(

I do wish I wasn’t quite so stupid

Investigating further …

mayavi · December 26, 2012, 4:33am

Well this is embarrassing :shame:

Talk about having my brain unplugged :\

Having rebooted my brain the required information is:-

I upgraded from 12.1 to 12.2 using the Offline method.
The output from fdisk is

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 998.6 GB, 998579896320 bytes
255 heads, 63 sectors/track, 121403 cylinders, total 1950351360 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/sda1               1  1950351359   975175679+  ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 3994.3 GB, 3994319585280 bytes
255 heads, 63 sectors/track, 485615 cylinders, total 7801405440 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/sdb1               1  4294967295  2147483647+  ee  GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdc: 500.1 GB, 500106780160 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976771055 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/sdc1               1   976771054   488385527   ee  GPT

GParted lists the required information but I don’t know how to copy it

When I say not recognized I mean that the system does not mount the file system and reports it as unused.
And yet again, I’m not quite sure how to copy that information

Thanks

arvidjaar · December 26, 2012, 8:05am

Is it listed in /etc/fstab? If not, it will not be mounted on startup.

What happens if you do

mkdir /tmp/mnt
mount /dev/sdb1 /tmp/mnt

robin_listas · December 26, 2012, 11:04am

On 2012-12-26 04:06, mayavi wrote:
>
> Whoops
>
> The missing information is :-
>
> 1) The upgrade was by the Offline method.

Ok, then there are things to do after the upgrade, like reviewing the
packages that were not upgraded, and the list of config files that need
action. It is doubtful that it affects mounting of devices, but it is
something to be done.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

robin_listas · December 26, 2012, 11:08am

On 2012-12-26 04:06, mayavi wrote:
>
> Whoops
>
> The missing information is :-
>
> 1) The upgrade was by the Offline method.

I forgot to say. There is a bug affecting the naming of software raids
when using the offline upgrade method: during the upgrade the system
uses one device name different from the one the kernel creates when the
system boots later on. But your case is different, you have hardware
raid, you should not be affected.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

mayavi · December 29, 2012, 9:19am

the listing of /etc/fstab is

linux-b8kb:/etc # cat fstab
/dev/disk/by-id/ata-ST3500418AS_9VMJ8A53-part2 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-ST3500418AS_9VMJ8A53-part3 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-ST3500418AS_9VMJ8A53-part1 /boot/efi            vfat       umask=0002,utf8=true  0 0
/dev/disk/by-id/ata-ST3500418AS_9VMJ8A53-part4 /home                ext4       acl,user_xattr        1 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

One problem I do see is that, it is only listing the non-RAID HDD while the accessible RAID array is not listed :(:\

If I do as you suggested with mkdir and mount, then;-
Only if I log in as root and use an XTerm window (and only if I use XTerm) can I view the files on the other RAID array.

So the question I now have is, what entry do I need to add and where do I add it? or will it still be /etc/fstab?

Thanks

arvidjaar · December 29, 2012, 12:18pm

Yes, you need to add it to /etc/fstab so it is mounted automatically on startup.

robin_listas · December 29, 2012, 12:44pm

On 2012-12-29 09:26, mayavi wrote:

> So the question I now have is, what entry do I need to add and where do
> I add it? or will it still be /etc/fstab?

Similar to


> /dev/disk/by-uuid/UUID_of_your_array  /any/mountpoint/you/want	TYPE	OPTIONS	1 1

in fstab, of course.


ls -l /dev/disk/by-uuid/

will tell you the devices available, and


file -s /dev/disk/by-uuid/UUID_of_your_array

will tell you the type.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

mayavi · January 1, 2013, 11:22am

Thanks for that information Carlos.

I get the following information when I do as you suggest:-

Devices available

linux-b8kb:/ # ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jan  1 16:17 23c61906-ef9a-4a17-8840-a51e3ad218a1 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Jan  1 16:17 2f916450-1d5e-4a1f-b400-22cbd9b55c16 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan  1 16:17 5ed498ef-d72c-41dc-bf5e-1b6eb7e72dcb -> ../../sdc2
lrwxrwxrwx 1 root root 10 Jan  1 16:17 5f0b2731-3b87-4d57-9cc5-415318d5c596 -> ../../sda4
lrwxrwxrwx 1 root root 10 Jan  1 16:17 609B-1A9B -> ../../sdc1
lrwxrwxrwx 1 root root 10 Jan  1 16:17 77991a58-62e1-474c-bee4-75c66a257ccf -> ../../sdc4
lrwxrwxrwx 1 root root 10 Jan  1 16:17 b76d53b8-f944-4cd9-ae80-6385ee6f2dac -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jan  1 16:17 bee240cf-cd71-45be-9d74-19bd756a5032 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan  1 16:17 c26127c6-c46b-4440-b470-c589a3f553b9 -> ../../sda3
linux-b8kb:/ #

I know from GParted that /…/sdb1 is my 4TB array

Type

linux-b8kb:/ # file -s /dev/disk/by-uuid/b76d53b8-f944-4cd9-ae80-6385ee6f2dac
/dev/disk/by-uuid/b76d53b8-f944-4cd9-ae80-6385ee6f2dac: symbolic link to `../../sdb1'
linux-b8kb:/ #

I assume that by TYPE you mean the bit that says “symbolic link” so I assume the TYPE is “symbolic” ?

Mount point

I assume that I can add my 4TB array to the same mount point as my other array?
Using the tail command -

linux-b8kb udisksd[2120]: Mounted /dev/sda1 at /run/media/brian/RAID PARTITION A on behalf of uid 1000

which would make the mount point /run/media/brian/RAID ?

Further dumb questions

I’m a bit confused by the OPTIONS 1 1, where do i find what it means; do I look in fstab or the mount documentation?

Thanks

robin_listas · January 1, 2013, 2:28pm

On 2013-01-01 11:26, mayavi wrote:
>
> Thanks for that information Carlos.
>
> I get the following information when I do as you suggest:-

…

> I know from GParted that /…/sdb1 is my 4TB array

So it also is /dev/disk/by-uuid/b76d53b8-f944-4cd9-ae80-6385ee6f2dac

>
> 2) Type
>
>
> Code:
> --------------------
> linux-b8kb:/ # file -s /dev/disk/by-uuid/b76d53b8-f944-4cd9-ae80-6385ee6f2dac
> /dev/disk/by-uuid/b76d53b8-f944-4cd9-ae80-6385ee6f2dac: symbolic link to `…/…/sdb1’

linux-b8kb:/ #

I assume that by TYPE you mean the bit that says “symbolic link” so I
assume the TYPE is “symbolic” ?

Huh, no, you have to follow that link, or point file directly to
/dev/sdb1. Instead of what i wrote, you have to use “file -s /dev/sdb1”.
Look:


> minas-tirith:/home/cer # file -s /dev/disk/by-label/Boot
> /dev/disk/by-label/Boot: symbolic link to `../../sda6'
&gt; minas-tirith:/home/cer # file -s -L /dev/disk/by-label/Boot
&gt; /dev/disk/by-label/Boot: Linux rev 1.0 ext2 filesystem data (mounted or unclean)
&gt; minas-tirith:/home/cer #

So that partition of mine is type ext2.

> 3) Mount point
>
> I assume that I can add my 4TB array to the same mount point as my
> other array?
> Using the tail command -

No, each partition has to be mounted on a different point. Plus,
automatics use /media, you should not. You should use /mnt/something.
/media will give you troubles.

> 4) Further dumb questions
>
> I’m a bit confused by the OPTIONS 1 1, where do i find what it means;
> do I look in fstab or the mount documentation?

Any or both of them. Try
Look for something like “the sixth field”.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

mayavi · February 3, 2013, 8:46am

Sorry about the long delay, but I have had other system problems >:(

However, I can now manually mount and access my 4TB RAID array lol!
So, technically the initial problem has been solved.

Thanks for all the help Carlos.

robin_listas · February 3, 2013, 12:18pm

On 2013-02-03 08:56, mayavi wrote:
>
> Sorry about the long delay, but I have had other system problems >:(
>
> However, I can now manually mount and access my 4TB RAID array lol!
> So, technically the initial problem has been solved.
>
> Thanks for all the help Carlos.

Welcome! Glad you solved it.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)