Personal computing discussed

Moderators: renee, mac_h8r1, Nemesis

 
churin
Gerbil Elite
Topic Author
Posts: 738
Joined: Wed Nov 28, 2007 4:38 pm
Location: CA

Partition became "RAW"

Sun Jun 16, 2013 10:18 pm

One of the data partitions all of a sudden became "RAW". I have been using this 1G hard drive for three months and noticed chkdsk run frequently. I wonder if I should replace this hard drive.
 
MadManOriginal
Gerbil Jedi
Posts: 1533
Joined: Wed Jan 30, 2002 7:00 pm
Location: In my head...

Re: Partition became "RAW"

Sun Jun 16, 2013 10:52 pm

Um, yeah, probably, unless you got a virus of some sort or did something yourself that might have wiped it out. Run the manufacturer diagnostic tool on it to see.
 
JustAnEngineer
Gerbil God
Posts: 19673
Joined: Sat Jan 26, 2002 7:00 pm
Location: The Heart of Dixie

Re: Partition became "RAW"

Sun Jun 16, 2013 10:53 pm

It's long past time to replace any 1 GB (0.001 TB) drives that you may still have. I suggest a 2.0 or 3.0 TB hard-drive or a 0.250 TB SSD as a replacement.
· R7-5800X, Liquid Freezer II 280, RoG Strix X570-E, 64GiB PC4-28800, Suprim Liquid RTX4090, 2TB SX8200Pro +4TB S860 +NAS, Define 7 Compact, Super Flower SF-1000F14TP, S3220DGF +32UD99, FC900R OE, DeathAdder2
 
just brew it!
Administrator
Posts: 54500
Joined: Tue Aug 20, 2002 10:51 pm
Location: Somewhere, having a beer

Re: Partition became "RAW"

Sun Jun 16, 2013 11:33 pm

Have you run the manufacturer's diagnostics?

Corrupted partitions can be caused by a lot of things -- bad drive, bad SATA cable, bad SATA controller, overclocking, flaky power, and bad RAM are all potential culprits. Have you seen any other signs of system instability, or are you only having issues with this one data drive?
Nostalgia isn't what it used to be.
 
churin
Gerbil Elite
Topic Author
Posts: 738
Joined: Wed Nov 28, 2007 4:38 pm
Location: CA

Re: Partition became "RAW"

Wed Jun 19, 2013 5:04 am

I am having difficulty getting diagnostic utility from the vendor. The problem is with a machine of my relatives where I am visiting. I decided to replace it with a new one of a different brand.
Thanks to all responded.
 
PenGun
Gerbil Elite
Posts: 893
Joined: Fri Jun 18, 2004 1:48 pm
Location: BC Canada
Contact:

Re: Partition became "RAW"

Wed Jun 19, 2013 12:09 pm

JustAnEngineer wrote:
It's long past time to replace any 1 GB (0.001 TB) drives that you may still have. I suggest a 2.0 or 3.0 TB hard-drive or a 0.250 TB SSD as a replacement.

One 3 TB drive takes a lot with it when it dies. A few 1 TB drives with data scattered redundantly about the place is more resilient.

Oh no, because backups. ;)
Fuji X-E1 Leica Elmar 135 4 XF60mm 2.4 Macro | Zeiss FE 35mm 2.8
http://carnagepro.com
"Everything ... they eat everything, and fear is their bacon bits."
 
churin
Gerbil Elite
Topic Author
Posts: 738
Joined: Wed Nov 28, 2007 4:38 pm
Location: CA

Re: Partition became "RAW"

Wed Jun 26, 2013 6:32 am

I replaced the hard drive as previously posted but the exact same problem symptoms remained. The symptoms include frequent CHKDSK running, data partition becoming "RAW", OS becoming no boot, system freezing, etc.

I ran Memtest and it reported errors. I ran Memtest for one module at a time and found one of the pair did not generate error.

I tried one which did not report error and found the system was stable.

I got a new pair of RAM module of a different brand, ran Memtest and found that this pair also generated error. I went ahead and tried this new pair to find that the system is just as stable as when one of the old pair was used as above. The following is a screen shot of the Memtest. The error happened always at the Test #6 with new pair or old pair. It appears that culprit of this problem is bad RAM. I wonder why the new RAM pair does not cause instability even the Memtest reports errors.
Image
 
notfred
Maximum Gerbil
Posts: 4610
Joined: Tue Aug 10, 2004 10:10 am
Location: Ottawa, Canada

Re: Partition became "RAW"

Wed Jun 26, 2013 8:37 am

It's going to be about the access pattern (i.e. combination of reads and writes) that triggers the error in the memory. The original sticks probably would fail under conditions that you are hitting commonly when running normally, whilst the new sticks may only fail under a particular access pattern that you are not happening to hit.
 
churin
Gerbil Elite
Topic Author
Posts: 738
Joined: Wed Nov 28, 2007 4:38 pm
Location: CA

Re: Partition became "RAW"

Wed Jun 26, 2013 4:56 pm

notfred wrote:
It's going to be about the access pattern (i.e. combination of reads and writes) that triggers the error in the memory. The original sticks probably would fail under conditions that you are hitting commonly when running normally, whilst the new sticks may only fail under a particular access pattern that you are not happening to hit.

Does this mean that why no problem with the new sticks was that the machine was not used exactly the same way as when the old sticks were used?

True that the way I used the machine was not exactly the same but generally the same way because I was testing the machine which I just built. Also it is generally unlikely that the two different brands of new RAMs have the same type of defect as reported by the diagnostic utility. With the old sticks the problem symptoms happened consistently, while with the new sticks the problem never happened for two consecutive days.
Last edited by churin on Wed Jun 26, 2013 6:22 pm, edited 1 time in total.
 
notfred
Maximum Gerbil
Posts: 4610
Joined: Tue Aug 10, 2004 10:10 am
Location: Ottawa, Canada

Re: Partition became "RAW"

Wed Jun 26, 2013 6:21 pm

churin wrote:
notfred wrote:
It's going to be about the access pattern (i.e. combination of reads and writes) that triggers the error in the memory. The original sticks probably would fail under conditions that you are hitting commonly when running normally, whilst the new sticks may only fail under a particular access pattern that you are not happening to hit.

Does this mean that why no problem with the new sticks was that the machine was not used exactly the same way as when the old sticks were used?

No, I mean that whilst the new pair fail, they only fail under slightly more stress than the new pair. How you use your machine is between the two points so in general use you see failures with the old but not with the new. Memtest is stressing the memory to the limit so it finds all the failures.

churin wrote:
Also it is generally unlikely that the two different brands of new RAMs have the same type of defect as reported by the diagnostic utility.
It could also be a problem in the memory controller (i.e. CPU), memory sockets or motherboard traces.
 
churin
Gerbil Elite
Topic Author
Posts: 738
Joined: Wed Nov 28, 2007 4:38 pm
Location: CA

Re: Partition became "RAW"

Wed Jun 26, 2013 8:44 pm

notfred wrote:
No, I mean that whilst the new pair fail, they only fail under slightly more stress than the new pair. How you use your machine is between the two points so in general use you see failures with the old but not with the new. Memtest is stressing the memory to the limit so it finds all the failures.

You appear to indicate that the extent of the defect of the new sticks is smaller so that I will eventually see the same problem. Is this correct?
churin wrote:
notfred wrote:
Also it is generally unlikely that the two different brands of new RAMs have the same type of defect as reported by the diagnostic utility.
It could also be a problem in the memory controller (i.e. CPU), memory sockets or motherboard traces.

I would think these hardware conditions can be considered the same since I only replaced the old sticks with the new sticks and everything else was unchanged.
 
notfred
Maximum Gerbil
Posts: 4610
Joined: Tue Aug 10, 2004 10:10 am
Location: Ottawa, Canada

Re: Partition became "RAW"

Thu Jun 27, 2013 9:18 am

churin wrote:
notfred wrote:
No, I mean that whilst the new pair fail, they only fail under slightly more stress than the new pair. How you use your machine is between the two points so in general use you see failures with the old but not with the new. Memtest is stressing the memory to the limit so it finds all the failures.

You appear to indicate that the extent of the defect of the new sticks is smaller so that I will eventually see the same problem. Is this correct?

Yes, you may be lucky and never see the issue again or it may crop up at some later point in time.
churin wrote:
notfred wrote:
It could also be a problem in the memory controller (i.e. CPU), memory sockets or motherboard traces.

I would think these hardware conditions can be considered the same since I only replaced the old sticks with the new sticks and everything else was unchanged.

True, but it could be a the new sticks are more tolerant of something being just slightly off in those components e.g. poor connection in the memory socket and new sticks have slightly better but still not good enough.

On the whole I think I would just RMA the new RAM sticks and try again to get a set that passes memtest without errors.

Who is online

Users browsing this forum: No registered users and 1 guest
GZIP: On