New answers tagged

1

I finally Did it. Many thanks for you supportive and helpful answers. i really appreciate it. What i did was to create new 4 drive Raid5 and used expand existing pool, then attach it with the old 5 drive raid5 pool , then I created new volume and map it with the host. then using windows 2008 disk management tool where this 4 drive new raid5 was appearing as ...


1

Per the documentation, p 393, you can only expand volumes, not pools: 8.4.8 Expanding a volume The IBM Storwize V3700 can expand volumes. This feature should be used only if the host OS supports it. This capability increases the capacity that is allocate d to the particular volume by the amount specified. To expand a volume, complete the ...


0

I found that I must build a new array and edit the boot record, I don't know how to do that, so I tried to install new OS and it's now migrating my data


-2

you can use dd to mesure the latency of a disk eg. dd if=/dev/zero of=/root/testfile bs=512 count=1000 oflag=dsync


0

Uh, never mind. The initial assumption was wrong: The hot spare didn't fail but another disk from the raid group failed during reconstruction. The array kept the disk alive as long as it could but some sectors were inevitably lost (double parity error on a single parity raid).


0

As this may help someone else in the future: Because the larger disks (2.5TB) had been added to an array that was first initialised with smaller disks (2TB), they are treated as a 2TB disk. I confirmed this with QNAP tech and replaced the 2.5TB disk with a new 2TB disk. The array has succesfully rebuilt and working fine. My next step is to replace the ...


-2

My 0.02.$ Since the server is already offline, run ddrescue on the drive that is about to fail, to clone it to another, sane drive. Then put the new, sane drive in the array instead. If the cloning is successful, you'll avoid the risk of seeing that drive fail during 2 rebuilds.


1

As we saw (I saw the problem in situ with Msegade), the problem was the resultant sda1 wasn't a partition with a filesystem within. When you disabled the RAID, sda had 1 partition that contained an image with its own (DOS) partition table: root@server:~# fdisk /dev/sda Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you ...


0

I think the whole thing is failing because you didn't remove the raid device md1 The exact steps are : 1. mdadm --stop raid_device 2. mdadm --remove raid_device 3. mdadm --zero-superblock component_device…


0

You don't. That's kinda the whole point of RAID: that the OS doesn't know that a single drive has failed, and can keep happily chugging along. I guess you could wire up something to the mdadm --monitor command to run a custom script on degrade events that did a mount -o ro,remount /dev/md/N, but that seems like putting lipstick on the pig. You should be ...


0

Here's THE best solution if going to a H700 isnt possible. Enable cache directly from the firmware. YOU MUST be running on a battery backup or if power goes out you could be hosed by enabling the cache. Below is a tutorial explaining the full process to do so. http://www.1337admin.org/windows-server/windows-server-2012-r2/dell-h200-raid-controller-speed-...


1

This does seem kind of round-about, do I have any better options? Your general idea is spot-on. I would personally suggest using ZFS with Solaris or FreeBSD, but mdadm might also work. Maybe though you don't get all the advantages I write about in this post, so take that as a disclaimer. This post will be quite long, I apologize in advance for the wall of ...


1

So long as the 2.5 Tb drives look like 2.0 drive to the array, you should be able to swap it.


0

I don't think you can replace with a smaller disk in any kind of raids. Instead you might need to move/copy your data from the functioning disk(s) to the new (smaller) disk and recreate your raid. On the other hand replacing with bigger disks is possible.


0

Providing a proper answer to your question goes way beyond the scope of a post here - it's way too broad. But the conclusion would be the same - assuming that redundancy is irrelevant, then the difference will depend on the nature of the workload (although as Andrew points out, it's a lot easier to mis-configure a RAID system than a single disk filesystem). ...


1

PERC cards are for local RAID. This isn't local. RAID config for your SAN is done via a Dell utility from the server, not from BIOS on the server utilizing the SAN. The LSI card is a host bus adapter, allowing the host (server) to talk to the SAN (storage) via external SAS connections. I suspect the LSI card is already working properly, but check device ...


0

If your file systems report they're intact, and data is not corrupted, you're lucky. Make a full backup NOW! This is always you should do first when you see your storage system is messed up, i.e. behaves strangely. I didn't get completely, which RAID technology you use. Intel does not make RAID chips, they offer either rebranded LSI MegaRAID or "Intel Matrix ...


0

it's unlikely your RAID is going to rebuild, unfortunately. you may try removing the spare, then sticking it back in after you've rebooted once. this MAY cause it to revisit and try to re-read. it's highly discouraged to use non-similar drives. In fact, we (my business) won't even manage systems which don't have matching drives (same mfr, same model), due ...


0

You must use swidth=10, for all partitions Modern linux systems can calculate and use sunit/swith sizes automatically. There is no need to calculate it manualy, in most cases.


1

We used to refurbish those machines. Things I'd try in that situation (unplug the machine from the power socket first): take out the motherboard battery and replace it clear the motherboard CMOS settings reseat the RAID card i.e. take it out and put it in again reseat the RAID backup battery connector try 'import foreign config' (F2 -> foreign config -> ...


0

Yes, the Raid controller seems to have died, I would open the case and get the part number from the existing controller and order a new one ( with a warranty) and replace the defective card. ( of course observing all of the safety precaution protocols pertaining to static sensitive devices.) Then after bringing the server back up configure the Raid with the ...


2

Not necessarily the root of my problem, but to get around the immediate problem of not booting, you have to clear the cache in the PERC BIOS. To clear the cache, you navigate to the screen that has the tree structure of disk groups and virtual disks. Then navigate by up-arrow until you are on the root of the tree structure, which will be the PERC H710 Mini ...


2

The critical lines are Jun 5 13:21:55 vault kernel: [154199.676477] blk_update_request: I/O error, dev sda, sector 954247056 Jun 5 13:21:55 vault kernel: [154199.676485] md/raid1:md126: sda: unrecoverable I/O read error for block 954244864 Jun 5 13:21:55 vault kernel: [154199.676488] ata3: EH complete Jun 5 13:21:55 vault kernel: [154199.676597] md: ...


1

Have you logged into the management interface? that'll tell you if you have any hardware issues or if those disks just aren't assigned to a VDISK yet or not - there's no other way really, just connect to it and see. By the way, don't be too fast to update the firmware on the 1040/2040's at the moment, HPE have been releasing some very buggy versions of ...


2

Maybe give this guys approach a try if you are brave (or desperate) enough: http://matrafox.info/how-to-get-md-raid-array-to-rebuild-even-if-read-errors.html His hack forces the badblocks to be reallocated on the "good" disk by writing nonsense to them. Which shouldnt matter for your data, since the sector in question is dead anyways, and the disks ...



Top 50 recent answers are included