similar to: howto mark bad block with fsck?

Displaying 20 results from an estimated 10000 matches similar to: "howto mark bad block with fsck?"

2005 Oct 27
6
Mail Server
Hi, I need to setup a new mail server and before I got my feet wet or losing in the configurations jungle, I really need some advice from the gurus here for what the best software to used for the mailserver base on CentOS 4.x setup. The objective is, the mailserver will be easy to setup, maintained and have some 1. database backend for storing user info ( mysql? ) 2. spam and antivirus
2005 Oct 01
1
Need help on UFS driver
Hi, Does anyone have ufs driver modules for centOS 4.1 kernel 2.6.9-11.EL? I need this modules but don't want to border for recompile my kernel to get just ufs support. Can anyone point me where could I download this modules? Thanks In Advances. Regards, ijez
2005 Jul 30
2
Running another gnome or kde on virtual console
Hi, I'm still new in linux world and CentOS is my 2nd linux desktop I ever used ( have used it for month now, before using Ubuntu for 2 days ), so please gave me a little favor on it :) What I need to do is to have my virtual console that can also run gnome or kde, so I can have different windows on different virtual console. After googling, I found the qingy that just fit for my need. I
2008 Sep 03
0
HELP - RAC Cant fsck bad superblock
Hi All I just installed a 2 node ,10 r2 rac on centos Linux 4.6 My rac install was done by following Jeff Hunters document (excellent work!) http://www.idevelopment.info/ For storage I used openfiler with the iscsi protocol http://www.openfiler.com/ everything went perfect... to the letter, I gracefully shutdown the 2 nodes , then the openfiler appliance, when I went to start it back up,
2017 Mar 10
2
CentOS-6.8 fsck report Maximal Count
On Fri, March 10, 2017 9:52 am, Warren Young wrote: > On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: >> >> On Thu, March 9, 2017 09:46, John Hodrien wrote: >>> >>> fsck's not good at finding disk errors, it finds filesystem errors. >> >> If not fsck then what? > > badblocks(8). And I definitely will
2017 Mar 10
1
CentOS-6.8 fsck report Maximal Count
I get up around 0630, u can come anytime after that. I want to hit the range that morning but if I KNEW when you are arriving, I could plan around that... > On Mar 10, 2017, at 9:28 AM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: >> >> >> On Fri, March 10, 2017 9:52 am, Warren Young wrote: >>> On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at
2010 Jan 28
2
Advanced fsck?
Dear All My CentOS server got file system inconsistency , asking for "type Ctrl-D for normal boot or give root password for maintenance to run fsck manually". I tried for manually run fsck , as the followings : #fsck -s /dev/hda3 But after rebooting the server it will come back again at the similar prompt asking for "give root password for maintenance" . Can you please do me
2017 Mar 10
0
CentOS-6.8 fsck report Maximal Count
On Mar 10, 2017, at 9:28 AM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > > > On Fri, March 10, 2017 9:52 am, Warren Young wrote: >> On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: >>> >>> On Thu, March 9, 2017 09:46, John Hodrien wrote: >>>> >>>> fsck's not good at finding disk
2017 Mar 14
2
CentOS-6.8 fsck report Maximal Count
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
2013 Apr 07
4
[BUG] btrfs.fsck failing to fix corrupted block
Hi there, I am newbie and recently started using btrfs. Now facing a weird problem. FWIW, I am on archlinux, kenel v3.8.0, having Btrfs v0.20-rc1. After an abnormal reboot, getting these errors while boot: systemd.fsck[289]: checking extents systemd.fsck[289]: checking fs roots systemd.fsck[289]: checking root refs systemd.fsck[289]: found 23728128 bytes used err is 0 systemd.fsck[289]: total
2017 Mar 10
3
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
2009 May 16
6
fsck file system is mounted
Hi, Is there a way to run fsck or any other program to check if there is drive problem. I don't want it repaired, now, but maybe later on. I can't shutdown the system and reboot in single user-mode. All suggestions are welcomed. -- Thanks http://www.911networks.com When the network has to work
2007 Jun 19
5
TentSteak 0.2.0
The second release of TentSteak is out and available as a gem on rubyforge ("gem install tent_steak"). This version introduces a handful of new form helpers, a couple method renames, editable HTML tables, and some application bootstrappers for kickstarting Camping and initializing ActiveRecord. It''s still in active development, and I''d very much appreciate
2005 Mar 22
1
ext2fs_read_bb_inode: Invalid argument && Can't read an block bitmap
Hello, sorry if the question was asked a couple of times before but I couldn't find any useful hinds to this problem using google and the listman search-engine of the archive of this list. Somehow the ext3 filesystem on one of my machines died an after a reboot grub wouldn't come up again. What I did so far: fsck -y /dev/hda4 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004)
2006 Nov 01
1
e2fsck: Bad magic number in super-block
I posted this to the Fedora-list, but thought I might get some additional information here as well. I have a HD that refuses to mount with a 'bad magic number in super-block'. I'm running FedoraCore 6 x86_64. [root at moe ~]# fdisk -l /dev/hdc Disk /dev/hdc: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
2015 May 25
2
fsck failing to notice that the block device was pulled out from under it?
Hello, tl;dr: it seems like fsck fails to notice when the block device disappears from under it. I have the following setup: * external USB disk * a partition with LUKS in it * ext4 filesystem inside the LUKS block device While doing backups to it I noticed that after some time backups would fail with an error (failed to write, ). In the following log I'm attaching the disk, enabling LUKS
2011 Nov 18
2
Monitoring progress of fsck.ocfs2
Hello Everyone, I just ran fsck.ocfs2 on /dev/drbd0 which is a one gig partition on a vm with limited resource (100meg of ram). I am worried that the process crashed because it has not responded in the past hour or so? fsck.ocfs2 /dev/drbd0 fsck.ocfs2 1.6.4 [RECOVER_CLUSTER_INFO] The running cluster is using the cman stack with the cluster name ASTCluster, but the filesystem is configured for
2008 Nov 21
2
Growth rate determination using ANCOVA
I'm a programmer in a biology lab who is starting to use R to automate some of our statistical analysis of growth rate determination. But I'm running into some problems as I re-code. 1) Hypotheses concerning Slope similarity/difference: I'm using R's anova(lm()) methods to analyse a model which looks like this: growth.metric ~ time * test.tube I understand that
2003 Sep 29
1
Fsck (presumably e2fsck) returns exit code 127 on an ext3 file sy stem
fsck (Red Hat Enterprise Linux AS 2.1) returns an exit code 127 on an ext3 file system when run from a shellscript started by cron. Here is the pertinent part of the script: ... fsck -p /dev/${BK_SLICE} 1>/dev/null 2>&1 STATUS=$? if [ ${STATUS} -ne "0" ] then echo "${MIR_PID}: file system check of /dev/${BK_SLICE} failed, status = ${STATUS}" >>${LOG}
2005 Mar 15
2
unattended reboot/fsck
Hi, We've got some units in client's vehicles which are running Fedora core 1. We've can log into them over ssh remotely there is no console attached to them. I suspect one of them has some filesystem corruption, and I'd like to both force a fsck at next reboot (which I think I can do with shutdown -F) but I'd also like to make this fsck not require any human intervention.