© J.C. Kessels 2009
MyDefrag Forum
May 24, 2013, 11:00:04 am
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News
:
Home
Help
Search
Login
Register
MyDefrag Forum
>
JkDefrag v3 Forum
>
Questions and help
>
vista 64 raid question
Pages: [
1
]
« previous
next »
Print
Author
Topic: vista 64 raid question (Read 3629 times)
moe
JkDefrag Junior
Posts: 7
vista 64 raid question
«
on:
January 09, 2009, 05:02:04 pm »
I get this in the log --- D: is a raid 0 dual channel, c: sata c: defrag ok any ideas?
HDtool did not reconize the raid on install. I rebooted then it dectected the raid, also ran the defrag again after reboot. log is attached.
10:38:45 Analyzing volume 'D:\'
10:38:45 Processing 'D:\*'
10:38:45 Opening volume '\\?\Volume{fc35b421-668e-11dd-bf29-00508db22c2d}' at mountpoint 'D:'
10:38:45 Input mask: D:\*
10:38:46 Phase 1: Analyze
10:38:46 This is an NTFS disk.
10:38:48 Phase 2: Defragment
10:40:27 ERROR: could not get volume bitmap: [21] The device is not ready.
10:40:27 ERROR: could not get volume bitmap: [21] The device is not ready.
10:40:27 Phase 3: Fixup
10:40:27 ERROR: could not get volume bitmap: [21] The device is not ready.
10:40:27 ERROR: could not get volume bitmap: [21] The device is not read
frag1.txt
(165.36 KB - downloaded 195 times.)
«
Last Edit: January 09, 2009, 05:42:02 pm by moe
»
Logged
jeroen
Administrator
JkDefrag Hero
Posts: 7155
Re: vista 64 raid question
«
Reply #1 on:
January 09, 2009, 08:16:15 pm »
Are you using the latest version of the drivers of your RAID controller? The error message "could not get volume bitmap" comes from the FSCTL_GET_VOLUME_BITMAP Microsoft defragmentation API call. JkDefrag only executes this call when it is looking for an empty gap on disk. I have never seen this message combined with "The device is not ready" message. Maybe the disks are running too hot?
Logged
moe
JkDefrag Junior
Posts: 7
Re: vista 64 raid question
«
Reply #2 on:
January 10, 2009, 07:06:48 pm »
Not sure if they are running to hot? This raid has been running 4-6 months and have not had any issues with programs on the drive, so far. Do have quite a few fans in my case 2-120, 2-pw supply fans, video fan, cpu fan, everything with temp sensors on it is on the cool side. I do have room for one more 120mm to blow on my drives, do not have a temp sensor on them?
Quote from: jeroen on January 09, 2009, 08:16:15 pm
Are you using the latest version of the drivers of your RAID controller? The error message "could not get volume bitmap" comes from the FSCTL_GET_VOLUME_BITMAP Microsoft defragmentation API call. JkDefrag only executes this call when it is looking for an empty gap on disk. I have never seen this message combined with "The device is not ready" message. Maybe the disks are running too hot?
Logged
jeroen
Administrator
JkDefrag Hero
Posts: 7155
Re: vista 64 raid question
«
Reply #3 on:
January 11, 2009, 05:50:40 am »
Quote from: moe on January 10, 2009, 07:06:48 pm
Not sure if they are running to hot?
Harddisks have internal temperature sensors that can be read with S.M.A.R.T. aware software. For example the HdTune utility that you used to measure the speed of your disks in another thread, will show the temperature of your disks (perhaps not of RAID configured harddisks, because those may be hidden behind the controller). Anything up to about 50 degrees celcius is ok. From your logfile I see that the messages occur after running for a while, that's why I thought it might be the temperature. A fan specially for the harddisks is a good idea and a good investment, cooler harddisks will live longer.
Logged
Harald
JkDefrag Senior
Posts: 33
Re: vista 64 raid question
«
Reply #4 on:
January 11, 2009, 11:01:13 am »
Quote from: jeroen on January 11, 2009, 05:50:40 am
cooler harddisks will live longer.
Actually, this may not necessarily be true. Quoting from a Google study (
http://research.google.com/archive/disk_failures.pdf
):
"One of our key findings has been the lack of a consistent pattern of higher failure rates for higher temperature drives or for those drives at higher utilization levels. Such correlations have been repeatedly highlighted by previous studies, but we are unable to confirm them by observing our population. Although our data do not allow us to conclude that there is no such correlation, it provides strong evidence to suggest that other effects may be more prominent in affecting disk drive reliability in the context of a professionally managed data center deployment."
Logged
moe
JkDefrag Junior
Posts: 7
Re: vista 64 raid question
«
Reply #5 on:
January 11, 2009, 07:30:27 pm »
Checked and cannot see any health info on the raid drives. I will invest in a drive fan, case has a 120mm socket to blow directly over drives. There is a 120mm in the front blowing into the drive, but the case allows for another fan to blow at a right angle to them.
Will also check to make sure software for the controller is up to date.
Logged
jeroen
Administrator
JkDefrag Hero
Posts: 7155
Re: vista 64 raid question
«
Reply #6 on:
January 12, 2009, 07:36:48 pm »
Quote from: hsteensland on January 11, 2009, 11:01:13 am
for higher temperature drives
I think the study refers to drives that get warmer by themselves as compared to drives that stay cooler, given the same circumstances. They were designed to run at a higher temperature, so I would expect the failure pattern to be designed to be the same. Also, the study is an analysis of a large population of disks used normally. It was not a laboratory test that focused on determining the circumstances that affect the lifespan of harddisks.
Logged
ABasketOfPups
JkDefrag Supporter
Posts: 12
Re: vista 64 raid question
«
Reply #7 on:
January 15, 2009, 10:17:59 pm »
I tend to believe the Google study, that drives aren't as affected by heat as has been rumored over the years. But having more fans in the case to improve airflow helps the whole box, including the CPU and the video card, so it's still worth putting some effort into cooling.
Logged
moe
JkDefrag Junior
Posts: 7
Re: vista 64 raid question
«
Reply #8 on:
February 16, 2009, 10:09:29 pm »
can someone look at the attachment - still do not know why the defrag is not defraging the raid0
All drivers are up to date. defrag works the same right after boot up or after several hours running.
JkDefragCmd64.log
(162.1 KB - downloaded 179 times.)
Logged
jeroen
Administrator
JkDefrag Hero
Posts: 7155
Re: vista 64 raid question
«
Reply #9 on:
February 17, 2009, 11:39:44 am »
Could you please run JkDefrag with the "-d 5" parameter? And only for disk "d:". This will write more information to the logfile and perhaps it will help me explain the problem. I don't think I will need the entire logfile, only a section around the first couple of error messages and the beginning and the end of the logfile.
Logged
Light768
Newbie
Posts: 1
Re: vista 64 raid question
«
Reply #10 on:
May 25, 2009, 04:47:25 am »
i just want to share my ideas to this JkDefrag .,
JkDefrag is a free open source disk defragmenting utility for Windows. It is the first free software defragmenting project of its kind.This also a computer program.,
«
Last Edit: May 26, 2009, 10:42:52 am by jeroen
»
Logged
jeroen
Administrator
JkDefrag Hero
Posts: 7155
Re: vista 64 raid question
«
Reply #11 on:
May 26, 2009, 10:46:06 am »
Quote from: Light768 on May 25, 2009, 04:47:25 am
i just want to share my ideas to this JkDefrag .,
Feel free to do so! I have stopped development on JkDefrag and am busy with it's successor, called "MyDefrag" (see
http://www.mydefrag.com
). MyDefrag is not open source, but has a very flexible scripting language so it's much easier to customize.
Logged
Pages: [
1
]
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
MyDefrag v4 Forum
-----------------------------
=> Announcements
=> Questions and help
=> Bugs and problems
=> Requests for new features
=> Scripts, and other contributions
-----------------------------
JkDefrag v3 Forum
-----------------------------
=> Announcements
=> Questions and help
=> Bugs and problems
=> Requests for new features
=> Programming with the library
Loading...