Help - Search - Members - Calendar
Full Version: Suse Can't See Second Hard Drive
Linuxhelp > Support > Hardware Support
AngryWookiee
Hello,

I recently install Suse 9.2 on my computer. I am dual booting Suse 9.2 with Windows XP Pro. I have 2 hard drives, an 80GB which Windows and Suse are both installed and second hard drive that has one NTFS partition and a fat32 partition.

When I had Fedora Core 3 installed I was easily able to mount the Fat32 partition so that I could share files between Linux and Windows. However, Suse does not see the second hard drive at all... and Windows only sees the 2nd hard drive if I shut the computer off and turn it on for the first time, if I restart the computer and boot back into Windows it does not see it. I have also noticed that the hard drive light on my computer stays on solid after I reboot the PC whether I use Windows or Suse.

I have also noticed that when I cannot see the hard drive in either Windows or Suse it no longer shows up in BIOS either...

I had a similar issue with Fedora Core 2 but after reinstalling it the problem went away, and I didn't have any issues with Fedora Core 3 at all.

I have tried googling to find the solution and have also visited other linux boards but nobody else seems to have the same problem. I'm hoping that somebody here can shed some light on what is going on. I have already tried reinstalling Suse but that did not resolve the issue.

Also after checking the system log in Yast it says the following:

Apr 18 19:33:23 linux kernel: Disabled Privacy Extensions on device
dc5e9800(sit0)
Apr 18 19:33:23 linux kernel: hdb: status error: status=0x7f {
DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index
Error }
Apr 18 19:33:23 linux kernel: hdb: status error: error=0x7f {
DriveStatusError UncorrectableError SectorIdNotFound TrackZeroNotFound
AddrMarkNotFound }, LBAsect=260013951, sector=0
Apr 18 19:33:23 linux kernel: ide: failed opcode was: unknown
Apr 18 19:33:23 linux kernel: hdb: drive not ready for command
Apr 18 19:33:23 linux kernel: ide0: reset timed-out, status=0xd0
Apr 18 19:33:23 linux kernel: drivers/usb/class/usblp.c: usblp0: USB
Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04A9 pid 0x1082
Apr 18 19:33:23 linux kernel: usbcore: registered new driver usblp
Apr 18 19:33:23 linux kernel: drivers/usb/class/usblp.c: v0.13: USB
Printer Device Class driver
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 0
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 0
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 8
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 1
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 16
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 2
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 24
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 3
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 32
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 4
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 40
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 5
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 48
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 6
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 56
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 7
Apr 18 19:33:23 linux kernel: usbcore: registered new driver snd-usb-audio
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 64
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 8
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 72
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 9
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 80
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 10
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 88
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 11
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 96
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 12
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 104
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 13
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 112
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 14
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 120
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 15
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 0
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 0
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 0
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 0
Apr 18 19:33:23 linux kernel: end_request: I/O error, dev hdb, sector 0
Apr 18 19:33:23 linux kernel: Buffer I/O error on device hdb, logical block 0

..and continues on like this for many more lines.

Any help would be greatly appreciated. Thank You in advance.
michaelk
If it does not show up in the BIOS when it is having problems and windows also has can not access the drive then IMHO it is a hardware problem and the drive is failing. The SuSE vs FC3 might be just a coincidence. I assume that the 1st drive is hda and can eliminate the controller from being the problem.

If you can access the drive from a cold boot back up any important data immediately. I would also use the manufacture's drive utilities to verify the integrity of the drive.
AngryWookiee
I took your advice and backed up the data on the hard drive. I then downloaded manufacture's drive utilities. I'm not sure if this the right area for posting this information but the diagnostic utilities reported the following. I'm not sure what it means but I'm sure that it can't be good. The hard drive is 3+ years old so it would not surpise me if it was dieing.

Anybody have any suggestions as to what the following means, is the hard drive dead?

[ Model Name : SAMSUNG SV4002H
Rom Revision : QP100-07
Serial Number : 0379J1ET501622
Drive Size : 32253MB (LBA : 66055248)
Start Time : Wed Apr 20 23:51:12 2005


-------------------------------------------------
Test Loop Number : 1/1
-------------------------------------------------
>> CHECK CHANNEL INTEGRITY : Testing... Pass !
>> CHECK M.C. : Testing... Pass !
>> CHECK S.M.A.R.T. : Testing... Pass !
>> SPIN DOWN / UP : Testing... Pass !
>> SIMPLE READ / WRITE : Testing... Pass !
>> SIMPLE SURFACE SCAN : Testing...
Error : Data is uncorrectable.
>> WRITE VERIFY : Testing... Pass !
>> AVERAGE SEEK TIME : Testing... Pass !
>> MAXIMUM SEEK TIME : Testing... Pass !
>> RANDOM SURFACE SCAN : Testing...
Error : LBA 361426
Error : Data is uncorrectable.
>> READ SURFACE SCAN : Testing...
Error : LBA 124487
Error : LBA 125802
Error : LBA 199470
Error : LBA 201663
Error : LBA 202978
Error : LBA 205171
Error : LBA 217010
Error : LBA 219203
Error : LBA 220518
Error : LBA 222711
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2017 Invision Power Services, Inc.