how to trick kernel: ata1.00: both IDENTIFYs aborted, assuming NODEV
by icegood from LinuxQuestions.org on (#5GEGG)
Hi there.
I'm ddrescue-ing my old SATA HDD and everything was fine till today until I moved to
some group of bad sectors.
I cannot detect my hdd anymore in Linux :
Code:[ 1.523611] ata1: SATA max UDMA/133 abar m2048@0xda133000 port 0xda133100 irq 126
[ 1.837502] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.838024] ata1.00: both IDENTIFYs aborted, assuming NODEVI still can detect it via BIOS and even read partition table via external SATA --> USB connection. Still, I cannot ddrescue it correctly in this case as it hangs as described there.
So, how can I trick my kernel so it will detect partition tables again via internal SATA connection?
Maybe i could even change the kernel source for short time for this case only?
As i understand from the web it might just relate to some timeouts.
I'm ddrescue-ing my old SATA HDD and everything was fine till today until I moved to
some group of bad sectors.
I cannot detect my hdd anymore in Linux :
Code:[ 1.523611] ata1: SATA max UDMA/133 abar m2048@0xda133000 port 0xda133100 irq 126
[ 1.837502] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.838024] ata1.00: both IDENTIFYs aborted, assuming NODEVI still can detect it via BIOS and even read partition table via external SATA --> USB connection. Still, I cannot ddrescue it correctly in this case as it hangs as described there.
So, how can I trick my kernel so it will detect partition tables again via internal SATA connection?
Maybe i could even change the kernel source for short time for this case only?
As i understand from the web it might just relate to some timeouts.