New answers tagged

0

It was because of dead sectors on my sda drive. The solution was to create a partition without dead sectors. How to find what's wrong Go to /var/log/messages to figure out which partition isn't working and why. For example I had : md/raid:md0: read error not correctable (sector 25205280 on sda1); md0: unable to read partition table. That means your disk ...


-1

This could be a "bad sign", I'm not sure... But in our case the device "/dev/sdc1" was having problems as we could see with the command... fsck -c /dev/sdc1 TIP: If you are not worried about the contents of the disk use the fsck -y /dev/sdc1 command so that all corrections will be made automatically if necessary. You can use the command below to check ...


0

RAID: software VS hardware You didn't wrote which kind of RAID you are using. There's two main categories: Hardware RAID: the RAID stuff is managed by your hard drive controller and the devices shown in your Linux are an abstract of your array. Usually, there's a firmware accessible during the boot to configure the array (RAID 0, 1, etc...). The devices ...


0

The problem was occurring for the reasons below... The dracut documentation implies that any md raid arrays should be automatically assembled, and that the "rd.md.uuid" parameter should only be used if you only want certain arrays assembled as part of the boot process. It seems that in reality, the arrays are not assembled automatically, and ...


0

Is there a way to mount multiple hard drives to a single mount point? Probably not in the way that you want to. You can do all kinds of funny things, but this doesn't solve the problem you're trying to resolve. Let's say I run out of space on /home and decide to add an extra hard drive to the computer. How do I scale the space on a mount point? One ...


0

I was able to solve it by stopping the raid device with mdadm and creating a new linear raid containing only the first drives


1

Sorry, I did not intend my earlier comment as a chastisement, but more to raise awareness of the trap of using hardware RAID in small-scale settings. You're not the first one who has ended up in a bad situation like that, and I'm afraid you won't be the last one either. I was against comment length limit, so it ended up harsher than needed. dmraid supports ...


3

It all depends on how you set it up. With ten disks in RAID 1, you get a single disk capacity, with plenty of redundancy: if any 9 disks fail, the data is still there on the single remaining disk. This sounds weird but sometimes you see it as a mdadm RAID 1 for the /boot partition, while everything else is RAID 5/6/10 - which the bootloader might not know ...


3

This is a very common problem with old mdadm 0.90 metadata. This metadata is located somewhere at the end of the device, but not in the very last sector but at a 64K-aligned offset: The superblock is 4K long and is written into a 64K aligned block that starts at least 64K and less than 128K from the end of the device (i.e. to get the address of the ...


Top 50 recent answers are included