Partitioner config issues

Hey there,

Thanks for your time and coming and checking out this post, I appreciate it.
I have a RAID card with a volume that is named the same as the volume it replaced (new array is larger). Now when booting it works most of the time. Once it booted into emergency mode and I thought was because I was using a volume with the same name and mountpoint something was being mistook for the old disk. I changed fstab using partitioner to mount the volume in question by UUID which worked for a while and then again today it booted into emergency mode.
I don’t really know where to look deeper into the issue than to look at partitioner which marks my drive with an *.

Thanks,

Josh

First please tell us which version of openSUSE this is about.

Suse 13.1 (Bottle)

I was thinking of upgrading to 13.2 but figured I should take a closer look at this first.

Also what kind of RAID a true hardware RAID is transparent to the OS but FAKE (BIOS assisted) is not. Many "cards: these days are not true RAID but FAKE RAID. The makers hid the fact that they sell 50 cent chips often like on the mother board for hundreds of dollars. Talk about a racket :X

And maybe give us some information about what the system thinks the partitioning is:

su -c 'fdisk -l'

And because you are new here:
Please use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.

Hey there I have an LSI card, I would hope it’s a decent controller and not a cheap chip of a mobo. It was on sale though… It’s SAS so I am fairly confident it’s a real RAID, transparent to the OS.

Disk /dev/sda: 60.0 GB, 60018253312 bytes, 117223151 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 label type: dos
Disk identifier: 0x7caba60e

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048     4208639     2103296   82  Linux swap / Solaris
/dev/sda2   *     4208640    88100863    41946112   83  Linux
/dev/sda3        88100864   111218687    11558912   83  Linux

Disk /dev/sdb: 3000.0 GB, 2999988518912 bytes, 5859352576 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 label type: dos
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb4               1           1           0+  ee  GPT

Disk /dev/sdc: 1000.0 GB, 999989182464 bytes, 1953103872 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 label type: dos
Disk identifier: 0x000ebc40

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048  1953103871   976550912   83  Linux


That should help. It seems fine. One day after I replaced the RAID volume for a larger set I booted into emergency mode till I edit my fstab.

Thanks again!

This looks as a “normal” disk to Linux. Thus when there is a RAID, Linux does not know about it.

BTW, you used the CODE tags, but forgot to copy/paste ALL that is asked for. Both prompts and the command are missing.

You story in post #1 above is a bit vague to me, but as you talk about changing things in /etc/fstab, we most probably need

cat /etc/fstab

And to check that against what the system detected:

ls -l /dev/disk/*

Lots of LSI stuff want to give part numbers??

If it is true hardware RAID it requires no drivers but you may need or have supplied a configuration utility. Note also that you may need to reinstall things once configured since it may change things on the drives which could wipe data.partitions.

Hmm SAS do you also have SAS drives I guess??

Hey sorry for letting this go dead. No SAS disks, just SAS to 4xSATA. When it works it’s great. What are these configurations?Sorry not very knowledgeable about drivers in SuSE