OMV does not boot when all RAID drives are connected

Zitat von jonni

I can not put in new commands nor see any progress

The there is a serious problem somewhere as you should be back at this root@nas-Jonathan:~# so that you run cat /proc/mdstat

Do you have a backup of your data?

Zitat von jonni

Do you think there is no realistic chance of getting it back

Something is wrong, what, I don't know, the --readwrite option should put you back to the command prompt and that is done instantaneously after executing it.

The only other option at this stage is to download and create then boot with a systemrescuecd the issue is either hardware related i.e. your m'board, sata cables, power supply, or the drives themselves. The systemrescuecd isolates OMV from the equation with that you could test each of drives using the smartmontools.

The alternative is you start from again, disconnect the drives, reinstall OMV, connect each drive one at a time and wipe it, if you connect all the drives together the probability is it will detect the raid signatures on the drives.

TBH I don't know what else to suggest, it's as if the machine and/or OMV is frozen.

I'm sorry but I am somewhat at a loss as to why you have reposted back here after five days, I suggested you use a systemrescuecd to run commands from the cli in an attempt to ascertain what might be wrong. After suggesting that I was waiting for feedback, to proceed, but as I said this could be hardware related.

Zitat von jonni

I have checked all drives with smartctl and did not find any errors

How, where, long, short, do you know what specific errors you're looking for

Zitat von jonni

I then found the following link: https://unix.stackexchange.com…shed-linux-md-raid5-array

I connected only 3 out of 4 RAID drives and used the following command

I used this once on here with a user, this is a last resort option as it can lose the data on the array, in that case it didn't work and he had to start again anyway.

Going back to #1 you removed one of the drives and the system boots, this was an error on my part as this thread should have stopped there, the error you posted in there suggests there is a hardware problem. The use of the systemrescuecd along with the m'boards BIOS may have been enough to locate the issue.

Removing any drive from an mdadm causes the array to go inactive when it's booted, because it is software mdadm knows a drive is missing, it knows what drive, but it doesn't know why.

By 'pulling' a drive from your system you had no idea if that was the drive causing the system not to boot, it could be one of the other three, it could be another problem with the m'board.

If you want confirmation regarding the error you posted in #1 have a look here

Raid is not my thing and I'm coming in the middle so;

Zitat von jonni

If it is of any help I can post the results of smartctl --atributes -H /dev/sdX as well.

The attributes to look at, for each spinning drive, are:

SMART 5 – Reallocated_Sector_Count.

SMART 187 – Reported_Uncorrectable_Errors.

SMART 188 – Command_Timeout.

SMART 197 – Current_Pending_Sector_Count.

SMART 198 – Offline_Uncorrectable.

The following is usually related to cabling or interfaces, but it's worth mentions becuase an array may kick a drive out with CRC errors.

SMART 199 - UltraDMA CRC errors
__________________________________________________________________________

Zitat von jonni

If you would tell me that using the mdadm --create command I have ruined my array anyways, I will just go ahead and do this:

I don't understand this. Have you ran mdadm --create ?

**Edit:** Also to confirm - you stay you've tested each drive in the array, with a SMART LONG drive test, correct? smartctl -s on -t long /dev/sd?

Zitat von jonni

My only reason why I have not given up yet is the fact that I can actually see the RAID in the OMV gui again, where it has not shown up for weeks.

There is an option you could try before going down the complete testing route, which will take time.

Recreate/rebuild OMV on a USB flash drive or small hard drive, disconnect the data drives, clean install, update, shutdown, then connect all the data drives, the new install should pick up the array from the drive signatures. If that failed then you're back to testing and the systemrescuecd.

Based on what I'm seeing /dev/sdd is probably the one being kicked out of the array. And this is speculation on my part but,,,

It looks like you may have an actual hardware problem. SMART 199 is, typically, associated with a bad SATA/SAS cable, intermittent contact at hard drive SATA connections at either end of, or a hardware interface issue (one of the drive's SATA interface card) or the motherboard's drive controller.

While more pronounced on one drive (/dev/sdd) you have CRC's on ALL drives which is something I haven't seen before. You could try replacing all cables. That's the cheapest route - they're relatively low cost on E-bay.

However, statistical probability suggests that all cables and all interface boards would not go bad at the same time. (Unless there was a power surge or a lightening strike.) The only thing ALL drives have in common is the drive controller. If the controller is integrated into the motherboard, that's not a good state of affairs....
________________________________________________

Zitat von jonni

t recognizes my newly created RAID as shown in #25, but I can not access any data.

I'm going to assume geaves walked you through mounting the array on the command line. With the array mounted, can you navigate to the array, into it's file structure? (If you're not comfortable with navigating on the Linux command line, Midnight Command or WinSCP might be helpful.)

Zitat von crashtest

I'm going to assume geaves walked you through mounting the array on the command line

Nope, I've actually given up on this, why;

1) mdadm --create -> bad idea and should only ever be used as a last resort on the basis it can cause data loss

2) reinstall on new hardware and connect all data drives did that happen -> no, we're still using the same drives from the mdadm --create

could try mount -a which will probably fail or mount /dev/md127 /srv this will most likely throw an fs error

Zitat von geaves

could try mount -a which will probably fail or mount /dev/md127 /srv this will most likely throw an fs error

jonni

If the array can't be mounted on the command line, in my opinion, it's over. You could try a Live Distro like Knoppix. It wouldn't hurt to try, but I doubt that you'll be able to pull anything off of the array after running the "create" command. Even if you could pull something off of the array, you'd need a destination drive/array to store data as it spools out.

With CRC's on all drives, I'd wonder how long that's being going on. Was it a recent event or over a longer period of time? If you had E-mail reports set up, as recommended in the User Guide, you'd have been aware of the problem as it started to develope. To avoid getting in a situation like this again, you might entertain 100% backup, perhaps even setting up an SBC or an old workstation as a Backup Server. (Your call.)

I'll get out of this thread (and out of geaves business and go back to minding mine) but, on a departing note, I'd look really hard at your motherboard before trusting it with another (data filled) array.

Sorry that I don't have more to offer.