We just upgraded our server with 8 brand new seagate cheetah 15k.5's, a battery backup unit, and a 256mb dimm for the raid controller. In the boot process, i noticed an error about caching or something.
After analyzing the dmesg log, i found the error:
sda: asking for cache data failed
sda: assuming drive cache: write through
It seems like the kernel can't get to the raid controllers cache, so it switches to the write through setting.
I've benchmarked the harddisks with the write through, and write back setting. The odd thing is that both settings deliver the same performance.
Normally, write back increases the performance with like 100%... That's why we bought the battery backup unit.
So something is going wrong, but where lays the problem?
Server:
Quote:
8 X seagate cheetah 15k.5, U320, 16mb cache, SCA, 73GB
1 X chenbro backplane, U320, SCA, 2 channels, 8 ports
1 X LSI megaraid 320-2x raid controller, U320, 2 channels, battery pack and 256 upgraded dimm
6 GB DDR PC3200, ECC, CL3
2 X AMD opteron dual cores (4 X 2.0 ghz)
I have 100+ sites on this hard drive, and one site in particular that meant the world to me.
My host sent the drive to Gillware first, but they failed saying that the file system was so severely damaged that they could not recover anything.
Then shortly after, my host sent it to DriveSavers, a very well-known company, but they also FAILED.
I'm extremely depressed because of this. Please don't post if you're going to say "make sure you do backups next time" because I've heard it 504329504395 times now, and while I do realize my mistake, saying that does NOT help me.
I am willing to spend ALOT to get my sites back. I still have hope. Are there any other companies out there BETTER than DriveSavers? Assuming that you'd still have hope even after two companies failed, where you would you go or what would you do?
My host just recently sent the hard drive with my sites to a data recovery company called Gillware. Website is [url]- but they failed and gave the following reason:
Quote:
Originally Posted by Gillware
Unfortunately, your file system was so severely damaged that no data can be recovered. We will make arrangements to return your drive via UPS. Sorry we could not help you further.
Gillware Inc.
Do you guys think there's still hope?
The hard drive is now being shipped to a more well known company, Drive Savers - [url]and I'm guessing that this is the last hope, because the more the drive gets tampered with, the more chance of permanent data loss.
So yeah.. I was just wondering what you think? If the file system is so severely damaged, do you think it STILL can be recovered?
I use apache with CentOS VPS hosting for my blog. I only host one blog in this VPS account. I have 1.5GB RAM and I have 7, 500 page preview per day. My page loading time is 2-3 seconds (according to the pingdom tool).
I want to know what is the best performance (faster web page loading) W3 Total cache option for VPS hosting blog. Currently I use Disk to enhance for page cache and database cache for disk.
when am sending emails its cannot be delevired .. and its show me this error
"There was an error sending your message: Failed to send data [SMTP: Invalid response code received from server (code: 451, response: Temporary local problem - please try later)]"
i think its from the CFS i installed it
when i go to Cpanel my site the email " manager / creat " there is a red line content
Fatal! Write Failure: /etc/valiases/box.site.com . Ignore any messages of success this can only result in failure!
I am putting this thread to take other people advise and to advise them about my bad experience with rsync. Lucky, I was able to get my data back through the old drive
Three times a day, I take mysqldump and then rsync that mysql dump to a drive located in a different state.
Everything was working fine..The rsync was transferring data daily and updating the backup on other server. Few days ago, there was a hard drive failure on my server and then i checked in my backup drive for mysql dump...It was 764 bytes instead of 5 Gb...
Then i went to my other server where I rsync, to my surprise that was also 764 bytes from 5 Gb as it synced the both database..
My backup strategy failed and would be in tears if I couldn't grap data from failed drive
I would like to hear everyone views on this and learn from it
I've already changed a lot of MX records but never run into a problem like this one ...
I google it and found out that this might be cPanel/WHM bug. I've mailed them but they need a lot of time before they reply so I will also ask here
Here is error log from WHM:
Setting mx priority 10 (mx1.domain.com)........failed: Error fetching zone data for otherdomain.com.db's MX ...Done Setting mx priority 20 (mx2.domain.com)........failed: Error fetching zone data for otherdomain.com.db's MX ...Done
I just discovered there is seperate error log for php-fpm and since only 1 site is running fully nginx, the log is full with this error:
"NOTICE: PHP message: PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) in Unknown on line 0"
Two servers running Windows Server 2008 R2 and Plesk 11.5.30 MU #33 are running into the same problem with my daily FTP backup.
Problem is, the backup is fine as such, but the upload fails with the following error message:
Cannot export dump file 'backup_info_1402241551.xml' to 'ftp://xxx@xxx.net//' [Transport error: unable to send directory to repository: Transport error: unable to put local file C:Program Files (x86)ParallelsPleskPrivateTemp/repo_transport_tmp_01cf317215755ec0ackup_1402241551.zip4 to backup_1402241551.zip4: Curl error: Failed sending data to the peer]Click to expand...
I guess I have finally seen the adverse effects of raising the conntrack table max too high.
May 15 09:13:52 cp4 kernel: [6430723.486626] dst cache overflow May 15 09:13:52 cp4 kernel: [6430723.622616] dst cache overflow May 15 09:13:56 cp4 kernel: [6430727.562862] dst cache overflow May 15 09:13:56 cp4 kernel: [6430727.698868] dst cache overflow May 15 09:13:56 cp4 kernel: [6430727.844221] dst cache overflow May 15 09:13:56 cp4 kernel: [6430727.991276] dst cache overflow May 15 09:13:56 cp4 kernel: [6430728.131962] dst cache overflow
I got tons of these during an attack today. I have googled around for a lil while and not have been able to find any useful info on raising this cache level up. Would anyone here know how to do this?
I see no sysctl settings or anything of that nature for it.
I'm running shared hosting and would like to keep the amount kept in cache down so that there is always more memory free... how would i go about doing that?
