Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
On Sat, 23 Dec 2006 01:23:13 +, Alan E. Davis wrote: > Can anyone point me to the right literature on line or other help? It > could be a hardware problem, but one suspects the partition table and > boot record. Gpart was unable to determine the sector size. Try running cfdisk with the -z option. This ignores the MBR and starts afresh with a blank one. If that fails, try zeroing the MBR with dd if=/dev/zero of=/dev/hdX bs=512 count=1 If it still fails, it would appear to be a broken disk. -- Neil Bothwick To most people solutions mean finding the answers. But to chemists solutions are things that are still all mixed up. signature.asc Description: PGP signature
Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
Thank you, Neil: Neither of these worked: # dd if=/dev/zero of=/dev/hda bs=512 count=1 dd: writing `/dev/hda': Input/output error 1+0 records in 0+0 records out 0 bytes (0 B) copied, 3.96744 seconds, 0.0 kB/s gparted shows the whole disk as unallocated. When I try to install a new partition, it wants to install a disklabel. The attempt fails. What I don't understand---this happened after installing Sabayon on /dev/hda8. The first time I downloaded sabayon (mini x86) the md5sum was incorrect, but the install tried to work. The second time, with a correct md5sum, I tried to install on /dev/hda1, with errors on that partition. Then, I reinstalled on /dev/hda8. The install seemed to go really quickly, perhaps TOO quickly. Then, ever since rebooting, the system knows there's a disk. But something isn't right. I am starting to wonder whether a virus or trojan was hitchhiking on the blown iso download? Very seldom does wget fail. I think the download may have been resumed from a different mirror. I don't know where to go from here. Maybe try some other install cds. Maybe back to a gentoo CD. Thank you again. Alan On 12/23/06, Neil Bothwick <[EMAIL PROTECTED]> wrote: On Sat, 23 Dec 2006 01:23:13 +, Alan E. Davis wrote: > Can anyone point me to the right literature on line or other help? It > could be a hardware problem, but one suspects the partition table and > boot record. Gpart was unable to determine the sector size. Try running cfdisk with the -z option. This ignores the MBR and starts afresh with a blank one. If that fails, try zeroing the MBR with dd if=/dev/zero of=/dev/hdX bs=512 count=1 If it still fails, it would appear to be a broken disk. -- Neil Bothwick To most people solutions mean finding the answers. But to chemists solutions are things that are still all mixed up. -- Alan Davis, Kagman High School, Saipan [EMAIL PROTECTED] 1-670-256-2043 I consider that the golden rule requires that if I like a program I must share it with other people who like it. Richard Stallman -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
Alan E. Davis wrote: > Thank you, Neil: > > Neither of these worked: > > # dd if=/dev/zero of=/dev/hda bs=512 count=1 > dd: writing `/dev/hda': Input/output error > 1+0 records in > 0+0 records out > 0 bytes (0 B) copied, 3.96744 seconds, 0.0 kB/s > > gparted shows the whole disk as unallocated. When I try to install a > new partition, it wants to install a disklabel. The attempt fails. > > > What I don't understand---this happened after installing Sabayon on > /dev/hda8. The first time I downloaded sabayon (mini x86) the md5sum > was incorrect, but the install tried to work. The second time, with a > correct md5sum, I tried to install on /dev/hda1, with errors on that > partition. Then, I reinstalled on /dev/hda8. The install seemed to > go really quickly, perhaps TOO quickly. Then, ever since rebooting, > the system knows there's a disk. But something isn't right. > > I am starting to wonder whether a virus or trojan was hitchhiking on > the blown iso download? Very seldom does wget fail. I think the > download may have been resumed from a different mirror. > > I don't know where to go from here. Maybe try some other install cds. > Maybe back to a gentoo CD. > > Thank you again. > > Alan > > > On 12/23/06, Neil Bothwick <[EMAIL PROTECTED]> wrote: >> On Sat, 23 Dec 2006 01:23:13 +, Alan E. Davis wrote: >> >> > Can anyone point me to the right literature on line or other help? It >> > could be a hardware problem, but one suspects the partition table and >> > boot record. Gpart was unable to determine the sector size. >> >> Try running cfdisk with the -z option. This ignores the MBR and starts >> afresh with a blank one. If that fails, try zeroing the MBR with >> dd if=/dev/zero of=/dev/hdX bs=512 count=1 >> >> If it still fails, it would appear to be a broken disk. >> >> >> -- >> Neil Bothwick >> >> To most people solutions mean finding the answers. But to chemists >> solutions are things that are still all mixed up. >> >> >> > > I suspect your HDD is dead. Send the boot messages here - they may contain some useful info. dmesg > dmsg.log #and attach "dmsg.log" -- Best regards, Daniel -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
Hi,
These type of messages:
[17180157.02] hda: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
[17180157.02] hda: dma_intr: error=0x40 { UncorrectableError },
LBAsect=5, high=0, low=5, sector=0
[17180157.02] ide: failed opcode was: unknown
[17180157.02] end_request: I/O error, dev hda, sector 0
are very bad signs. Nine times out of ten it means the drive is dead,
or nearly so. The few times it's not a dead/dying drive, is usually due
to dma not being supported, or a bad cable. Given that dd is not
working, and nothing seems able to actually write to the drive, I'm
leaning towards a dead drive.
As a last ditch attempt, you could try reseating the power and ide
cable on the drive, as well as the motherboard end of the ide cable. If
you have another system laying around, you could put the problem drive
in there to confirm it is a drive problem.
HTH,
PaulNM
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
On Sat, 23 Dec 2006 23:22:02 +, Alan E. Davis wrote: > Neither of these worked: > > # dd if=/dev/zero of=/dev/hda bs=512 count=1 > dd: writing `/dev/hda': Input/output error > 1+0 records in > 0+0 records out > 0 bytes (0 B) copied, 3.96744 seconds, 0.0 kB/s > > gparted shows the whole disk as unallocated. When I try to install a > new partition, it wants to install a disklabel. The attempt fails. It looks like a dead disk to me :( -- Neil Bothwick Documentation: (n.) a novel sold with software, designed to entertain the operator during episodes of bugs or glitches. signature.asc Description: PGP signature
Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
It's looking really bad. However, I have seen some messages about similar messages/problems being addressed by flashing the bios. I have received a diagnostic utility from Gateway. This is a laptop. Thank you for the advice. I'll keep trying. Merry Christmas (in an hour, here in the W. Pacific), Alan On 12/24/06, Neil Bothwick <[EMAIL PROTECTED]> wrote: On Sat, 23 Dec 2006 23:22:02 +, Alan E. Davis wrote: > Neither of these worked: > > # dd if=/dev/zero of=/dev/hda bs=512 count=1 > dd: writing `/dev/hda': Input/output error > 1+0 records in > 0+0 records out > 0 bytes (0 B) copied, 3.96744 seconds, 0.0 kB/s > > gparted shows the whole disk as unallocated. When I try to install a > new partition, it wants to install a disklabel. The attempt fails. It looks like a dead disk to me :( -- Neil Bothwick Documentation: (n.) a novel sold with software, designed to entertain the operator during episodes of bugs or glitches. -- Alan Davis, Kagman High School, Saipan [EMAIL PROTECTED] 1-670-256-2043 I consider that the golden rule requires that if I like a program I must share it with other people who like it. Richard Stallman
Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
On Sunday 24 December 2006 08:42, PaulNM wrote:
> Hi,
>
> These type of messages:
>
> [17180157.02] hda: dma_intr: status=0x51 { DriveReady SeekComplete
> Error }
> [17180157.02] hda: dma_intr: error=0x40 { UncorrectableError },
> LBAsect=5, high=0, low=5, sector=0
> [17180157.02] ide: failed opcode was: unknown
> [17180157.02] end_request: I/O error, dev hda, sector 0
>
>
> are very bad signs. Nine times out of ten it means the drive is dead,
> or nearly so. The few times it's not a dead/dying drive, is usually due
> to dma not being supported, or a bad cable. Given that dd is not
> working, and nothing seems able to actually write to the drive, I'm
> leaning towards a dead drive.
>
> As a last ditch attempt, you could try reseating the power and ide
> cable on the drive, as well as the motherboard end of the ide cable. If
> you have another system laying around, you could put the problem drive
> in there to confirm it is a drive problem.
I agree that in all likelihood your HD is toast. However, before you start
searching on Ebay you would better follow the above advice to reseat cables
and, or sockets. I used to have an IBM laptop with a problematic floppy
drive that needed reseating in its socket every now and then to cure its boot
problems.
--
Regards,
Mick
pgpcMTFFlV3zR.pgp
Description: PGP signature
RE: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
I am maybe "late to the party" here but for specific types of disk failure the
freezer trick can work briefly if you have any data to recover (looks unlikely
in this case but thought I'd mention it). I did this for my friends laptop
drive a few weeks ago so he could back his stuff up to my box via Samba - the
drive was shoved in a plastic sealed bag with as much air squeezed out as
possible and left in a freezer for a few days. It lived for an hour and a half
before dying again.
(Note: the failure in this case involved the drive making a rather horrid
grinding noise)
In a rather cruel case of Murphy's law, one of my hard disks died the following
week, taking his backup with it. Nice.
David
Note: These views are my own, advice is provided with no guarantee of success.
I do not represent anyone else in any emails I send to this list.
> -Original Message-
> From: Mick [mailto:[EMAIL PROTECTED]
> Sent: 24 December 2006 13:09
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] desperation question: disklabel, unable to
> write to disk, etc.
>
>
> On Sunday 24 December 2006 08:42, PaulNM wrote:
> > Hi,
> >
> > These type of messages:
> >
> > [17180157.02] hda: dma_intr: status=0x51 { DriveReady
> SeekComplete
> > Error }
> > [17180157.02] hda: dma_intr: error=0x40 { UncorrectableError },
> > LBAsect=5, high=0, low=5, sector=0
> > [17180157.02] ide: failed opcode was: unknown
> > [17180157.02] end_request: I/O error, dev hda, sector 0
> >
> >
> > are very bad signs. Nine times out of ten it means the
> drive is dead,
> > or nearly so. The few times it's not a dead/dying drive,
> is usually due
> > to dma not being supported, or a bad cable. Given that dd is not
> > working, and nothing seems able to actually write to the drive, I'm
> > leaning towards a dead drive.
> >
> > As a last ditch attempt, you could try reseating the
> power and ide
> > cable on the drive, as well as the motherboard end of the
> ide cable. If
> > you have another system laying around, you could put the
> problem drive
> > in there to confirm it is a drive problem.
>
> I agree that in all likelihood your HD is toast. However,
> before you start
> searching on Ebay you would better follow the above advice to
> reseat cables
> and, or sockets. I used to have an IBM laptop with a
> problematic floppy
> drive that needed reseating in its socket every now and then
> to cure its boot
> problems.
>
> --
> Regards,
> Mick
>
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
I am still in limbo about this drive. I have gotten a disk scanning utility
from Gateway, and am now trying to get together a floppy to test it that
way.
I have had another HDD issue this week, on a SATA drive. I may post
separately about that. I can see partitions from Ubuntu that I cannot see
from Gentoo. Etc. Back to the laptop. I hope for the best, and suspect
that somehow the disk was corrupted by software, and if so I HOPE it can be
recovered. Otherwise, I guess I can run a live cd and save files to a usb
flash drive! I haven't heard any strange noises, but the freezer trick
would certainly be a last resort.
Alan
On 1/3/07, Nelson, David (ED, PAR&D) <[EMAIL PROTECTED]> wrote:
I am maybe "late to the party" here but for specific types of disk failure
the freezer trick can work briefly if you have any data to recover (looks
unlikely in this case but thought I'd mention it). I did this for my friends
laptop drive a few weeks ago so he could back his stuff up to my box via
Samba - the drive was shoved in a plastic sealed bag with as much air
squeezed out as possible and left in a freezer for a few days. It lived for
an hour and a half before dying again.
(Note: the failure in this case involved the drive making a rather horrid
grinding noise)
In a rather cruel case of Murphy's law, one of my hard disks died the
following week, taking his backup with it. Nice.
David
Note: These views are my own, advice is provided with no guarantee of
success. I do not represent anyone else in any emails I send to this list.
> -Original Message-
> From: Mick [mailto:[EMAIL PROTECTED]
> Sent: 24 December 2006 13:09
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] desperation question: disklabel, unable to
> write to disk, etc.
>
>
> On Sunday 24 December 2006 08:42, PaulNM wrote:
> > Hi,
> >
> > These type of messages:
> >
> > [17180157.02] hda: dma_intr: status=0x51 { DriveReady
> SeekComplete
> > Error }
> > [17180157.02] hda: dma_intr: error=0x40 { UncorrectableError },
> > LBAsect=5, high=0, low=5, sector=0
> > [17180157.02] ide: failed opcode was: unknown
> > [17180157.02] end_request: I/O error, dev hda, sector 0
> >
> >
> > are very bad signs. Nine times out of ten it means the
> drive is dead,
> > or nearly so. The few times it's not a dead/dying drive,
> is usually due
> > to dma not being supported, or a bad cable. Given that dd is not
> > working, and nothing seems able to actually write to the drive, I'm
> > leaning towards a dead drive.
> >
> > As a last ditch attempt, you could try reseating the
> power and ide
> > cable on the drive, as well as the motherboard end of the
> ide cable. If
> > you have another system laying around, you could put the
> problem drive
> > in there to confirm it is a drive problem.
>
> I agree that in all likelihood your HD is toast. However,
> before you start
> searching on Ebay you would better follow the above advice to
> reseat cables
> and, or sockets. I used to have an IBM laptop with a
> problematic floppy
> drive that needed reseating in its socket every now and then
> to cure its boot
> problems.
>
> --
> Regards,
> Mick
>
--
gentoo-user@gentoo.org mailing list
--
Alan Davis, Kagman High School, Saipan [EMAIL PROTECTED] 1-670-256-2043
I consider that the golden rule requires that if I like a program I must
share it with other people who like it. Richard
Stallman
Every great advance in natural knowledge has involved the absolute rejection
of authority. - Thomas H. Huxley
RE: [gentoo-user] desperation question: disklabel, unable to write to disk, etc.
-Original Message- From: Alan E. Davis [mailto:[EMAIL PROTECTED] Sent: 03 January 2007 11:50 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] desperation question: disklabel, unable to write to disk, etc. > I am still in limbo about this drive. I have gotten a disk scanning utility > from Gateway, and am now trying to get together a floppy to test it that way. > > > I have had another HDD issue this week, on a SATA drive. I may post > separately about that. I can see partitions from Ubuntu that I > cannot see from Gentoo. Etc. Back to the laptop. I hope for the best, and > suspect that somehow the disk was corrupted by software, > and if so I HOPE it can be recovered. Otherwise, I guess I can run a live > cd and save files to a usb flash drive! I haven't heard any > strange noises, but the freezer trick would certainly be a last resort. Sounds like some sort of driver issue then surely? Or a kernel config issue. I can't say more than that about it I'm afraid - I'm not entirely sure. David Note: These views are my own, advice is provided with no guarantee of success. I do not represent anyone else in any emails I send to this list.
