similar to: CentOS-6.8 fsck report Maximal Count

On Thu, March 9, 2017 09:46, John Hodrien wrote: > On Thu, 9 Mar 2017, James B. Byrne wrote: > >> This indicated that a bad sector on the underlying disk system might >> be the source of the problem. The guests were all shutdown, a >> /forcefsck file was created on the host system, and the host system >> remotely restarted. > > fsck's not good at finding

CentOS-6.6 virt-manager 0.9.0 I have cloned a template server with a 32GB virtio HDD already defined and am attempting to add additional virtio disks. The basic cloned system boots without error. If I create a virtio disk with 32000/32000 megabytes I can add it and the system reboots; providing that I do not first create a partition: fdisk -l /dev/vg_vhost03/lv_vm_inet11.harte-lyne.ca_03

On Fri, March 10, 2017 11:57, m.roth at 5-cent.us wrote: > > Looks like only one sector's bad. Running badblocks should, > I think, mark that sector as bad, so the system doesn't try > to read or write there. I've got a user whose workstation has > had a bad sector running for over a year. However, if it > becomes two, or four, or 64 sectors, it's replacement

On Tue, Mar 14, 2017, 7:41 AM James B. Byrne <byrnejb at harte-lyne.ca> wrote: > On Fri, March 10, 2017 11:57, m.roth at 5-cent.us wrote: > > > > > Looks like only one sector's bad. Running badblocks should, > > I think, mark that sector as bad, so the system doesn't try > > to read or write there. I've got a user whose workstation has > > had

Dear all, I'm trying to find a way to automate checkdisk every 1 month on a weekend. in other words i want checkdisk to run every saturday morning. i can of course change the default mount/count though that wont let me control WHEN it will happen. so i need your expert opinion with the following if possible: 1. reboot into single user mode 2. start checkdisk for all disks 3. once done,

About two weeks ago i was whining about an inode that got lost, now i'm going to whine more about strange things happening here. A matroxfb just oopsed on me (thats not strange), the machine got unusuable, so i logged in from another and got the idea to touch /forcefsck. Upon reboot, fsck said that some inodes are in use but have dtime set and that some files are illegal sockets. Now this

This morning I discovered this in the logwatch report for our external MX backup host. STARTTLS: write error=syscall error (-1), errno=32, get_error=error:00000000:lib(0):func(0):reason(0), retry=99, ssl_err=5: 206 Time(s) I also see many entries similar to this: 8: fl=0x802, mode=140777: SOCK inet04.mississauga.harte-lyne.ca/34091->(Transport endpoint is not connected): 1 Time(s)

If I have the 6th column in fstab (the pass column) set to 0, does that mean disk checks will never be forced at boot regardless of anything like File System State, Mount Count, and Check Interval on the file system itself, or are there exceptions to this? I know `man fstab` says: If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does

Am 25.11.2014 um 21:39 schrieb James B. Byrne: > This morning I discovered this in the logwatch report for our external MX > backup host. > > > STARTTLS: write error=syscall error (-1), errno=32, > get_error=error:00000000:lib(0):func(0):reason(0), retry=99, ssl_err=5: 206 > Time(s) > > > > I also see many entries similar to this: > > > > 8:

I appear to have a broken filesystem on this box to the point where I am probably going to rebuild the system since I have lost trust in it.... I was wondering if there was any reasonable postmortum work I could do on it before it gets rebuilt. History is that the laptop has a much mauled partition set on it - initially it came with 100% win2k, I then shrunk that and added linux (a RH71 install

VFS: brelse: Trying to free free buffer buffer layer error at fs/buffer.c:1182 Pass this trace through ksymoops for reporting Call Trace: [<c01468f0>] [<c0146aa9>] [<c0146b57>] [<c0146b84>] [<c0175a17>] [<c023cbfa>] [<c023d2f1>] [<c0175c90>] [<c01728e9>] [<c01ad7d6>] [<c014d215>] [<c0154c68>] [<c0154f79>]

Hello everyone, It seems like we have a corrupted /etc/mtab file and I just wanted to check that my plan of action is correct. df -k returns: df: cannot read table of mounted file systems: No such file or directory ls -la mtab: ?--------- ? ? ? ? ? mtab messages full of errors: EXT3-fs error (device cciss/c0d2p1): ext3_lookup: unlinked inode 847444 in dir #846977 I

Sep 13 12:18:56 sfe fsck: /dev/VolGroup00/LogVol00 is mounted. Sep 13 12:18:56 sfe fsck: e2fsck: Cannot continue, aborting. Sep 13 12:18:56 sfe rc.sysinit: Checking root filesystem failed I had updated the box a few days ago but I had not rebooted with the new kernel. After the reboot, I get the root filesystem is not marked clean message and also that it was not mounted read-only. I supplied

Hi, My Centos 5.2 server (5.1 suffered the same problem as well) has a logical volume on a RAID 10 array (4 SATA harddisks on a Highpoint RR2310 controller). /etc/fstab has an entry for this array as below /dev/raid_vg0/raid_lv0 /mnt/raid ext3 defaults 0 0 Normally it works OK. But, file system of "this volume" once in a while goes "read only"

Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25" and a 3.5" drive, both are plugged in, but in the BIOS, all I see is the 3.5". Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor

This may or may not be ext3 related but I am trying to find any pointers which might help me. I got a number of HP Proliant DL380 g5 with a P400 controller and also two qla2400 cards. The OS is RedHat EL4 U5 x86_64. Every time during reboot these systems panic after the last umount and I believe before the cciss driver is getting unloaded. The last messages I am able to see are: md: stopping

Hi, I have set-up the ups shutdown feature provided by Red Hat /etc/rc.d/init.d/halt script, which will issue a "upsdrvctl shutdown" command just before powering off the system. It appears that this command fails as if the driver is not available. I wonder whether the usb driver / stack is still available at this very late stage ? If not available then does it mean one cannot

A user running gnome came in this morning, clicked on the application menu... and it was much shorter than he expected. He could get to firefox, and googled about refreshing that... and found something that told him to reboot. And that's it: I cannot get X up, at all. I just get the "oh, no, something failed, please log out and try again". Fully updated CentOS 7, [AMD/ATI] Oland

Hey, I currently have a box serving as a firewall (running iptables) and packet shaper (using tc / tcng''s tcc compiler) to shape a large amount of inbound and outbound traffic to my data center. Whilst I can perform shaping functions using HTB, I need to also provide an absolute (to the nearest few 100kb/s) bandwidth usage maximum. As an example I might have 200MBit/sec

Hi everybody, I'm using Lubuntu 14.04 on an old desktop PC with a NVIDIA GeForce 7600 GS and a screen of 19 inches. The maximal resolution of my screen with Nvidia drivers is 1280x1024. (In particular, I use the Nvidia 331.89 driver) With Nouveau driver, the maximal resolution falls to 1024x768. Is there a solution for increasing the maximum resolution with Nouveau ? Best regards,