search for: hdc3

...ive raid1 hdc1[1] hda1[0] 104320 blocks [2/2] [UU] What happens with md1 ? My dmesg output is: [root at server admin]# dmesg | grep md1 Kernel command line: ro root=/dev/md1 rhgb quiet md: created md1 raid1: raid set md1 active with 1 out of 2 mirrors md: md1 already running, cannot run hdc3 md: md1 already running, cannot run hdc3 EXT3-fs: md1: orphan cleanup on readonly fs EXT3-fs: md1: 4 orphan inodes deleted md: md1 already running, cannot run hdc3 EXT3 FS on md1, internal journal [root at server admin]# Thanks for any help !!! roberto -- Ing. Roberto Pereyra ContenidosOnline...

...255/63, UDMA(133) hda: cache flushes supported hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14 hda15 > hdc: max request size: 1024KiB hdc: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63, UDMA(133) hdc: cache flushes supported hdc: hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 hdc12 hdc13 hdc14 hdc15 > ACPI: PCI Interrupt 0000:00:10.3[D] -> GSI 21 (level, low) -> IRQ 21 PCI: Via IRQ fixup for 0000:00:10.3, from 10 to 5 ehci_hcd 0000:00:10.3: VIA Technologies, Inc. USB 2.0 ehci_hcd 0000:00:10.3: new USB bus registere...

....  Within this I loaded Suse 10 as a guest OS, the config file is as below: kernel = "/boot/vmlinuz-2.6.11.12-xenU" memory = 100 name = "suseguest" nics = 1 vif= [''mac=aa:00:10:00:00:10, bridge=xen-br0''] ip = "192.168.2.2" disk = [''file:/dev/hdc3,hdc3,w''] root = "/dev/hdc3 rw" extra = "3" Boots and allows me to login .. then I tried to ping the dom0 from domU and it didnt work. Heres the ifconfig from domU: eth0 Link encap:Ethernet HWaddr AA:00:10:00:00:10 inet addr:192.168.2.2 Bcast:192.168....

Hi. I'm using e2fsprogs 1.23 on a Roswell system with a patched 2.4.7 kernel (using patch ext3-2.4-0.9.5-247) and am trying to create an ext3 filesystem whose journal is located on another device. The incantation I'm trying is: mke2fs -j -J device=/dev/hdc2 /dev/hdc3 I keep getting an error along the lines of "mke2fs: Journal superblock not found". I've tried creating different types of filesystems (ext2, ext3, etc.) on the target device for journaling, but this didn't seem to change anything. Could someone point out the error or my ways?...

...Bloques de 1K Usado Dispon Uso% Montado en /dev/md1 75442944 1334492 70276152 2% / /dev/md0 497765 16029 456037 4% /boot none 241588 0 241588 0% /dev/shm cat /proc/mdstat Personalities : [raid1] md1 : active raid1 hdc3[1] hda3[0] 76646016 blocks [2/2] [UU] md0 : active raid1 hdc1[1] hda1[0] 513984 blocks [2/2] [UU] cat /etc/fstab # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/md1 / ext3 defaults 1 1 /dev/md0...

...maximum available idle IO bandwith (but not more than 200000 KB/sec) for reconstruction. md: using 128k window, over a total of 6144768 blocks. md: resuming recovery of md3 from checkpoint. md: md3: sync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:hda3 disk 1, wo:0, o:1, dev:hdc3 Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070321/58dbd3c5/attachment.html>

I am trying to create an additional domain and have created a configuration file based on the examples. When I try to boot the domain, it eventually hits a Kernel panic, as follows: Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none

Hi, I have a 20GB partition on a hard disk that just developed bad blocks. Fortunately, I had backups for the most important data on it, but I'd like to recover some files that were too large to backup. When running 'e2fsck /dev/hdc3', I get the following message: e2fsck 1.27 (8-Mar-2002) Group descriptors look bad... trying backup blocks... e2fsck: Invalid argument while checking ext3 journal for / I already made a backup copy of the whole partition. I also tried to copy the partition on a new disk and run e2fsck on the n...

...nds to correct. swapoff -a raidstop /dev/md3 mkraid /dev/md3 --really-force swapon -a And then I get a proper ourput for /proc/mdstat, but when I reboot /proc/mdstat again reads as below, with md3 [0] [1] reversed. [root]# cat /proc/mdstat Personalities : [raid1] md3 : active raid1 hda3[0] hdc3[1] 1000320 blocks [2/2] [UU] md1 : active raid1 hdc1[1] hda1[0] 1953408 blocks [2/2] [UU] md2 : active raid1 hdc2[1] hda2[0] 1953408 blocks [2/2] [UU] md5 : active raid1 hdc5[1] hda5[0] 1953408 blocks [2/2] [UU] md6 : active raid1 hdc6[1] hda6[0] 71295232 blocks [2...

...rect Used/Available info. root@debserver:~# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda1 1981000 608800 1269788 32% / /dev/hda3 2858128 1032622 1677708 38% /var /dev/hdc1 794118 445793 307301 59% /usr /dev/hdc3 189335 159760 19798 89% /home root@debserver:~# df Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda1 1981000 608800 1269788 32% / /dev/hda3 2858128 1032636 1677694 38% /var /dev/hdc1 794118 445793...

...g. the raid arrays, I always create the boot partitions in hda1 and hdc1 and make them primary...maybe I am doing wrong by giving them 200mb instead of 100mb but I do it in the other 2 raided systems I run and no probs. I then create the sys partitions: hda2 and hdc2 lastly, the swaps as hda3 and hdc3 ........................... grub: here's what I did/do and here's the results: linux rescue chroot /mnt/sysimage /sbin/grub-install /dev/hda ...the complaint/result: /dev/md0 does not have any corresponding drive I have tried: /sbin/grub-install /dev/hda (as a stab in the dark) it giv...

I have a CentOS 4.2 system that was set up VERY quickly following the demise of its former life as a CentOS 3 server - you don't want the full story, but it had to be done quickly to get a company up and working following a slight disaster involving an electrician, a portable appliance safety tester and a pulled power cable - anyway, here's where I am at... Everything is running fine but

...1 GB, 46115758080 bytes 255 heads, 63 sectors/track, 5606 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 1 2295 18434587 83 Linux /dev/hdc2 2296 4207 15358140 83 Linux /dev/hdc3 4208 5542 10723387+ 83 Linux /dev/hdc4 5543 5606 514080 f Win95 Ext'd (LBA) /dev/hdc5 5543 5606 514048+ 82 Linux swap And mount -t ext3 /dev/hdc1 /audio gives mount: wrong fs type, bad option, bad superblock on /dev/hdc1,...

...es : 1 Working Devices : 2 Failed Devices : 1 Spare Devices : 1 Checksum : 2652883e - correct Events : 0.15217 Number Major Minor RaidDevice State this 2 33 0 2 spare /dev/hde 0 0 22 3 0 active sync /dev/hdc3 1 1 0 0 1 faulty removed 2 2 33 0 2 spare /dev/hde Any suggestions on getting this pair talking properly? Thanks Nigel

...nighltly source too :-). I''ve tired Keir''s suggestions but to no avail... I''m fairly new to linux, but not to unix. I''m just don''t know what to try next. Suggestions? Here''s my setup: Device Boot /dev/hdc1 /dev/hdc2 FreeBSD /dev/hdc3 FC3 Boot (ext3fs) /dev/hdc4 Extended /dev/hdc5 FC3 Root (ext3fs) /dev/hdc6 FC 3 swap I''ve also got other partitions. Grub.conf: default=0 timeout=5 splashimage=(hd1,2)/grub/splash.xpm.gz hiddenmenu title Xen 2.6 / XenLinux kernel /xen...

Hi I have mailed about this previously, but back then it was not really confirmed, so I have let it be at that. Anyhow, problem is that for some reason 2.5/2.6 ext3 with HTREE support do not like what perl-5.8.0 does during installation. It *seems* like one of the temporary files created during manpage installation do not get unlinked properly, or gets into the hash (this possible?) and cause

...rs/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 13 104391 fd Linux raid autodetect /dev/hdc2 14 27651 222002235 fd Linux raid autodetect /dev/hdc3 27652 30201 20482875 fd Linux raid autodetect /dev/hdc4 30202 30401 1606500 5 Extended /dev/hdc5 30202 30392 1534176 82 Linux swap Disk /dev/md0: 106 MB, 106823680 bytes 2 heads, 4 sectors/track, 26080 cylinders Units = cylinders...

...one of my servers in a similar setup to yours: > > $ cat /proc/mdstat > Personalities : [raid0] [raid1] > md1 : active raid1 hdc1[1] hda1[0] > 248896 blocks [2/2] [UU] > > md2 : active raid1 hdc2[1] hda2[0] > 995904 blocks [2/2] [UU] > > md3 : active raid1 hdc3[1] hda3[0] > 2000000 blocks [2/2] [UU] > > md5 : active raid1 hdc5[1] hda5[0] > 38081984 blocks [2/2] [UU] > > md6 : active raid1 hdc6[1] hda6[0] > 38708480 blocks [2/2] [UU] > > unused devices: <none> > > $ df -h > Filesystem S...

...6304 2958 3021 50% /usr6 /dev/hdb2 3153 1860 1129 63% /usr /dev/hdb3 3160 2408 589 81% /usr8 /dev/hdc1 2016 212 1701 12% /oldroot /dev/hdc2 4032 3542 284 93% /usr5 /dev/hdc3 4032 3464 363 91% /usr2 /dev/hdc4 18771 13193 4625 75% /usr4 tried redoing the one where I got the core dump message [root@joker /root]# tune2fs -j /dev/hda4 tune2fs 1.25 (20-Sep-2001) The filesystem already has a journal. Tried a couple of m...

Dear All, I would like to get community's feedback with regard to RAID1 ( Software or Hardware) implementations with asterisk. This is my setup Motherboard with SATA RAID1 support CENT OS 4.4 Asterisk 1.2.19 Libpri/zaptel latest release 2.8 Ghz Intel processor 2 80 GB SATA Hard disks 256 MB RAM digium PRI/E1 card Following are the concerns I am having I'm planing to put this asterisk