LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 08-11-2004, 01:09 PM   #1
tsigane
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Rep: Reputation: 0
Bad Sector Hard Drive


Please let me bother you with a little history.....I'm just desperate and a Linux newbie... I have a 20gig hdd with >95% of drive having bad sectors.I "NEED" some office files of data from the drive badly.I used GetDataBack for FAT to get the files..but to no avail...no single file emerged from the recovery tree...OnTrack's Easy Recovery cannot help me either...I used HDD Regenerator to fix the bad sectors-It just reports it...it can't fix it....The drive doesn't grind....no unusual noises.....Tried SpinRite6.0 yesterday...Level 2 ...for Emergency Data Recovery....it sees it as an Add-on Controller..cannot retrieve the drive details...and hence unable to access the entire range of sectors...giving me some RED writings.....the Drive had a FAT32 file system whilst it was functional....WHY I'M I IN A LINUX FORUM TALKING ABOUT A FAT32....????.... I burnt a knoppix live CD .....The partition label is no longer set to FAT32.. was running /sbin/ fdisk /dev/hdb and then in fdisk type "p" to see what fdisk sees so that I would see whether I could STILL mount the drive as a FAT32 partition, or use linux fdisk to label it as a FAT32 partition again...and from there proceed to find how I can retrieve the files.....BUT!!!!!!!...........As I run the /sbin/ fdisk /dev/hdb comamnd...in the Shell - Bash ....it reports "Not a directory"...and it also gives me the same feedback with the master drive....hda.....Is there something I'm doing wrong....?????...can somebody please help me ASAP...Thanks.

Last edited by tsigane; 08-11-2004 at 01:15 PM.
 
Old 08-11-2004, 03:51 PM   #2
jomen
Senior Member
 
Registered: May 2004
Location: Leipzig/Germany
Distribution: Arch
Posts: 1,687

Rep: Reputation: 54
if you put in /sbin/ fdisk /dev/hdb it tells you quite correctly what it did...

...there is NO SPACE between /sbin/ and fdisk - it is: /sbin/fdisk /dev/hdb

also: in Knoppix you should not need to give the full path - just: fdisk /dev/hdb would suffice - provided that you are root - it will not work otherwise

please try also: cfdisk /dev/hdb -it has a easier to use interface
 
Old 08-11-2004, 04:59 PM   #3
tsigane
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
Thanks Jomen.....
I don't know why I brought a space when I was typing the request...I never left any space in the console.....I tried the cfdisk command ...."FATAL ERROR"..Cannot open Disk Drive......I have a master drive....the bad drive is the slave...when I go to the Info Centre...the master drive is reported correctly...with its file system..NTFS...the slave drive is also shown..but I can't mount it...coz its not in any file system....I cannot create a directory on the master drive...but I can create one in the home/Knoppix....just wanna label the disk as a FAT32...and find other ways as to how I'm gonna proceed.
 
Old 08-12-2004, 03:31 AM   #4
jomen
Senior Member
 
Registered: May 2004
Location: Leipzig/Germany
Distribution: Arch
Posts: 1,687

Rep: Reputation: 54
What is it you want to do?
What happened?

if you have a bad drive (you said more than 95%) it is probably hopeless anyway to recover anything...

If the drive was formatted NTFS - then it will surely NOT help to label it as FAT or anything else in the hope you might then be able to read something... Just labelling one filesysten to appear as another will not work
There are tools - even on the Knoppix-CD which can be used for tasks like this:
parted - in some variants - and I think another similar program are on Knoppix-CD
I'm not sure if they can deal with NTFS - look into them and into the Knoppix documentation - as this CD is made to be able to deal with cases like this.

If you need to rescue a drive - it is best to leave it unchanged, until you made a backup copy.
You can do that with dd - if access via the filesystem is not possible. You will need another drive equally large to put the image on...
Then you can go about trying to fix what can be fixed on the crashed drive - but you will need to ask someone else on details - I just know, that there is good documentation on that topic out there --> Google
 
Old 08-12-2004, 05:48 AM   #5
tsigane
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
Jomen...
I think u have a very good idea of what I wanna do.....The crashed drive had WinMe on...files system was FAT32.....Now that file system is messed up...and I wanna relabel that original FAT32 on.....I have a master drive now...40gig hdd....so space for a backup copy is not a problem....just wanna have a stepwise process....with the requisite tools..be it Windows or Linux..to get this thing done....u might know the tools on the Knoppix....plz c whether u can direct me.....Thanks
 
Old 08-12-2004, 08:42 AM   #6
jomen
Senior Member
 
Registered: May 2004
Location: Leipzig/Germany
Distribution: Arch
Posts: 1,687

Rep: Reputation: 54
When I have the time I will boot up my Knoppix and look for what is on there to be used to help resolving your problem...
You should also get yourself some knowledge on how these things are done - especially how to operate parted from knoppix - because that is what I would first suggest to try out.
I'm not there - so I cannot see what is really happening...or has happened...
Why is it that your drive is 95% bad?
What program told you that?

Everything I can tell you here is done from linux - I don't know nothing about tools or ways to use with Windows itself - but I suppose it is best anyway - and since you cannot boot to windows, that option does not even exist.
I - or anyone else who could help - would like to have the following things:

a listing of the current partition-table of that drive - IF it is hdb, then the command is:

fdisk /dev/hdb ---> and then press "p" to get a list of the partition-table

or use "cfdisk /dev/hdb" - it has a nicer interface

for both these commands to work in Knoppix, you have to be root!
To do that: type: su in a terminal - and you will be root - without a password

Please try that - even if you already did...

What version of Knoppix do you have - I have 3.3 and 3.4 (some CD which came with a Computer-magazine)
 
Old 08-12-2004, 09:17 AM   #7
tsigane
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
Thaanks Jomen..
I normally do these things in windows...partition table...mbr...blah..blah..etc..but this time..looks like I got no option..but linux to have the stuff...I just started gearing into linux...I was using the HDD Regenerator i.41 or sth....it took about 3-4days before getting to about 10mb....I jsut had to stop it..coz it was gonna take forever to regenetrate all those sectors....and it wasn't able to fix them anyway....it just reports them....(>95%)..I just presumed that the drive may be that bad....but even in the Linux it reports of the I/O Error.....I gonna try the "root" stuff u r talking about now....I think its so since I'm booting from the CD..not Linux from the hdd...I'm currently using the Knoppix 3.4....Plz lemme know of anything u got for me...I gonna go start right away.Thanks again!!!
 
Old 08-12-2004, 12:05 PM   #8
tsigane
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
Jomen.....
Tried it.....it was the "su" at the sommnad line that was missing....this time I was able to do the fdisk and cfdisk...with the master hdd..its perfect....I can get to see the number of cylinders and it gave me all the other options...with the problem hdd....on executing cfidsk /dev/hdb....the user interface that appears says..FATAL ERROR..Cannot Read Disk Drive...Press any key to exit cfdisk..on fdisk/dev/hdb....message that appears is.."Unable to read dev/hdb"....Where do I go from here????..Plz help me..!!!!
 
Old 08-12-2004, 12:19 PM   #9
tsigane
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
I'm able to mount the drive on the desktop...but it gives me an I/O error ...MESSAGE....Could not mount device...I couldn't determine the file system type or none was specified...and hence I can't get to see the files.
 
Old 08-12-2004, 04:27 PM   #10
jomen
Senior Member
 
Registered: May 2004
Location: Leipzig/Germany
Distribution: Arch
Posts: 1,687

Rep: Reputation: 54
So...fdisk worked and gave you some output...Why don't you give it to me?

fdisk /dev/hdb --> then press "p" (this prints out the partition table as it is now) and send me the output

Your second message: no - you did not mount it - it failed to mount because it could not determine the filesystem-type - what command did you use for this?
 
Old 08-12-2004, 04:53 PM   #11
tsigane
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
output..

knoppix@ttyp0[knoppix]$ su
root@ttyp0[knoppix]# fdisk /dev/hda

The number of cylinders for this disk is set to 5169.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/hda: 40.0 GB, 40020664320 bytes
240 heads, 63 sectors/track, 5169 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 5168 39070048+ 7 HPFS/NTFS

Command (m for help): e
e: unknown command
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)

Command (m for help): x

Expert command (m for help): x
Command action
b move beginning of data in a partition
c change number of cylinders
d print the raw data in the partition table
e list extended partitions
f fix partition order
g create an IRIX (SGI) partition table
h change number of heads
m print this menu
p print the partition table
q quit without saving changes
r return to main menu
s change number of sectors/track
v verify the partition table
w write table to disk and exit

Expert command (m for help): q

root@ttyp0[knoppix]# fdisk /dev/hdb

Unable to read /dev/hdb
root@ttyp0[knoppix]#

For the second part I just right-clicked on desktop...mount hard drive device....and I jsut mounted the hdb.....but it won't open ..bcos of the file system...

I also did dmseg....will send u the output soon.
 
Old 08-12-2004, 04:55 PM   #12
tsigane
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
root@ttyp0[knoppix]# dmesg
eekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
end_request: I/O error, dev 03:40 (hdb), sector 8
hptraid: Error reading superblock.
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
end_request: I/O error, dev 03:40 (hdb), sector 8
hptraid: Error reading superblock.
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
end_request: I/O error, dev 03:40 (hdb), sector 8
hptraid: Error reading superblock.
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
ide0: reset: success
hdb: read_intr: status=0x5b { DriveReady SeekComplete DataRequest Index Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=8, sector=8
end_request: I/O error, dev 03:40 (hdb), sector 8
hptraid: Error reading superblock.
megaraid: v1.18k (Release Date: Thu Aug 28 10:05:11 EDT 2003)
megaraid: no BIOS enabled.
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
end_request: I/O error, dev 03:40 (hdb), sector 39102272
pdcraid: Error reading superblock.
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x5b { DriveReady SeekComplete DataRequest Index Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102272, sector=3910272
end_request: I/O error, dev 03:40 (hdb), sector 39102272
pdcraid: Error reading superblock.
Promise Fasttrak(tm) Softwareraid driver 0.03beta: No raid array found
Guestimating sector 78164335 for superblock
Guestimating sector 39101311 for superblock
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39101304, sector=3910104
end_request: I/O error, dev 03:40 (hdb), sector 39101304
silraid: Error reading superblock.
driver for Silicon Image(tm) Medley(tm) hardware version 0.0.1: No raid array fund
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 19:48:59 Apr 17 2004
usb-uhci.c: High bandwidth mode enabled
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0x1440, IRQ 16
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0x1460, IRQ 19
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.2 to 64
usb-uhci.c: USB UHCI at I/O 0x1480, IRQ 18
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
blk: queue c03591e0, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c0359328, I/O limit 4095Mb (mask 0xffffffff)
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
cloop: Initializing cloop v2.01
cloop: loaded (max 8 devices)
cloop: /cdrom/KNOPPIX/KNOPPIX: 29715 blocks, 65536 bytes/block, largest block i 65552 bytes.
ISO 9660 Extensions: RRIP_1991A
Freeing unused kernel memory: 140k freed
Real Time Clock Driver v1.10f
ACPI: Power Button (FF) [PWRF]
ACPI: Processor [CPU0] (supports C1, 8 throttling states)
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
usbdevfs: remount parameter error
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI IAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
hw_random: RNG not detected
tg3.c:v2.9 (March 8, 2004)
eth0: Tigon3 [partno(BCM95782A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/1001000BaseT Ethernet 00:30:6e:b2:26:f2
Intel 810 + AC97 Audio, version 0.24, 19:47:54 Apr 17 2004
PCI: Setting latency timer of device 00:1f.5 to 64
i810: Intel ICH5 found at IO 0x1400 and 0x1000, MEM 0xf8500400 and 0xf8500600, RQ 17
i810: Intel ICH5 mmio at 0xd0c6d400 and 0xd0c6f600
i810_audio: Primary codec has ID 0
i810_audio: Audio Controller supports 6 channels.
i810_audio: Defaulting to base 2 channel mode.
i810_audio: Resetting connection 0
i810_audio: Connection 0 with codec id 0
ac97_codec: AC97 Audio codec, id: ADS116 (Unknown)
i810_audio: AC'97 codec 0 supports AMAP, total channels = 2
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: Unsupported Intel chipset (device id: 2578), you might want to try agptry_unsupported=1.
agpgart: no supported devices found.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: Trying generic Intel routines for device id: 2578
agpgart: AGP aperture is 128M @ 0xe8000000
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hda: DMA disabled
hdb: DMA disabled
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
end_request: I/O error, dev 03:40 (hdb), sector 0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
ide0: reset: success
hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=0, sector=0
end_request: I/O error, dev 03:40 (hdb), sector 0
FAT: bogus logical sector size 63222
VFS: Can't find a valid FAT filesystem on dev 02:00.
EFS: 1.0a - http://aeschi.ch.eu.org/efs/
root@ttyp0[knoppix]#
 
Old 08-12-2004, 05:45 PM   #13
jomen
Senior Member
 
Registered: May 2004
Location: Leipzig/Germany
Distribution: Arch
Posts: 1,687

Rep: Reputation: 54
o.k. (rather not...) - I see

there is no recognizable filesystem on /dev/hdb and no valid partition information...

If someone sees this - and already knows how to deal with this...please do help.

I'm going to suggest a full backup of the whole device /dev/hdb to a file on another disk
(dd if=/dev/hdb of=_some_image_file_on_another_disk)
and then try parted on the real device - I'll have to get some info on that before I'm able to give advice - I've used parted to restore a drive with destroyed partition information but this drive was - apart from that - o.k. in every aspect and I managed to get it working again without data-loss...but this was more than two years ago and I can't remember exactly what and how I did it.

Question:

how many partitions where on the damaged drive ?

where they all fat32 ?

do you have any detailed info about the partition-layout prior to the drive failing to work correctly?
any dumps of the output of fdisk for instance or any older logfiles with info on the drive layout and geometry?

I'll be back 20 hrs from now at the earliest...
 
Old 08-12-2004, 06:09 PM   #14
jomen
Senior Member
 
Registered: May 2004
Location: Leipzig/Germany
Distribution: Arch
Posts: 1,687

Rep: Reputation: 54
just did some research...
the tool I was looking for - and have used then - was gpart...
I hope it is on Knoppix - don't know...
 
Old 08-13-2004, 03:32 PM   #15
jomen
Senior Member
 
Registered: May 2004
Location: Leipzig/Germany
Distribution: Arch
Posts: 1,687

Rep: Reputation: 54
...gpart...it is on Knoppix all right

If you still need help - I'd like to - as far as I can...
If your drive has really fallen apart - there is not much of a chance - but if just the partition-table got screwed up and the drive itself is o.k. - you might have a chance...

try this:

right after you booted up to Knoppix (do not yet try to mount /dev/hdb...) - open a terminal and get root (su)

then do:

dmesg | grep CHS

alternatively:

locate the kernel.log-file (/var/log/kern.log probably) and do search it for lines starting with: hdb: ...(something...) and CHS=...(something)

this is to get info on your damaged drive - and on the drive-geometry reported by the kernel during boot up - we might need this later on...

issue:

gpart /dev/hdb

and post the output of this too

you will find in there - if there is anything - what the partition table might have to look like, to be correct

for info on gpart:

man gpart
 
  


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



Similar Threads
Thread Thread Starter Forum Replies Last Post
Repair Hard drive bad sector jselby Linux - Hardware 4 10-25-2005 06:27 PM
Bad hard drive? Kitohe Linux - Hardware 4 09-25-2004 07:32 PM
hard drive, going bad? cheater1034 Linux - Hardware 7 09-13-2004 03:02 PM
Hard Drive going bad seldomseen Linux - Hardware 3 12-10-2003 02:13 PM
Is my hard-drive bad? moger Linux - Hardware 10 01-18-2003 01:42 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 04:03 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration