similar to: CentOS 4.3 occasionally locking up accessing IDE drive

Me again. The ASUS P5N32-SLI motherboard in my new machine has dual NICs but CentOS has only detected one of them. I've tried rebooting with the network plugged in only to the second one, but kudzu still doesn't find it. Any suggestions?

Hi all, I'm trying to troubleshoot my way thru a ACPI-issue on several machines with the Asus P5N32-E SLI motherboard (S775, Nvidia 680i chipset) http://www.asus.com/products.aspx?l1=3&l2=11&l3=397&l4=0&model=1459&modelmenu=1 This is CentOS 4 x86_64, and appears on all tested kernels, including kernel-smp-2.6.9-67.0.4.EL My symptoms are that the machine won't

Hi all, Same system as my previous mail - Asus P5N32-E SLI motherboards, CentOS 4 x86_64. The kernel-supplied forcedeth driver works in kernel-smp-2.6.9-55.0.9.EL (both with and without acpi=off), but after upgrading to kernel-smp-2.6.9-67.0.4.EL, networking does not start. After trying dhcp, ifconfig reports 17 dropped TX packets (all other counters are empty). Ethtool reports the same

I am having problems with silent data corruption on (some) drives connected to an MCP55 SATA controller. I have two servers, both running RELENG_7_0/amd64. One has the 570 Ultra chipset, the other has 570 SLI. Both chipsets have the MCP55 SATA controller. The server with 570 Ultra chipset has a bunch of older 250GB SATA-150 drives hooked up to the MCP55 controller and it is working just fine.

Hello After compiling and booting a RH 8.0 box with a 2.4.19 vanilla kernel i've started to experience some problems on my /home partition, (i/o errors on 2 files). After rebooting the machine failed the to mount /home and dropped me in the recovery shell. The fsck is still running after 9 hours. The system is a dual athlon MP with 1Gb ram and ASUS MB. the /home patrition is mounted on 3 120

I am reporting this on the advice of the Fedora Users Mailing List Member. This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. I am reporting this per suggestions made to me on the Fedora Users Mailing List. The following is the mailing list exchange: On 09/18/2014 07:01 PM, Robert Nichols wrote: > On

I was playing around with btrfs, and did a mkfs.btrfs on one of my partition. Mistakes, it was my data partition (ext3 based). I have not yet mounted the device, but the mkfs.btrfs continued to completion. Is it possible to salvage my ext3 filesystem? Anyway to reverse the effect of mkfs.btrfs? Thank you for your help/answer. -- Regards, Peter Teoh

On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. > > I am reporting this per suggestions made to me on the Fedora Users Mailing List. I would

I've been having an extremely hard time using the on board SATA controller on my nvidia based board. I have two 160gig Maxtor SATA drives attached to the on board controller, setup as software raid0. The problem is the array is extremely unreliable, where I'm getting constant I/O errors like: sd 0:0:0:0: SCSI error: return code = 0x00040000 end_request: I/O error, dev sda, sector

Hi List, i'd like to share with you what happened yesterday. Kernel 2.6.36.1 ocfs2-tools 1.6.3 (latest). I had an old OCFS2 partition created with a 2.6.32 kernel and ocfs2 tools 1.4.5. I unmounted all partitions on all nodes in order to enable discontig-bg. I then used tunefs to add discontig-bg, inline-data and indexed-dirs. During indexed-dirs tunefs segfaulted and since then, fsck

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

Hi, I'm sending a series of patches implementing quota support into ocfs2-tools. It's the same as the original huge patch I've sent but now it's split as Joel asked. I've also realized that when disabling SPARSE feature, we should update quota information. That piece of code is missing, I'll implement it soon. Comments welcome. Honza

On Fri, Apr 21, 2023 at 03:35:01PM +0800, Joseph Qi wrote: > Hi, > Could you please share a reproducer? > Anyone could access & download the URL [1] (I wrote it in patch commit log) without register SUSE account. Please check attachment file, which I downloaded from [1] and modified under the BZ comment 1. The trigger method is also in comment 1, I copy here: ./defragfs_test.sh -d

When I try and run the mkfs.ocfs2 command after I have updated all of the other nodes in the cluster with the new node information in cluster.conf I am getting the following error: mkfs.ocfs2 -b 4k -C 32K -L "ocfs2" -N 4 /dev/sdb1 mkfs.ocfs2 1.4.4 Cluster stack: classic o2cb Overwriting existing ocfs2 partition. mkfs.ocfs2: Could not create domain while initializing the dlm As this is

The `lofiadm'' man page describes how to export a file as a block device and then use `mkfs -F pcfs'' to create a FAT filesystem on it. Can''t I do the same thing by first creating a zvol and then creating a FAT filesystem on it? Nothing I''ve tried seems to work. Isn''t the zvol just another block device? -- -Gary Mills- -Unix Group-

Hi, this is the next version of quota support for quota tools. I've addressed all the comments of Tao, Joel and others. Sparse feature disabling also correctly updates quota information now and the patch is merged into the tunefs support patch. Honza

Hello group I added a new partition in fstab, and works without a problem. I used mkfs.ext3 to create the partition. My problem is that every 26 boots, the system tells that the partition have no been checked since 26 systems boots, ant start to check my new partition. This is a lot of time consuming, and always is in a bad time. There some way to do the check in a controlled time? i.e. do it the

Hello, I have a 1.3TB ext3 filesystem that has been in service for about 3 months. About 6 days ago the Emulex fibrechannel controller logged a SCSI error and the filesystem changed to RO. It appears that the filesystem instantly changes to RO and prevents the journal from working, therefore invalidating the filesystem. The filesystem was unmounted and a remount was attempted. The mount failed

With kernel 2.6.30-rc2-git6 and prior I am having problems mounting ext4 partitions after reboot. A successful mount looks like this: /dev/cciss/c0d0p8 on /squid-cache0 type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic) /dev/cciss/c0d0p9 on /squid-cache1 type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic) /dev/cciss/c0d0p10 on /squid-data type ext4

Hello! I''ve a ubuntu server running over a HVM DomU. After a hang, the domU doesn''t start again. The domU was not able to mount the virtual machine disk so I started with a live cd and I tried to mount the disk root part / with no success so I ran fsck.ext3 and it gave me input/output error in the domU and in dom0 the kernel says: Feb 14 18:22:28 scofield last message