Re: Restoring failed due to Unexpected Error

2011-11-22 Thread Reindl Harald
yes - take your fingers away and go to a datarecovery company
if it is not too late because you are damaging the disk more
and more, NOW it is too late for backups!

Am 22.11.2011 06:03, schrieb Adarsh Sharma:
 Any comments to get the data back know.
 My hard disk crashes about 90% but when I start any kind of backup or select 
 output into a file from 40GB table ,
 it stops after 30 GB  then stalled because there are bad sectors to read.
 
 Is it possible to get the remaining data ( 10GB) , as all backups are also 
 corrupted resulting in errors.
 
 Hard disk heats up after 30 Gb backup , but if no backup is taken it is 
 working fine.
 
 
 Thanks
 
 
 Reindl Harald wrote:
 Am 18.11.2011 14:18, schrieb Johan De Meersman:
   
 - Original Message -
 
 From: Reindl Harald h.rei...@thelounge.net

 but anyways, the message sounds like a damaged compressed file
   
 Looks more like he's got an HTML file instead of an SQL file, to me.

 Have a look inside the file, maybe the HTML is just a wrapper or something.
 How was the backup taken ?
 

 yes the tml is strange but gunzip: stdin: unexpected end of file sounds
 like the bigger problem to me, backups without verify integrity are
 a dangerous game because you need them not often but if you need them
 it is fatal if they are corrupt

   
 

-- 

Mit besten Grüßen, Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/

http://www.thelounge.net/signature.asc.what.htm



signature.asc
Description: OpenPGP digital signature


Re: Restoring failed due to Unexpected Error

2011-11-21 Thread Adarsh Sharma

Any comments to get the data back know.
My hard disk crashes about 90% but when I start any kind of backup or 
select output into a file from 40GB table , it stops after 30 GB  then 
stalled because there are bad sectors to read.


Is it possible to get the remaining data ( 10GB) , as all backups are 
also corrupted resulting in errors.


Hard disk heats up after 30 Gb backup , but if no backup is taken it is 
working fine.



Thanks


Reindl Harald wrote:

Am 18.11.2011 14:18, schrieb Johan De Meersman:
  

- Original Message -


From: Reindl Harald h.rei...@thelounge.net

but anyways, the message sounds like a damaged compressed file
  

Looks more like he's got an HTML file instead of an SQL file, to me.

Have a look inside the file, maybe the HTML is just a wrapper or something.
How was the backup taken ?



yes the tml is strange but gunzip: stdin: unexpected end of file sounds
like the bigger problem to me, backups without verify integrity are
a dangerous game because you need them not often but if you need them
it is fatal if they are corrupt

  




Restoring failed due to Unexpected Error

2011-11-18 Thread Adarsh Sharma

Dear all,

Today i need to restore the backup of a 40GB table in a new system.
I create a script that takes the backup in compressed format ( 2.3 GB 
).The existing hard disk crashes  I need to restore my data.


But when I restore the data below error exists :-

[root@test1 hdd2-1]# gunzip  source.sql.gz | mysql test

gunzip: stdin: unexpected end of file
ERROR 1064 (42000) at line 30309: You have an error in your SQL syntax; 
check the manual that corresponds to your MySQL server version for the 
right syntax to use near ''!DOCTYPE html PUBLIC \-//W3C//DTD XHTML 1.0 
Transitional//EN\\n\http://www.' at line 1

[root@test1 hdd2-1]#


Any suggestion to solve this issue.



Thanks



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org



Re: Restoring failed due to Unexpected Error

2011-11-18 Thread Reindl Harald


Am 18.11.2011 12:41, schrieb Adarsh Sharma:
 But when I restore the data below error exists :-
 
 [root@test1 hdd2-1]# gunzip  source.sql.gz | mysql test
 
 gunzip: stdin: unexpected end of file
 ERROR 1064 (42000) at line 30309: You have an error in your SQL syntax; check 
 the manual that corresponds to your
 MySQL server version for the right syntax to use near ''!DOCTYPE html PUBLIC 
 \-//W3C//DTD XHTML 1.0
 Transitional//EN\\n\http://www.' at line 1
 [root@test1 hdd2-1]#

sounds bad

have you tried to unpck the backup manually and considered to use mysqlimport
but anyways, the message sounds like a damaged compressed file



signature.asc
Description: OpenPGP digital signature


Re: Restoring failed due to Unexpected Error

2011-11-18 Thread Johan De Meersman
- Original Message -
 From: Reindl Harald h.rei...@thelounge.net
 
 but anyways, the message sounds like a damaged compressed file

Looks more like he's got an HTML file instead of an SQL file, to me.

Have a look inside the file, maybe the HTML is just a wrapper or something.

How was the backup taken ?

-- 
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org



Re: Restoring failed due to Unexpected Error

2011-11-18 Thread Reindl Harald


Am 18.11.2011 14:18, schrieb Johan De Meersman:
 - Original Message -
 From: Reindl Harald h.rei...@thelounge.net

 but anyways, the message sounds like a damaged compressed file
 
 Looks more like he's got an HTML file instead of an SQL file, to me.
 
 Have a look inside the file, maybe the HTML is just a wrapper or something.
 How was the backup taken ?

yes the tml is strange but gunzip: stdin: unexpected end of file sounds
like the bigger problem to me, backups without verify integrity are
a dangerous game because you need them not often but if you need them
it is fatal if they are corrupt



signature.asc
Description: OpenPGP digital signature