Thanks much, highly informative.
On Sun, 30 Dec 2018, David wrote:
> Date: Sat, 29 Dec 2018 18:18:41
> From: David
> To: debian-user
> Subject: Re: e2fsck detail check
> Resent-Date: Sat, 29 Dec 2018 23:19:07 + (UTC)
> Resent-From: debian-user@lists.debian.org
>
> O
On Sun, 30 Dec 2018 at 05:20, Jude DaShiell wrote:
>
> I have a question about the -c fd command line switch. Would the valid
> options for fd be stdin stdout and stderr?
The file descriptor fd is a number. It is defined by the parent process.
The parent process is typically the shell you use to
On 12/29/18 7:20 PM, Jude DaShiell wrote:
I have a question about the -c fd command line switch. Would the valid
options for fd be stdin stdout and stderr?
I may need to provide remote support for someone and it will be helpful if
e2fsck can show completion percentage as any repair happens.
I
Good time of the day, Kamaraju.
You wrote:
> Yes, there are I/O errors in syslog such as
>
> Aug 30 08:27:20 kusumanchi kernel: [118453.218041] Buffer I/O error
> on device sdb7, logical block 5384272
> Aug 30 08:27:20 kusumanchi kernel: [118453.219839] Buffer I/O error
> on device sdb7, logica
Good time of the day, Jon.
Thank You for Your correction.
You wrote:
> > You have to understand: You have to connect it to the controller
> > directly OR You can not use what the SMART offers to You. That
> > simple.
>
> This is not actually true. Yes, the majority of USB hard drives do
> not s
Kamaraju S Kusumanchi writes:
> lee wrote:
>
>> Kamaraju S Kusumanchi writes:
>>
>>> When I ran
>>>
>>> $sudo e2fsck -c -c -f -v /dev/sdb7
>>>
>>> I am getting a lot of errors such as
>>>
>>> Error reading block 18022401 (Attempt to read block from filesystem
>>> resulted
>>> in short read) whi
On Tue, Sep 04, 2012 at 11:39:37PM +0700, Sthu Deus wrote:
> You have to understand: You have to connect it to the controller
> directly OR You can not use what the SMART offers to You. That simple.
This is not actually true. Yes, the majority of USB hard drives do not support
SMART, but some do.
lee wrote:
> Kamaraju S Kusumanchi writes:
>
>> When I ran
>>
>> $sudo e2fsck -c -c -f -v /dev/sdb7
>>
>> I am getting a lot of errors such as
>>
>> Error reading block 18022401 (Attempt to read block from filesystem
>> resulted
>> in short read) while reading inode and block bitmaps. Ignore er
Good time of the day, Andrei.
You wrote:
> To quote an uncle of mine, one only needs a "persuader" (read:
> hammer) :D
You have very wise uncle! :o)
Sthu.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
On Ma, 04 sep 12, 23:39:37, Sthu Deus wrote:
>
> Personally, I do not believe that the HDD is not extractable -
> speaking in general.
To quote an uncle of mine, one only needs a "persuader" (read: hammer)
:D
Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http:
Good time of the day, Kamaraju.
You wrote:
> May be I am missing something here. The USB hard drive I am talking
> is very similar to http://www.amazon.com/Iomega-Prestige-Portable-
> SuperSpeed-35192/dp/B004NIAG5E/ref=cm_cr_pr_product_top . The case
> can't be removed.
You have to understand:
Kamaraju S Kusumanchi writes:
> When I ran
>
> $sudo e2fsck -c -c -f -v /dev/sdb7
>
> I am getting a lot of errors such as
>
> Error reading block 18022401 (Attempt to read block from filesystem resulted
> in short read) while reading inode and block bitmaps. Ignore error? yes
> Force rewrite?
On Thu, Aug 30, 2012 at 11:40:55PM -0400, Kamaraju S Kusumanchi wrote:
> Dan Ritter wrote:
>
> > On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote:
> >> 4) What might have caused this problem and how to prevent it in the
> >> future?
> >
> > I don't know, but in my experience,
Dan Ritter wrote:
> On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote:
>> 4) What might have caused this problem and how to prevent it in the
>> future?
>
> I don't know, but in my experience, USB-connected hard disks
> suffer these problems much more than PATA/SATA/eSATA/SCSI
Sthu Deus wrote:
> Kamaraju, You wrote:
>
>> > You will not be able to do so until You connect Your drive to
>> > computer directly - i.e. through PATA/SATA cable.
>> >
>>
>> This is an external USB hard drive. The only connection it has is
>> USB. So, I guess in this case smartctl is not much
Kamaraju, You wrote:
> > You will not be able to do so until You connect Your drive to
> > computer directly - i.e. through PATA/SATA cable.
> >
>
> This is an external USB hard drive. The only connection it has is
> USB. So, I guess in this case smartctl is not much useful.
And You can not dis
On Thursday 30 August 2012 19:17:14 Kamaraju S Kusumanchi wrote:
> Sthu Deus wrote:
> > You will not be able to do so until You connect Your drive to computer
> > directly - i.e. through PATA/SATA cable.
>
> This is an external USB hard drive. The only connection it has is USB. So,
> I guess in thi
On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote:
> 1) Does this mean there are badblocks on my hard drive?
Yes.
> 2) Am I correct in choosing "yes" to both these questions or is there a
> better way?
Yes.
> 3) Is the drive going bad and need to be replaced?
Yes.
> 4) Wh
Sthu Deus wrote:
>
> You will not be able to do so until You connect Your drive to computer
> directly - i.e. through PATA/SATA cable.
>
This is an external USB hard drive. The only connection it has is USB. So, I
guess in this case smartctl is not much useful.
--
Kamaraju S Kusumanchi
http:/
Good time of the day, Kamaraju.
You wrote:
> $smartctl -a /dev/sdb
> smartctl 5.41 2011-06-09 r3365 [i686-linux-3.0.0-1-686-pae] (local
> build) Copyright (C) 2002-11 by Bruce Allen,
> http://smartmontools.sourceforge.net
>
> /dev/sdb: Unknown USB bridge [0x059b:0x0571 (0x000)]
> Smartctl: plea
Federico Alberto Sayd wrote:
> Did you try to diagnose your hardrive with smartmontools? Smartmontools
> uses S.M.A.R.T.[1] technology included in harddrives, and displays info
> about predictable failures, time of use, etc.
>
> Regards
>
> [1] http://en.wikipedia.org/wiki/S.M.A.R.T.
$smartctl
On 28/08/12 10:28, Kamaraju S Kusumanchi wrote:
When I ran
$sudo e2fsck -c -c -f -v /dev/sdb7
I am getting a lot of errors such as
Error reading block 18022401 (Attempt to read block from filesystem resulted
in short read) while reading inode and block bitmaps. Ignore error? yes
Force rewrite
On Jo, 24 iun 10, 13:16:29, Paul E Condon wrote:
>
> I was OP on a related thread a couple of months ago. I would say that
> I abandoned trying to understand issues of checking for errors on USB
> drives as a user. I did gain the impression that what I thought were
> hardware errors were instead m
On 20100622_022612, Ron Johnson wrote:
> On 06/22/2010 12:33 AM, Augustin wrote:
> >
> >Hello,
> >
> >I must learn to use e2fsck as I am having some I/O problems on some of
> >my external drives.
> >I checked all the existing documentation everywhere I could think of
> >(including the Debian offici
On Tue, Jun 22, 2010 at 1:33 PM, Augustin wrote:
>
> Hello,
>
> I must learn to use e2fsck as I am having some I/O problems on some of
> my external drives.
> I checked all the existing documentation everywhere I could think of
> (including the Debian official documentation and existing HOWTOs fro
On 6/22/2010 3:47 AM, Jochen Schulz wrote:
What's unclear about it?
The manpage doesn't say: Okay, when this happens, run this. When that
happens, run that. (That's what he wants. And, I admit, what I want,
sometimes.)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.or
Augustin:
> On Tuesday 22 June 2010 15:26:12 Ron Johnson wrote:
>> The *drive*? No. e2fsck checks the filesystem data structures
>> that have been written onto the drive.
>
> Yes, sorry. I did mean the partition, not the drive.
No, you didn't mean the partition, you meant the filesystem. ;-) T
On 06/22/2010 03:17 AM, Augustin wrote:
On Tuesday 22 June 2010 15:26:12 Ron Johnson wrote:
The *drive*? No. e2fsck checks the filesystem data structures
that have been written onto the drive.
Yes, sorry. I did mean the partition, not the drive.
You need SMART to check the drive.
Yes,
On Tuesday 22 June 2010 15:26:12 Ron Johnson wrote:
> The *drive*? No. e2fsck checks the filesystem data structures
> that have been written onto the drive.
Yes, sorry. I did mean the partition, not the drive.
> You need SMART to check the drive.
Yes, I haven't had time to install smartmonto
On Tuesday 22 June 2010 15:26:12 Ron Johnson wrote:
> The *drive*? No. e2fsck checks the filesystem data structures
> that have been written onto the drive.
Yes, sorry. I did mean the partition, not the drive.
> You need SMART to check the drive.
Yes, I haven't had time to install smartmonto
On 06/22/2010 12:33 AM, Augustin wrote:
Hello,
I must learn to use e2fsck as I am having some I/O problems on some of
my external drives.
I checked all the existing documentation everywhere I could think of
(including the Debian official documentation and existing HOWTOs from
TLDP), but couldn'
Boyd Stephen Smith Jr. wrote:
On Sunday 2008 December 21 15:00:44 Alex Samad wrote:
On Sun, Dec 21, 2008 at 03:44:04AM -0600, M.Lewis wrote:
Boyd Stephen Smith Jr. wrote:
On Sunday 21 December 2008, "M.Lewis" wrote about
'Re: e2fsck /dev/md0 issues':
Maybe what I sh
On Sunday 2008 December 21 15:00:44 Alex Samad wrote:
> On Sun, Dec 21, 2008 at 03:44:04AM -0600, M.Lewis wrote:
> > Boyd Stephen Smith Jr. wrote:
> >> On Sunday 21 December 2008, "M.Lewis" wrote about
> >> 'Re: e2fsck /dev/md0 issues':
> >&
On Sun, Dec 21, 2008 at 03:44:04AM -0600, M.Lewis wrote:
>
> Boyd Stephen Smith Jr. wrote:
>> On Sunday 21 December 2008, "M.Lewis" wrote about
>> 'Re: e2fsck /dev/md0 issues':
>>> Boyd Stephen Smith Jr. wrote:
>>
>>> Maybe what I sho
On Sun, 2008-12-21 at 05:42 +0100, M.Lewis wrote:
>
> I having an issue with my RAID array. I get some errors on boot, but the
> boot process is going beyond them and mounting the drive anyhow. So far
> as I can tell, all the data is present and readable. I would like to
> resolve these errors tho
Boyd Stephen Smith Jr. wrote:
On Sunday 21 December 2008, "M.Lewis" wrote about 'Re:
e2fsck /dev/md0 issues':
Boyd Stephen Smith Jr. wrote:
Maybe what I should do is break the array and start over? Making sure
that e2fsck on both drives is good to go beforehand of cour
On Sunday 21 December 2008, "M.Lewis" wrote about 'Re:
e2fsck /dev/md0 issues':
>Boyd Stephen Smith Jr. wrote:
>> I assume that /dev/md0 knows it's size, so the filesystem superblock is
>> bad and you should correct it by resizing the filesystem.
>
&g
Boyd Stephen Smith Jr. wrote:
On Sunday 2008 December 21 01:02:04 M.Lewis wrote:
Boyd Stephen Smith Jr. wrote:
On Saturday 2008 December 20 22:42:10 M.Lewis wrote:
The filesystem size (according to the superblock) is 24419 blocks
^^^
On Sunday 2008 December 21 01:02:04 M.Lewis wrote:
> Boyd Stephen Smith Jr. wrote:
> > On Saturday 2008 December 20 22:42:10 M.Lewis wrote:
> >> The filesystem size (according to the superblock) is 24419 blocks
> >
> >^
> >
> >> Th
Boyd Stephen Smith Jr. wrote:
On Saturday 2008 December 20 22:42:10 M.Lewis wrote:
The filesystem size (according to the superblock) is 24419 blocks
^
The physical size of the device is 244189984 blocks
On Saturday 2008 December 20 22:42:10 M.Lewis wrote:
> The filesystem size (according to the superblock) is 24419 blocks
^
> The physical size of the device is 244189984 blocks
^
2441900
Christopher - thanks for the clarications.
--
Haines Brown, KB1GRM
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, 13 Feb 2008 11:12:52 -0500
Haines Brown <[EMAIL PROTECTED]> wrote:
> I gather one can use the e2fsck with -c option to have it call
> /sbin/badblocks to report bad blocks on an unmounted partition.
This option causes e2fsck to use badblocks(8) program to do a
read-only scan of the
Marco Calviani <[EMAIL PROTECTED]> writes:
> how could i know which partition is causing the ext3 warning?
Rune tune2fs -l on your /dev/hda1, /dev/hda2 ..
And check the mount count information. Eg:
Last mount time: Tue Jun 14 10:49:07 2005
Last write time: Tue Jun 14 15:58:
Hi,
how could i know which partition is causing the ext3 warning?
Regards,
MC
Dennis Stosberg wrote:
Am 15.06.2005 um 10:21 schrieb Marco Calviani:
I've tried to run e2fsck /dev/hda but here are the results:
e2fsck 1.38-WIP (09-May-2005)
Couldn't find ext2 superblock, trying backup blo
Am 15.06.2005 um 10:21 schrieb Marco Calviani:
> I've tried to run e2fsck /dev/hda but here are the results:
>
> e2fsck 1.38-WIP (09-May-2005)
> Couldn't find ext2 superblock, trying backup blocks...
/dev/hda is your complete hard disk. The ext2 file system you want
to check is (almost) always
On Thu, Sep 02, 2004 at 09:57:20AM -0700, Richard Weil wrote:
> Can e2fsck repair/cope with physical problems with a disk?
>
> smartmontools found a number of bad blocks on my hard drive. I don't
> remember the exact wording. Other disk parameters seemed fine, i.e.,
> the disk as a whole was not i
Hi,
if you find any way to boot or chroot your system, you can try to
reinstall everything (apt-get --reinstall). You shouldn't run e2fsck -y
because it will try to fix EVERYTHING without prompting.
regards
Wolfgang
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
Sound like things didnt go well...
a) boot with knoppix
b) attempt to backup important data (email,documents..)
c) see if you can get info for recreating your system.. CHROOT if
possible and dpkg --get-selections
(get other comments as I am not a GURU)
d) see if other can suggest a way to recover
on Fri, 08 Aug 2003 04:55:23PM -0700, Alvin Oga insinuated:
>
> hi ya
>
> On Fri, 8 Aug 2003, nori heikkinen wrote:
>
> > i booted up my laptop to check my email this evening, and e2fsck
> > declares it's been 22 mounts or more and starts chugging away. it
> > dies, so i knoppix-boot and manual
hi ya
On Fri, 8 Aug 2003, nori heikkinen wrote:
> i booted up my laptop to check my email this evening, and e2fsck
> declares it's been 22 mounts or more and starts chugging away. it
> dies, so i knoppix-boot and manually e2fsck -y the thing so i don't
> have to sit there and babysit it. it fi
On Sat, Oct 05, 2002 at 05:05:55PM -0400, Brenda J. Butler wrote:
>
>
> What is the difference between e2fsck and fsck.ext2?
> I'm about to try (one of) them without a net...
The name. There seems to be a tradition to have fsck.fstype (fsck.ext2,
fsck.minix, ...) that is called by fsck. Why e2
Patrick Wiseman <[EMAIL PROTECTED]> [2002-10-05 17:16:53 -0400]:
> On Sat, 5 Oct 2002 at 5:05pm, Brenda J. Butler wrote:
>
> :What is the difference between e2fsck and fsck.ext2?
> :I'm about to try (one of) them without a net...
>
> I think they're the same thing, linked:
Yes, they are the sam
On Sat, 5 Oct 2002 at 5:05pm, Brenda J. Butler wrote:
:What is the difference between e2fsck and fsck.ext2?
:I'm about to try (one of) them without a net...
I think they're the same thing, linked:
watson:/home/pwiseman# ls -l /sbin/e2fsck
-rwxr-xr-x2 root root 101224 Mar 21 2002
On Mon, 11 Mar 2002 18:03:05 +0100
"R.Pac" <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> which options should I use to check my ide hard disk when at startup
> e2fsck tell me that I've got a bad superblock ?
e2fsck --help affiche toutes les options ou man e2fsck
>
> thanks
>
> Pac
>
>
> --
> To
On Sat, Nov 11, 2000 at 10:58:14PM -0500, Paindavoine, Matthieu (MPAINDAV)
wrote:
> Hello,
>
> I recently decided to make my computer slimmer, and removed a couple of
> packages (mostly related to emacs). Shortly after, vim wouldn't work
> anymore, giving errors with "libXi.so.6 cannot open share
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I got just - jyst the same problem.
Anyway i'm lost becouse i have several raid-soft working on other systems
but i havent got to get working a new one with a 2.2.16 kernel.
any help?
At 15.40 14/7/00 -0700, [EMAIL PROTECTED] wrote:
>Today...
>
>
On Tue, 24 Aug 1999, Ralph Winslow wrote:
> Having got to single user mode (as root, BTW), umount the slice that
> you want to run e2fsk on before you e2fsk it. To be really safe. when
> you do the / filesystem, reboot from diskette first.
It isn't necessary to do that. If you remount it read-o
Brad wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
>
> On Fri, 20 Aug 1999, William T Wilson wrote:
>
> > You have to be in single-user mode. Do 'telinit 1' to accomplish that and
> > then 'telinit 3' to get back.
Having got to single user mode (as root, BTW), umount the slice that you
want
to
-BEGIN PGP SIGNED MESSAGE-
On Fri, 20 Aug 1999, William T Wilson wrote:
> You have to be in single-user mode. Do 'telinit 1' to accomplish that and
> then 'telinit 3' to get back.
IIRC, 'telinit 2' will get you back; with the default Debian setup, the
normal runlevel is 2. Although, tel
In article <[EMAIL PROTECTED]>,
Guilherme Soares Zahn <[EMAIL PROTECTED]> wrote:
>Hi there,
>
>I was wondering if there' s a way to run e2fsck w/out booting the
>machine... I know I'd have to remount my / partition as read-only, run
>e2fsck & remount the partition as rw, but I can't seem to be
On Fri, 20 Aug 1999, Guilherme Soares Zahn wrote:
> machine... I know I'd have to remount my / partition as read-only, run
> e2fsck & remount the partition as rw, but I can't seem to be able to do
> the first step (the system says / is busy)...
You have to be in single-user mode. Do 'telinit 1'
On Fri, 20 Aug 1999, Guilherme Soares Zahn wrote:
: > Did you go to single user mode before you tried to remount root
: > read-only? Have you more than one e2fs partition?
:
: The answer is 'nope' to both, and I think you've just got it... should have
entered
: single mode BEFORE trying th
> Did you go to single user mode before you tried to remount root
> read-only? Have you more than one e2fs partition?
The answer is 'nope' to both, and I think you've just got it... should have
entered
single mode BEFORE trying that! I guess it's just one typical case of the famous
'DOS/Win form
On Fri, 20 Aug 1999, Guilherme Soares Zahn wrote:
: Hi there,
:
: I was wondering if there' s a way to run e2fsck w/out booting the
: machine... I know I'd have to remount my / partition as read-only, run
: e2fsck & remount the partition as rw, but I can't seem to be able to do
: the fi
Thank you for the quick response. I must have gone a little crazy
with the 'x' when editing /etc/fstab. That was the problem.
Thanks again for getting me back up and running,
Mark
---
[EMAIL PROTECTED] wrote:
>
> Curious question - does the bootup message really say /dev/hda rather
> than /de
On 15 Aug, Mark Wagnon wrote:
> Hi all-
>
> I've managed to install the base system via floppies and I've spent
> several hours downloading packaged with dselect, and all seemed to
> be progressing nicely. I've only rebooted the system twice, and
> after downloading and installing something to do
Ian Eure wrote:
>On a similar topic, what do directory sizes mean? I can't seem to see any di
>rect
>connection between the size of a directory in an ls -l and it's contents, or
> the
>size of it's contents.
A directory is created with enough slots for a standard number of files.
* Ian Eure <[EMAIL PROTECTED]>
|
| On a similar topic, what do directory sizes mean? I can't seem to see
| any direct
| connection between the size of a directory in an ls -l and it's contents,
| or the
| size of it's contents.
A directory is internally just like any other file. Tha data it contai
On a similar topic, what do directory sizes mean? I can't seem to see any direct
connection between the size of a directory in an ls -l and it's contents, or the
size of it's contents.
On Wed, Jul 01, 1998 at 07:04:26PM -0400, Bob Hilliard wrote:
> I'd like to piggy-back on this discussion -
Bob Hilliard wrote:
> I have never found any files in lost+found, but ls-l and du
> always show it as 12kb, even in a brand new file system. What is
> occupying those 12k?
Ok, first some background:
The size of a directory is dependant on how much space has been allocated
for filenames in t
I'd like to piggy-back on this discussion - Oliver is the first
person I have heard talk knowledgeably lost+found.
I have never found any files in lost+found, but ls-l and du
always show it as 12kb, even in a brand new file system. What is
occupying those 12k?
Bob
--
"Oliver Elphick
On Thu, Jul 02, 1998 at 02:12:03AM +0800, Jieyao wrote:
>
> I had a few question regarding e2fsck.
>
> Can I assume e2fsck is something like Norton Disk Doctor for Linux.
Yes, in that it checks and repairs linux ext2fs partitions.
> When I run it, it gave me
> /dev/hda1 is mounted. Do you real
"Jieyao" wrote:
>
>I had a few question regarding e2fsck.
>
>Can I assume e2fsck is something like Norton Disk Doctor for Linux.
e2fsck is a file system check and repair utility for ext2 file systems.
It checks the self-consistency of the file system. It is run periodically on
reboot, and
From: Andrea Arcangeli <[EMAIL PROTECTED]>
> If I found a defective sectors on my /dev/hda2 using "e2fsck -c" and I try
> to fix the problem, how can I know the names of the damaged fixed files
> as I can do using dos scandisk?
The debugfs program would tell you this. However, e2fsck does not scan
75 matches
Mail list logo
