similar to: RAID Resynch...??

Dear all, Right out of the blue glusterfs is not working fine any more every now end the it stops working telling me, Endpoint not connected and writing core files: [root at tuepdc /]# file core.15288 core.15288: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from 'glusterfs' My Version: [root at tuepdc /]# glusterfs --version glusterfs 3.2.0 built on Apr 22 2011

Hello, I have a RAID5 array on my CentOS 5.6 x86_64 workstation which "suddenly" failed to work (actually after the system could not resume from a suspend). I had recently issues after moving the workstation to another office, where one of the disks got accidently unplugged. But the RAID was working and it had reconstructed (as far as I can tell) the data. After I replugged the disk,

Hello, I had a scientific linux 3.0.4 system (rhel compatible), with 3 ide disks, one for / and two others in linear raid (250 gb and 300 gb each). This system was obsoleted so i move the raid disks to a new scientific linux 3.0.7 installation. However, the raid array was not detected ( I put the disks on the same channels and same master/lsave setup as in the previous setup). In fact

I am running software RAID1 on a somewhat critical server. Today I noticed one drive is giving errors. Good thing I had RAID. I planned on upgrading this server in next month or so. Just wandering if there was an easy way to fix this to avoid rushing the upgrade? Having a single drive is slowing down reads as well, I think. Thanks. Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb

I just installed CentOS 5.4 64 bit release on a 1.9ghz CPU with 8gB of RAM. It has 2 Western Digital 1.5TB SATA2 drives in RAID1. [root at server ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/md2 1.4T 1.4G 1.3T 1% / /dev/md0 99M 19M 76M 20% /boot tmpfs 4.0G 0 4.0G 0% /dev/shm [root at server ~]# Its barebones

this has never happened to me before, and I'm somewhat at a loss. got a email from the cron thing... /etc/cron.weekly/99-raid-check: WARNING: mismatch_cnt is not 0 on /dev/md10 WARNING: mismatch_cnt is not 0 on /dev/md11 ok, md10 and md11 are each raid1's made from 2 x 72GB scsi drives, on a dell 2850 or something dual single-core 3ghz server. these two md's are in

Received the following message in mail to root: Message 257: >From root at desk4.localdomain Tue Oct 28 07:25:37 2014 Return-Path: <root at desk4.localdomain> X-Original-To: root Delivered-To: root at desk4.localdomain From: mdadm monitoring <root at desk4.localdomain> To: root at desk4.localdomain Subject: DegradedArray event on /dev/md0:desk4 Date: Tue, 28 Oct 2014 07:25:27

Sorry, this is going to be a rather long post...Here's the situation; I have 4 IDE disks from an old snap server which fails to mount the raid array. We believe there is a controller error on the SNAP so we've put them in another box running CentOS 5 and can see the disks OK. hda thru hdd looks like this Disk /dev/hdd: 185.2 GB, 185283624960 bytes 255 heads, 63 sectors/track, 22526

I have been reading lots of stuff but trying to find out if a raid10 2drive setup is any better/worse than a normal raid 1 setup....I have to 1Tb drives for my data and a seperate system drive, I am only interested in doing raid on my data... So i setup my initial test like this.... mdadm -v --create /dev/md0 --chunk 1024 --level=raid10 --raid-devices=2 /dev/sdb1 /dev/sdc1 I have also read

So I have been playing with a RAID 10 f2 ( 2 disks far layout) setup...thanks for all of the advice..Now I am playing with the format and want to make sure I have it setup the best that I can, my raid was built using the raid 10 option with 2 disks with the layout=far, chunk size 512....now I read all of the docs I could find about format and stride and stripe size and this is what i came up

Hi all. I have currently a server: cat /etc/redhat-release CentOS release 5.7 (Final) uname -a Linux host.domain.com 2.6.18-274.18.1.el5 #1 SMP Thu Feb 9 12:45:44 EST 2012 x86_64 x86_64 x86_64 GNU/Linux I have there a filesystem mounted: /dev/vg0/paczki /home/paczki-workdir ext4 defaults,noatime 0 0 on which df gives strange output: LANG=C df -h

I am trying to install CentOS 4.6 to a pair of 750GB hard drives. I can successfully install to either of the drives as a single drive, but when I try to use both drives and mirror the partitions, I start having problems. Anaconda crashes as it is trying to format the drives. This is what I'm trying to create: /dev/md0: 200MB, /boot /dev/md1: 2GB, swap /dev/md2: rest of the

Hello. I have several systems (CentOS 3 and CentOS 4) with software raid and I've observed a difference in the raid state: In CentOS 3 systems we find that mdadm --detail /dev/md* show: .............. Version : 00.90.00 Creation Time : Fri Apr 16 14:59:43 2004 Raid Level : raid1 Array Size : 20289984 (19.35 GiB 20.78 GB) Device Size : 20289984 (19.35 GiB 20.78 GB)

I have several Centos 8 machines that I update and every now and again I will go through and update all of them and one of them will get a slow mirror, like downloading the kernel at 50kb etc. With the newer version I am unable to figure out how to force it to update the mirror list and hopefully change to a faster mirror. I have searched but must not be using the right verbiage since I am unable

Hello, i have a little problem. Our server has an broken RAID. # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sda1[2](F) sdb1[1] 2096064 blocks [2/1] [_U] md2 : active raid1 sda3[2](F) sdb3[1] 1462516672 blocks [2/1] [_U] md1 : active raid1 sda2[0] sdb2[1] 524224 blocks [2/2] [UU] unused devices: <none> I have remove the partition: # mdadm --remove

Hi. I just noticed I had a CentOS 5.3 system that I updated to CentOS 5.5 a few days ago, and I just ran "yum -y update" again to get the latest kernel, and I just noticed it still has the old 2.6.18-128 kernel instead of the new 2.6.18-194.17. What gives? /etc/grub.conf points at 2.6.18-194.17, but when I reboot, 2.6.18-128 comes up. Any suggestions? Thanks, -at myserver# yum -y

So I am trying to rebuild this source rpm from fedora 10, shutter-0.85.1-1.fc10.src.rpm -its a screen capture application ( http://shutter-project.org/ ) that I have been unable to find in any repos, although it is in the fedora repos. Thought I would give it a go and try to rebuild the rpm, so here is the error that I am getting: + desktop-file-install --delete-original --dir

On Sat, Jun 20, 2020 at 4:08 AM Tom Bishop <bishoptf at gmail.com> wrote: > +1 Streams is not for a production workload, if I wanted that I can easily > deploy an Arch instance if I want or need a rolling distro (it's not Redhat > etc but still). If Redhat wanted CentOS to be released near the same time > line they could help make that happen, although that wouldn't be

I know of the issue using vmware server 2.0.2 and centos 5.4, but is their any reason not to use the .rpm install of for centos? I have always used the .tar file but this time used the rpm and it appeared to install and not crash. I went ahead and did the glib correction but I was wondering if using the rpm was not the rght thing to do, Thanks. -------------- next part -------------- An HTML

Hi, Does anyone know of a good program for doing RDP to windows servers on C-7? The "Remote desktop viewer" program that comes with C7 is not reliable for me. I frequently have multiple long running RDP sessions and the keyboard will stop responding. The only way I can find to get it started again is to restart the program and login to the servers again. In addition, I cannot find a