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 |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
06-29-2006, 01:53 PM
|
#1
|
|
Member
Registered: Mar 2006
Distribution: ALT linux 2.4 Master, and Fendora 5, and I have a damn small linux Live CD, and ubutu sever edition
Posts: 142
Rep: 
|
How do I find my other hard drive?
I have 2 hard drives on my computer. Bios can find both but I dont know how to find the 2nd one in Fedora 5. plz help
|
|
|
|
|
06-29-2006, 01:56 PM
|
#2
|
|
LQ Guru
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Wheezy (x86)
Posts: 6,094
|
fdisk -l (that's L, not 1) will tell you what the second drive is named. If you want to be able to read from it, you have to mount it. If you want it mounted at boot time, you'll have to edit /etc/fstab. The general way is to make a directory in your /mnt folder like /mnt/newdrive. then you do a mount -t ext3 -o defaults,rw /dev/hdb1 /mnt/newdrive. man mount will tell you the -t (filesystem type options) you need and the -o (other options). /dev/hdb1 would be the first partition on the second IDE disk.
Last edited by pljvaldez; 06-29-2006 at 01:58 PM.
|
|
|
|
|
06-29-2006, 01:59 PM
|
#3
|
|
Member
Registered: Mar 2006
Distribution: ALT linux 2.4 Master, and Fendora 5, and I have a damn small linux Live CD, and ubutu sever edition
Posts: 142
Original Poster
Rep:
|
Quote:
|
Originally Posted by pljvaldez
fdisk -l (that's L, not 1) will tell you what the second drive is named. If you want to be able to read from it, you have to mount it. If you want it mounted at boot time, you'll have to edit /etc/fstab. The general way is to make a directory in your /mnt folder like /mnt/newdrive. then you do a mount -t ext3 -o defaults,rw /dev/hdb1 /mnt/newdrive. man mount will tell you the -t (filesystem type options) you need and the -o (other options). /dev/hdb1 would be the first partition on the second IDE disk.
|
plz tell me how to mount it and everything, step by step instructions, oh, and that fdisk -l thing I did it in the terminal the command didnt work........
Last edited by Lord Hakk; 06-29-2006 at 02:02 PM.
|
|
|
|
|
06-29-2006, 02:13 PM
|
#4
|
|
LQ Guru
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Wheezy (x86)
Posts: 6,094
|
There's probably a gui somewhere in Gnome that would help you, but since I use KDE, I'll need some more information from you. Try running the fdisk command as the root user and posting the output here. It should list a bunch of partitions and what-not.
then also post the contents of file /etc/fstab here.
After that I'll be able to help you more.
|
|
|
|
|
06-29-2006, 02:26 PM
|
#5
|
|
Member
Registered: Mar 2006
Distribution: ALT linux 2.4 Master, and Fendora 5, and I have a damn small linux Live CD, and ubutu sever edition
Posts: 142
Original Poster
Rep:
|
Quote:
|
Originally Posted by pljvaldez
There's probably a gui somewhere in Gnome that would help you, but since I use KDE, I'll need some more information from you. Try running the fdisk command as the root user and posting the output here. It should list a bunch of partitions and what-not.
then also post the contents of file /etc/fstab here.
After that I'll be able to help you more.
|
I dont use Gnome I use KDE |
|
|
|
|
06-29-2006, 02:38 PM
|
#6
|
|
LQ Guru
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Wheezy (x86)
Posts: 6,094
|
Oh well, we can try this differently then, I think. Open the Konqueror file browser (the one with the little house icon). There should be a bar on the left that has 3 cubes stacked around each other (red, blue and green on my machine). If you click on it, it should open Devices. You should see your drive there, I believe. Right click on it and select mount.
|
|
|
|
|
06-29-2006, 02:45 PM
|
#7
|
|
LQ Guru
Registered: Dec 2005
Location: Somewhere on the String
Distribution: Debian Wheezy (x86)
Posts: 6,094
|
Okay, I was incorrect. You have to modify your /etc/fstab before Konqueror will see it...
So we're back to I need to see the output of /sbin/fdisk -l and the contents of /etc/fstab.
|
|
|
|
|
06-29-2006, 02:50 PM
|
#8
|
|
Member
Registered: Oct 2005
Location: Bhopal, India
Distribution: RHEL 6
Posts: 422
Rep:
|
Open the konsole and switch to root by this command
Enter the root password. Now run
You will see some lines similar to
Code:
Disk /dev/hdb: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 392 3148708+ 83 Linux
/dev/hdb2 1217 4870 29350755 f W95 Ext'd (LBA)
/dev/hdb3 393 411 152617+ 82 Linux swap
/dev/hdb4 412 1216 6466162+ 83 Linux
/dev/hdb5 1217 2432 9767488+ 83 Linux
/dev/hdb6 2433 3648 9767488+ 83 Linux
/dev/hdb7 3649 4870 9815683+ 83 Linux
The text in blue color represent my hard disk's primary partition.
The text in red color represent the other 4 logical partitions.
The text in green color represent the type of the filesystem.
These colored paritions are those which we will be mounting manually from your extra hard disk. I don't think that u would be having a swap partition on it,
Now suppose if we want to make the /dev/hda5 partition usable,
1) We will first create a directory somewhere on our current working hard disk. For eg: we make a directory named part2 in /mnt directory
Now we can mount the partition /dev/hdb5 to /mnt/part2 as
Code:
mount /dev/hdb5 /mnt/part2
or
Code:
mount /dev/hdb5 -t ext2 /mnt/part2
where -t <filesystem> is needed sometimes (mostly optional). And there you are done. For fat16/32 use -t vfat, for ntfs -t ntfs
Now, if you don't want to manually mount this partition every time you boot and u wish to get it mounted automatically at /mnt/part2, then you can add this line to your /etc/fstab file
Code:
/dev/hdb5 /mnt/part2 ext2 defaults 0 0
I think I have explained this method in a very simple way. If you have any problems doing this, please let me know.
Last edited by manishsingh4u; 06-30-2006 at 02:49 AM.
|
|
|
|
|
06-29-2006, 03:24 PM
|
#9
|
|
Member
Registered: Mar 2006
Distribution: ALT linux 2.4 Master, and Fendora 5, and I have a damn small linux Live CD, and ubutu sever edition
Posts: 142
Original Poster
Rep:
|
[Lord_Hakk@home_1 ~]$ su
Password:
[root@home_1 Lord_Hakk]# fdisk -l
bash: fdisk: command not found
[root@home_1 Lord_Hakk]# /sbin/fdisk -l
Disk /dev/hda: 20.4 GB, 20419854336 bytes
255 heads, 63 sectors/track, 2482 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 2482 19832242+ 8e Linux LVM
[root@home_1 Lord_Hakk]#
[root@home_1 Lord_Hakk]# mkdir /mnt/part2
[root@home_1 Lord_Hakk]# mount /dev/hda2 /mnt/part2
mount: /dev/hda2 already mounted or /mnt/part2 busy
[root@home_1 Lord_Hakk]# mount /dev/hda2 -t ext2 /mnt/part2
mount: /dev/hda2 already mounted or /mnt/part2 busy
[root@home_1 Lord_Hakk]# /dev/hda2 /mnt/part2 ext2 defaults 0 0
bash: /dev/hda2: Permission denied
y didnt it find my other hard drive? my other hard drive is a 15 BG one
|
|
|
|
|
06-29-2006, 03:28 PM
|
#10
|
|
Member
Registered: Oct 2005
Location: Bhopal, India
Distribution: RHEL 6
Posts: 422
Rep:
|
No, this is your first hard disk whose partitions are already mounted and are in use.
You must be seeing a second entry for hdb or hdd something....this would be your second hard disk.
|
|
|
|
|
06-29-2006, 03:31 PM
|
#11
|
|
Member
Registered: Mar 2006
Distribution: ALT linux 2.4 Master, and Fendora 5, and I have a damn small linux Live CD, and ubutu sever edition
Posts: 142
Original Poster
Rep:
|
the stange thing is that im not, i copied everything that happened in the terminal to this forum.
|
|
|
|
|
06-29-2006, 03:32 PM
|
#12
|
|
Member
Registered: Oct 2005
Location: Bhopal, India
Distribution: RHEL 6
Posts: 422
Rep:
|
Are you sure it was detected by linux during boot?
|
|
|
|
|
06-29-2006, 03:36 PM
|
#13
|
|
Member
Registered: Oct 2005
Location: Bhopal, India
Distribution: RHEL 6
Posts: 422
Rep:
|
Post the output of these commands
|
|
|
|
|
06-29-2006, 03:44 PM
|
#14
|
|
Member
Registered: Mar 2006
Distribution: ALT linux 2.4 Master, and Fendora 5, and I have a damn small linux Live CD, and ubutu sever edition
Posts: 142
Original Poster
Rep:
|
Buffer I/O error on device hdb, logical block 0
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 8
Buffer I/O error on device hdb, logical block 1
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 16
Buffer I/O error on device hdb, logical block 2
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 24
Buffer I/O error on device hdb, logical block 3
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 32
Buffer I/O error on device hdb, logical block 4
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 40
Buffer I/O error on device hdb, logical block 5
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 48
Buffer I/O error on device hdb, logical block 6
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 56
Buffer I/O error on device hdb, logical block 7
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x5b { DriveReady SeekComplete DataRequest Index Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 0
Buffer I/O error on device hdb, logical block 0
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 29886392
Buffer I/O error on device hdb, logical block 3735799
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 29886392
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 0
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 8
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 16
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 24
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 32
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 40
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 48
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 56
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdb: task_in_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev hdb, sector 0
[root@home_1 Lord_Hakk]# dmesg | grep sd
[root@home_1 Lord_Hakk]#
to me this is one long error but it could make some sense to u guys, so I posted most of what it said.(it was tooo long to post) maybe this has to do with the buffer I\O error at startup........
|
|
|
|
|
06-29-2006, 03:51 PM
|
#15
|
|
Member
Registered: Oct 2005
Location: Bhopal, India
Distribution: RHEL 6
Posts: 422
Rep:
|
Seeing such an error first time. No guesses would help from my side.
|
|
|
|
All times are GMT -5. The time now is 12:42 PM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
