Hard disk light stays on. No processes, no apps running. reboot=corruption. wtf?
Linux - HardwareThis 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.
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.
I dont think it would be.. It'd hafta be one or the other -- either a running system, OR the tars..
It's only a 14 or 15 GB drive.
Know what though, I'm impatient, and this tarring is taking forever!!!! I may just copy the OS over to that little drive, edit fstab and LILO, and run off the other drive.
Cool idea
Well.. I aborted the tar operation.. Instead I started just copying the system over.. Well, that was taking soooo long.. I mean, normally I can copy hundreds of MB in VERY little time.. THIS time, this $#@%^ thing was taking forEVER and when I finally managed to get it done, I couldn't get the stupid drive to boot.. Matter of fact, while trying to boot it, everything got hung up on these damn read-seek-can't seek drive_not_ready DMA_intr_timer_not-ready blah blah blah errors! Errors everywhere!
I went to load up Ubuntu LiveCD, and that took like 6 or 7 minutes.. I mean, come on this is ridiculous.
Finally I took the machine apart and removed my little old small HD, the Western Digital. Rearranged some connectors, rebooted --- Zoom everything took off like lightning
Sooo.... I am suspecting the OLD HD may for some reason have been causing all this crap. The enw one is working fine as we speak. I'll give it a week or so before I start relaxing about it though..
So now the Seagate is alone on IDE0, and the 2 optical drives are on IDE1, and the machine seems happy. Even with all the BIOS set to default settings, it worked better than it has for days now. So I cranked up the BIOS again to my supercharged settings , did some quick benchmarks, and am thoroughly impressed.
Tomorrow I'll run the Seatools Desktop program again and see what it says. Mebbe the old WD drive was jamming up the IDE controller somehow??
EDIT-- Maybe not... It's still doing this:
Code:
hda: dma_timer_expiry: dma status == 0x20
hda: DMA timeout retry
hda: timeout waiting for DMA
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x20
hda: DMA timeout retry
hda: timeout waiting for DMA
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x20
hda: DMA timeout retry
hda: timeout waiting for DMA
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x20
hda: DMA timeout retry
hda: timeout waiting for DMA
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hda: drive not ready for command
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
Last edited by GrapefruiTgirl; 05-03-2007 at 08:00 PM.
Sorry, assumed the other hd was already removed. might have to fdisk it and remove any bootable partitions. would be the last thing i would try before putting it out to pasture.
I'm back A la nouveau hard drive! And it's working lovely (just like the first one did when I got it). The entire machine feels like I removed a ball-and-chain from its leg.
Funny thing now, which I think is unrelated, but may have to do with the locations of the devices on the IDE bus: My CD-RW packet-writing device is calling itself a DVD device, when I am in Konqueror and I click 'GO' --> 'Storage Devices' .. It works fine, as does the actual DVD-ROM, but it's rather annoying having the wrong icon and wrong identifier; makes for a tad bit of confusion when it comes to eject/mount/umounting one of them. Here's the physical layout:
ide0,0 = hda = main HD
ide0,1 = hdb = small HD
ide1,0 = hdc = DVDROM
ide1,1 = hdd = CD-R/W
So during boot, from rc.local, the packet device is created (major:minor 254:0) and mapped to /dev/hdd (major:minor 22:64). This mapping is correct, so I think it must be a KDE issue. I've managed to get the icons corrected for my USER account, but from ROOT-konqueror, it's messed up, and when I try to change the icon/mimetypes/name of either the packet-device or the CD-R/W, it changes the other one to match.
I don't really know where to go next with it. Altogether though, I am happy that the new drive is in, and I didn't pull too much hair out restoring my system from all the CD archives
PS - the drive I took back, I checked the SMART logs in it before removing it, it had failed and aborted EVERY self-test before even completing 10% of each test -- no good! I ran a SMART test on the new one today - Pass @ 100%
Mine does the same think on fresh install. (dvd-rw and cdrom instead) but it set up both links as if they were both regular cdroms. had to create directories, change fstab and mount the cdrom as cdrom (added symlinks) and the dvdrw to dvd-rw and that fixed the kde settings somehow. I still haven't tracked down why this worked but its worth a try
Hmmmm. Interesting Hern_28. Well, I've done/tried everything except deleting and recreating the mount folders. I've fixed fstab, force-reloaded udev, deleted /dev nodes and rebooted.. So far nothing has worked..
BTW, this isn't a 'fresh' install -- I had archived my entire partition in pieces, and saved the archives to CD before returning the HD. That *might* have something to do with it too.
I'll keep fiddling, and report later!
Update: problem solved! I commented out the fstab entries, deleted the mount points, removed the packet-device node, and rebooted, and then re-made the stuff I deleted, and presto, all looks good! Thanks again Hern_28
Last edited by GrapefruiTgirl; 05-06-2007 at 07:30 PM.
Thanks Hern! Yes, everything is working just peachy , infact so well I've just re-upped my overclock again -- I've got my P4 1.8 Ghz now running 2.41 Ghz and all is super!
Your suggestion(s) were much appreciated.
Sasha
Ever since you helped me get started i have managed to even get Slackware to let me mount, umount and remount my usb drives . Good with windows and hardware, still working on getting good at Slackware, Debian and Ubuntu.
OK, well I HAVE TO GET OFF THIS WinXP MACHINE before I try to inject myself with drain-cleaner to end the pain! Thanks folks, see ya soon -- from Linux
Sasha
ROTFL. XP's not THAT bad, surely? Could have been worse, you know, could have been Vista.
Well me too, the Linux learning path is a long and continuous thing it seems. Plenty to keep us occupied for a long time .
BTW, though I don't care much for Ubuntu, it saved my bacon the other day (or atleast prevented the bacon from getting overcooked )-- I still use it for Gparted regularly, but I didn't know (or didn't bother to check) that it could mount and read my UDF-formatted floppy CD-RW's. So after figuring out that it could, I used Ubuntu to extract and restore my OS from archived CD-backups onto my new HD Slick as could be
EDIT: LOL @ BrianL Well, XP on 'that' particular machine, compared to my Slack on 'my' machine, was painful indeed; I doubt the XP machine here would run Visha.
Last edited by GrapefruiTgirl; 05-07-2007 at 10:07 AM.
My wife loves ubuntu, so its on her computer, she loves it till she has a problem (then she calls me lol). Running debian and zenwalker to manage emergency backups here. even think there is a version of slax on here somewhere. I will admit the upgrade to feisty had some interesting problems though
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
and when I finally managed to get it done, I couldn't get the stupid drive to boot.. Matter of fact, while trying to boot it, everything got hung up on these damn read-seek-can't seek drive_not_ready DMA_intr_timer_not-ready blah blah blah errors! Errors everywhere!
this is ridiculous.
