Forgot your password?
typodupeerror

Submission Summary: 0 pending, 4 declined, 0 accepted (4 total, 0.00% accepted)

+ - Recovering a drive on the cheap

Submitted by kantos
kantos (1314519) writes "I have a hard drive that that as best I can tell is a brick... I figured that I would ask slashdot before I turned the platters into sun catchers for my patio.

The drive in question is a WD1000BB-00CAA0 and this is what shows up in syslog on boot: Feb 2 05:54:56 Jester kernel: [ 115.982684] ata1.00: BMDMA stat 0x25 Feb 2 05:54:56 Jester kernel: [ 115.982691] ata1.00: failed command: READ DMA Feb 2 05:54:56 Jester kernel: [ 115.982706] ata1.00: cmd c8/00:08:00:00:00/00: 00:00:00:00/e0 tag 0 dma 4096 in Feb 2 05:54:56 Jester kernel: [ 115.982710] res 51/10:08:00:00:00/00: 00:00:00:00/e0 Emask 0x81 (invalid argument) Feb 2 05:54:56 Jester kernel: [ 115.982717] ata1.00: status: { DRDY ERR } Feb 2 05:54:56 Jester kernel: [ 115.982723] ata1.00: error: { IDNF } Feb 2 05:54:56 Jester kernel: [ 116.041376] ata1.00: configured for UDMA/100 Feb 2 05:54:56 Jester kernel: [ 116.041407] ata1: EH complete Feb 2 05:54:56 Jester kernel: [ 116.042651] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 2 05:54:56 Jester kernel: [ 116.042658] ata1.00: BMDMA stat 0x25 Feb 2 05:54:56 Jester kernel: [ 116.042665] ata1.00: failed command: READ DMA Feb 2 05:54:56 Jester kernel: [ 116.042680] ata1.00: cmd c8/00:08:00:00:00/00: 00:00:00:00/e0 tag 0 dma 4096 in Feb 2 05:54:56 Jester kernel: [ 116.042684] res 51/10:08:00:00:00/00: 00:00:00:00/e0 Emask 0x81 (invalid argument) Feb 2 05:54:56 Jester kernel: [ 116.042691] ata1.00: status: { DRDY ERR } Feb 2 05:54:56 Jester kernel: [ 116.042697] ata1.00: error: { IDNF } Feb 2 05:54:56 Jester kernel: [ 116.102657] ata1.00: configured for UDMA/100 Feb 2 05:54:56 Jester kernel: [ 116.102687] sd 0:0:0:0: [sda] Result: hostbyte =DID_OK driverbyte=DRIVER_SENSE Feb 2 05:54:56 Jester kernel: [ 116.102696] sd 0:0:0:0: [sda] Sense Key : Abor ted Command [current] [descriptor] Feb 2 05:54:56 Jester kernel: [ 116.102707] Descriptor sense data with sense d escriptors (in hex): Feb 2 05:54:56 Jester kernel: [ 116.102712] 72 0b 14 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 2 05:54:56 Jester kernel: [ 116.102735] 00 00 00 00 Feb 2 05:54:56 Jester kernel: [ 116.102744] sd 0:0:0:0: [sda] Add. Sense: Reco rded entity not found Feb 2 05:54:56 Jester kernel: [ 116.102754] sd 0:0:0:0: [sda] CDB: Read(10): 2 8 00 00 00 00 00 00 00 08 00 Feb 2 05:54:56 Jester kernel: [ 116.102774] end_request: I/O error, dev sda, s ector 0 Feb 2 05:54:56 Jester kernel: [ 116.102784] Buffer I/O error on device sda, lo gical block 0 Feb 2 05:54:56 Jester kernel: [ 116.102843] ata1: EH complete Feb 2 05:54:56 Jester kernel: [ 116.166764] type=1400 audit(1296651296.883:23)

So slashdot.... is this drive beyond all hope other than a data recovery specialists jig, or is there some way I can get at least something off this drive?"
Microsoft

+ - Zero day bug found in Windows 7 and Server 2008...->

Submitted by kantos
kantos (1314519) writes "Security researcher Laurent Graffie, responsible for finding the early SMB2 remote BSOD exploit, has done it again. As reported by Information Week the exploit can be triggered through IE or remotely. In his blog Graffie notes that the exploit doesn't even cause a BSOD rather it forces the OS into an infinite loop requiring a hard reset. MS of course has played down the issue saying that few if any of its customers will be affected...."
Link to Original Source

For every bloke who makes his mark, there's half a dozen waiting to rub it out. -- Andy Capp

Working...