What the heck is this:

-> Y'day a linux server started logging ext3FS errors about inode
access denied, or unable to... Later, after a reboot the SCSI Bus Scan
stated Failed at the disk status, later i changed the disk to another
adapter (LSI MPT-IM) and the disk gets detected but linux 2.4.29 says
this:

sdb: Spinning up
disk.............................................. .................................................. .......not
responding...
sdb : READ CAPACITY failed.
sdb : status = 1, message = 00, host = 0, driver = 28
Current sd00:00: sns = 70 2
ASC=40 ASCQ=85
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x18 0x00 0x00 0x00
0x00 0x40 0x85 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x80 0x00 0x25 0x00
0x00 0x00 0x00 0x00 0x00 0x00 0x00
sdb : block size assumed to be 512 bytes, disk size 1GB.
sdb:SCSI Error: (0:12:0) Status=02h (CHECK CONDITION)
Key=2h (NOT READY); FRU=00h
ASC/ASCQ=40h/85h ""
CDB: 28 00 00 00 00 00 00 00 08 00

Device 08:10 not ready.
I/O error: dev 08:10, sector 0
SCSI Error: (0:12:0) Status=02h (CHECK CONDITION)
Key=2h (NOT READY); FRU=00h
ASC/ASCQ=40h/85h ""
CDB: 28 00 00 00 00 00 00 00 08 00

Device 08:10 not ready.
I/O error: dev 08:10, sector 0
unable to read partition table

THIS IS TOTALLY FU**ED UP --> this disk contains too much important
data, and there is no backup available ...
HELP!!!!!!!!!!

Mr. Boy wrote:

> THIS IS TOTALLY FU**ED UP --> this disk contains too much important
> data, and there is no backup available ...

Looks like a hardware issue, the drive is dying/almost dead. Good luck, and
implement backups next time.

On 8 Jul 2005 13:33:49 -0700, "Mr. Boy" <mrboy77@gmail.com> wrote:
>
> THIS IS TOTALLY FU**ED UP --> this disk contains too much important
> data, and there is no backup available ...
> HELP!!!!!!!!!!

If you in data recovery mode, stop _writing_anything_ to the drive,
think in terms of booting slack-install or rescue cdrom and reading
HDD to another drive in box or another box via network. This is
important if the drive is failing.

If you cannot mount partition, take an image of the raw partition
and play with it on another HDD or machine, loopback mount image.

Take two copies of partition and diff them, if they different you
in trouble, drive / hardware failing. If they same then some soft
glitch happened (stuff happens).

At least with ext3 you can convert to / mount as ext2 and use some
ext2 data recovery tools out there.


Important data is on removable media, anything else simply
takes time to download again. Redefine important data ).

--Grant.

On Sat, 09 Jul 2005 07:05:32 +1000, Grant Coady <grant_lkml@dodo.com.au> wrote:
more on:
>Take two copies of partition and diff them, if they different you
>in trouble, drive / hardware failing. If they same then some soft
>glitch happened (stuff happens).

Look for the modified 'dd' that skips bad sectors without retry,
otherwise taking the image may kill a failing drive due to excessive
retries. Lots of info on the 'net. Take it calmly.

--Grant.

i would do a raw access to the disk (good idea by the way) but i cannot
access the disk at all, do you know any special way to force access or
something similar... ????

the backup is not available because the IT a$$hole (is not me) never
changes the tapes, and never follows the backup plan... the last backup
is 3 months old!

Thanks, Buddies!

On 8 Jul 2005 14:40:23 -0700, "Mr. Boy" <mrboy77@gmail.com> wrote:
> i would do a raw access to the disk (good idea by the way) but i cannot
> access the disk at all, do you know any special way to force access or
> something similar... ????

Is it the drive or the controller? Try drive in another machine,
don't bother trying to mount it, try looking at MBR, example:

deltree:~$ dd if=/dev/hda bs=512 count=1 | xxd
1+0 records in
1+0 records out
0000000: faeb 2101 b401 4c49 4c4f 1605 bde6 cc42 ..!...LILO.....B <<== bootloader
....
00001c0: 0100 837f 3f03 3f00 0000 c17d 0000 0000 ....?.?....}.... <<== partitions
00001d0: 0104 827f 3f1b 007e 0000 00f4 0200 0000 ....?..~........
00001e0: 011c 837f 3fbf 0072 0300 002e 1400 0000 ....?..r........
00001f0: 01c0 057f ff10 00a0 1700 80f7 4800 55aa ............H.U.
^^^^--> signature

and see if it look like an MBR. Cable / termination check, also,
anyone been inside box recently? I don't recognise the error messages,
haven't used SCSI since narrow 50-way scsi-2

Disk errors doing this step means trouble... OTOH if no disk error
reading MBR try data recovery of unmounted drive first. Been 18 months
since I last done a recovery, me rusty.

--Grant.

Mr. Boy wrote:

> What the heck is this:
>
> -> Y'day a linux server started logging ext3FS errors about inode
> access denied, or unable to... Later, after a reboot the SCSI Bus Scan
> stated Failed at the disk status, later i changed the disk to another
> adapter (LSI MPT-IM) and the disk gets detected but linux 2.4.29 says
> this:
>
> sdb: Spinning up
>
disk.............................................. .................................................. .......not
> responding...
> sdb : READ CAPACITY failed.
> sdb : status = 1, message = 00, host = 0, driver = 28
> Current sd00:00: sns = 70 2
> ASC=40 ASCQ=85
> Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x18 0x00 0x00 0x00
> 0x00 0x40 0x85 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x80 0x00 0x25 0x00
> 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> sdb : block size assumed to be 512 bytes, disk size 1GB.
> sdb:SCSI Error: (0:12:0) Status=02h (CHECK CONDITION)
> Key=2h (NOT READY); FRU=00h
> ASC/ASCQ=40h/85h ""
> CDB: 28 00 00 00 00 00 00 00 08 00
>
> Device 08:10 not ready.
> I/O error: dev 08:10, sector 0
> SCSI Error: (0:12:0) Status=02h (CHECK CONDITION)
> Key=2h (NOT READY); FRU=00h
> ASC/ASCQ=40h/85h ""
> CDB: 28 00 00 00 00 00 00 00 08 00
>
> Device 08:10 not ready.
> I/O error: dev 08:10, sector 0
> unable to read partition table

Depending in the importance of the data... take your hands off the drive,
get it out of the machine and get it to a professional recovery place. They
charge outrageous fees, but usually they can get your data - if the disk
isn't totally f'd up already by excessive tries to get to said data.

Oh, and fire that IT dork ASAP and load the bill on him for criminal
negligence of duties.


Good luck
J

On 2005-07-08, Jennifer Smith <jennifer@cathouse.mine.nu> wrote:
>
> Depending in the importance of the data... take your hands off the drive,
> get it out of the machine and get it to a professional recovery place. They
> charge outrageous fees, but usually they can get your data - if the disk

Outrageous is an understatement. I got a quote once from one of those clean
room places...$1200 and NO guarantees.

ken

No_One wrote:
> On 2005-07-08, Jennifer Smith <jennifer@cathouse.mine.nu> wrote:
>
>>Depending in the importance of the data... take your hands off the drive,
>>get it out of the machine and get it to a professional recovery place. They
>>charge outrageous fees, but usually they can get your data - if the disk
>
>
> Outrageous is an understatement. I got a quote once from one of those clean
> room places...$1200 and NO guarantees.
>

I got a quote from Ontrack for a friend's college laptop, a
20 gig Travelstar:

$100 to evaluate it, then $500 to $2,100 to retrieve anything that's
retrievable.

Ouch!

On Fri, 08 Jul 2005 19:39:23 -0500, Chris Sorenson <csoren@isd.net> wrote:
>I got a quote from Ontrack for a friend's college laptop, a
>20 gig Travelstar:
>
>$100 to evaluate it, then $500 to $2,100 to retrieve anything that's
>retrievable.

Fair price, last time I scored the laptop in return for the
recovered data. Several days' investigation and planning
least damaging approach. Which meant of course not putting
the HDD anywhere near another windows box. )

--Grant.