1 |
On Sat, Jul 31, 2010 at 3:14 PM, Volker Armin Hemmann < |
2 |
volkerarmin@××××××××××.com> wrote: |
3 |
|
4 |
> On Samstag 31 Juli 2010, Mick wrote: |
5 |
> > On Saturday 31 July 2010 19:04:47 Volker Armin Hemmann wrote: |
6 |
> > > On Samstag 31 Juli 2010, Mick wrote: |
7 |
> > > > On Saturday 31 July 2010 16:33:18 Dale wrote: |
8 |
> > > > > Kacper Kopczyński wrote: |
9 |
> > > > > > Dnia 2010-07-31, o godz. 16:15:51 |
10 |
> > > > > > |
11 |
> > > > > > Volker Armin Hemmann<volkerarmin@××××××××××.com> napisał(a): |
12 |
> > > > > >> On Samstag 31 Juli 2010, Kacper Kopczyński wrote: |
13 |
> > > > > >>> Hi, |
14 |
> > > > > >>> |
15 |
> > > > > >>> My problem is really strange - I can't access my hard drive |
16 |
> from |
17 |
> > > > > >>> linux, but it works from windows without problems. It has some |
18 |
> > > > > >>> bad blocks. |
19 |
> > > > > >> |
20 |
> > > > > >> it has a lot of bad blocks and a fucked up firmware it seems. No |
21 |
> > > > > >> way it is working 'without problems'. |
22 |
> > > > > > |
23 |
> > > > > > Well total space taken by bad blocks according to chkdsk is less |
24 |
> > > > > > than 1MB, windows is still able to access all data. Linux is only |
25 |
> > > > > > able to see partition table "for a while" - as you can see in |
26 |
> > > > > > dmesg. |
27 |
> > > > > > |
28 |
> > > > > > If firmware is broken then how it is possible that windows is |
29 |
> able |
30 |
> > > > > > to use this disk? |
31 |
> > > > > |
32 |
> > > > > Maybe windoze is ignoring the problem? It's not like windoze has |
33 |
> > > > > never done that before right? |
34 |
> > > > > |
35 |
> > > > > Just a thought. |
36 |
> > > > |
37 |
> > > > Couldn't it be that the MSWindows partition has no bad blocks, while |
38 |
> > > > Linux does? |
39 |
> > > |
40 |
> > > it is not about partitions. |
41 |
> > |
42 |
> > Please explain, I thought that bad blocks would coincide with some |
43 |
> > partitions. |
44 |
> |
45 |
> because defectice partitions don't give you no sense errors nor do they |
46 |
> give |
47 |
> you zero capacity errors. Read his dmesg. |
48 |
> |
49 |
> If the firmware/logic board is bad, you might be able to replace it with |
50 |
one from the same model. I've heard of some success from a coworker who |
51 |
took the logic board from a known good drive and put it on a HDD with good |
52 |
internals but a bad logic board, and it worked. That's if you need the |
53 |
data, that is. |
54 |
|
55 |
- Mark Shields |