LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
LinkBack Search this Thread
Old 10-21-2004, 07:10 AM   #1
mohapi
Member
 
Registered: Mar 2003
Distribution: Debian
Posts: 208

Rep: Reputation: 30
..."short read while reading block 516"


I have a nasty problem. I'm writing this on my Win 2000 harddrive because my Fedora Core I drive won't let me in. My error message is;
/: clean, ##/#### files, ###/#### blocks
/boot: clean, ##/###### files, #####/###### blocks
/data1: Attempt to read block from filesystem resulted in short read while reading block 516

/data1: Attempt to read block from filesystem resulted in short read while reading
journal superblock

fsk.ext3: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /data1

/data2: clean, blah, blah,blah
/data3: clean, blah, blah,blah
etc., etc., etc,. through all of disk and then

An error occured during the filesystem check.
Dropping you to a shell; the system will reboot when you leave the shell.
Give root password for maintenance
[ or type Control-D to continue ]

If I ^-D I just repeat this scenario, but if I give my psswd, I get;

Repair filesystem1:
[ to which I type ] fsck -y /dev/hda1/data1

and after a few moments of harddrive action I'm rewarded with;

Repair filesystem2:

And on and on. I've gone up to Filesystem 65, and began to wonder what good I'm actually doing. /data1 at block 516 is my obvious problem Can someone tell me how to resolve this mess? If nothing else, should I upgrade with a CD version of Fedora Core II or another distro so I can save my data on the harddrive and then buy a new drive? This same thing happened to my wife's drive about one year ago and after getting her drive to work about 5 times, I gave up and tried Win 2000 on her drive and it has worked perfectly for her ever since. Could it be Fedora rather than the drive?
Thanks

Last edited by mohapi; 10-21-2004 at 07:15 AM.
 
Old 10-21-2004, 04:28 PM   #2
misc
Senior Member
 
Registered: Apr 2003
Distribution: Red Hat + Fedora
Posts: 1,074

Rep: Reputation: 52
I don't understand why you type "fsck -y /dev/hda1/data1". It makes no sense.

/data1 is a partition label. /dev/hda1 is a partition. You must check /dev/hda1, that's all. E.g. fsck -y -C -V /dev/hda1
 
Old 10-21-2004, 08:37 PM   #3
mohapi
Member
 
Registered: Mar 2003
Distribution: Debian
Posts: 208

Original Poster
Rep: Reputation: 30
When I tried that, which I had before the original post, I got only the first message. Nothing would be accomplished.
 
Old 10-21-2004, 09:29 PM   #4
mohapi
Member
 
Registered: Mar 2003
Distribution: Debian
Posts: 208

Original Poster
Rep: Reputation: 30
I ran fsck -y -C -V /dev/hda1 and this was the response;

fsck.1.34 [25-Jul-2003]
{ [ /sbin/fsck.ext3 [1] -- /boot} fsck.ext3 -y - C0 /dev/hda1
e2fsk 1.34 [25-Jul-2003]
/boot: clean, 72/178816 files 18844/357438 blocks

Now what I need to repair is ONLY /data1 as all others, "/", /boot, /data2, /data3, /data4, /var, etc., are clean except for block 516 in /data1. How do I repair just that filesystem? There are zillions of files on this 80G drive!
 
Old 10-22-2004, 06:09 AM   #5
misc
Senior Member
 
Registered: Apr 2003
Distribution: Red Hat + Fedora
Posts: 1,074

Rep: Reputation: 52
Then the information in your original post is wrong, and /data1 is NOT /dev/hda1. Only you can tell which partition is labelled /data1. e2label /dev/hdaX (replace X appropriately) is one way to query a partition's label.
 
Old 10-22-2004, 10:06 AM   #6
mohapi
Member
 
Registered: Mar 2003
Distribution: Debian
Posts: 208

Original Poster
Rep: Reputation: 30
Can I do that query from the point of [Repair filesystem] 1# ? That is my only starting position unless I can do it from the splash screen where I choose the Linux kernel or Win 2000 HDD to boot into. @ that screen I'm allowed to make kernel arguments, etc.
 
Old 10-22-2004, 12:17 PM   #7
misc
Senior Member
 
Registered: Apr 2003
Distribution: Red Hat + Fedora
Posts: 1,074

Rep: Reputation: 52
Yes. You're at an ordinary shell prompt, just the system environment is a bit limited. Alternatively, boot first CD into "linux rescue" mode and fsck your file system from there.
 
Old 10-22-2004, 01:37 PM   #8
mohapi
Member
 
Registered: Mar 2003
Distribution: Debian
Posts: 208

Original Poster
Rep: Reputation: 30
Thanks much. I'll try those.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Getting "Short read in buffer_copy" error with "dpkg" stalefries Linux - Software 6 03-24-2010 03:19 PM
New kernel - VFS: Cannot open root device "301" or unknown block(3,1) j0y Debian 2 04-30-2005 09:14 PM
VFS: Cannot open root device "1601" or unknown-block(22,1) takehora Slackware 3 06-11-2004 08:34 PM
"/dev/cdrom is not a valid block device" error kungfuhokie Fedora 4 06-11-2004 06:55 AM
Kernel 2.6.1 /dev/cdrom "not a valid block device" jwjensen Linux - General 8 01-27-2004 12:50 PM


All times are GMT -5. The time now is 08:00 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration