LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Hard disk failing?? (https://www.linuxquestions.org/questions/linux-hardware-18/hard-disk-failing-4175454509/)

alaios 03-18-2013 06:29 AM

Hard disk failing??
 
Dear all,
in the last days I am having a problem with my hard disk. I guess this only windows (ntfs specific) as my linux works just great.

In the last days the windows have a lot of problems reading from the hard disks and when booting up windows are calling for scandisks. Indeed problems are found and fixed. As I was concerned regarding the files there, I have already finished the backups.

I would like to ask your help for some decent tool that can examine the hard disk and see what is going on in the low level (bad sectors?). This program should support ntfs partitions and being able to not mess up with my ext4-linux partitions.

I would like to thank you in advance for your help


Regards
Alex

#root 03-18-2013 07:43 AM

you must be using Segate hard drive

alaios 03-18-2013 07:51 AM

Thanks. my Yast reports it as
WD3200 so I guess it is a Western Digital

#root 03-18-2013 07:59 AM

hmm LOL ok but the above mentioned problem is common with segate

any ways.......you may try EaseUs

nagabhushan 03-18-2013 08:14 AM

use "fsck" command

H_TeXMeX_H 03-18-2013 08:20 AM

You should run a SMART long test on the drive, it also checks for bad blocks.

You can do this with 'smartctl -t long /dev/sda' or you can use one of the manufacturer's tools most of which are on the ubcd:
http://www.ultimatebootcd.com/

allend 03-18-2013 09:02 AM

Personally, I would just accept that the drive needs to be replaced. Minimise use and get a replacement. Stressing the drive with a disk test is unlikely to help.

alaios 03-18-2013 05:26 PM

Quote:

Originally Posted by allend (Post 4913869)
Personally, I would just accept that the drive needs to be replaced. Minimise use and get a replacement. Stressing the drive with a disk test is unlikely to help.

How can you be sure for that and how can you explain that the problem looks to be hitting only the ntfs partition?

allend 03-18-2013 05:51 PM

In my experience, Windows has sophisticated algorithms for maintaining the NTFS file system. If you are starting to see errors that Windows needs to recover from, then it suggests that deterioration of areas of the disk is occurring. That it is only happening on your NTFS partition may be due to the quality of the disk surface in that area, or perhaps a developing fault in the electronics that drive the head to that area of the disk.

alaios 03-18-2013 06:16 PM

Can it be also something else? This hard disk is in a three years old laptop and I wonder if I should replace the hard disk or sell it as second-hand in ebay and buy a new one?

What hard disk alternatives can a three years old laptop support. Can it support any 1TB hard disk like
http://www.amazon.de/Western-Digital...637838&sr=1-13


Smart output also given here
http://imageshack.us/photo/my-images/442/smarts.png/

allend 03-18-2013 07:26 PM

Your SMART output shows that the reallocated sector count has exceeded the threshold as well as a high multizone error count, consistent with the problem you are reporting.

rknichols 03-18-2013 10:14 PM

Quote:

Originally Posted by allend (Post 4914158)
Your SMART output shows that the reallocated sector count has exceeded the threshold as well as a high multizone error count, consistent with the problem you are reporting.

A problem is indicated when the current value is below the threshold. High numbers in the "Value" column are good.

allend 03-19-2013 12:12 AM

From http://en.wikipedia.org/wiki/S.M.A.R.T.
Quote:

Reallocated Sectors Count
The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future.[
and
Quote:

Multi-Zone Error Rate
The count of errors found when writing a sector. The higher the value, the worse the disk's mechanical condition is.

alaios 03-19-2013 02:13 AM

I am confused is my hard disk at bad state or not??

alaios 03-19-2013 02:19 AM

This comes from linux smart
Quote:

smartctl -a /dev/sda
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.1.10-1.16-default] (SUSE RPM)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Scorpio Blue Serial ATA
Device Model: WDC WD3200BEVT-22ZCT0
Serial Number: WD-WXF0A99P7681
LU WWN Device Id: 5 0014ee 20375eb73
Firmware Version: 11.01A11
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.5, 3.0 Gb/s
Local Time is: Tue Mar 19 08:17:11 2013 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 9960) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 118) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 198 198 051 Pre-fail Always - 23359
3 Spin_Up_Time 0x0027 184 183 021 Pre-fail Always - 1758
4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 4244
5 Reallocated_Sector_Ct 0x0033 186 186 140 Pre-fail Always - 111
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 7379
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3402
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 75
193 Load_Cycle_Count 0x0032 124 124 000 Old_age Always - 228553
194 Temperature_Celsius 0x0022 114 074 000 Old_age Always - 33
196 Reallocated_Event_Count 0x0032 184 184 000 Old_age Always - 16
197 Current_Pending_Sector 0x0032 198 198 000 Old_age Always - 112
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0009 100 253 051 Pre-fail Offline - 0

SMART Error Log Version: 1
ATA Error Count: 22858 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 22858 occurred at disk power-on lifetime: 7374 hours (307 days + 6 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 2c 7f e4 40 Error: WP at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 10 e8 29 7c 01 00 03:46:29.525 WRITE FPDMA QUEUED
61 08 08 98 28 7a 01 00 03:46:29.524 WRITE FPDMA QUEUED
61 08 f0 68 3f 53 06 00 03:46:29.524 WRITE FPDMA QUEUED
61 08 c8 a8 b4 81 01 00 03:46:29.524 WRITE FPDMA QUEUED
61 08 b0 b8 29 7c 01 00 03:46:29.524 WRITE FPDMA QUEUED

Error 22857 occurred at disk power-on lifetime: 7374 hours (307 days + 6 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 2c 7f e4 40 Error: UNC at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 28 80 08 7f e4 24 00 03:46:25.969 READ FPDMA QUEUED
60 40 78 ba 80 91 12 00 03:46:25.969 READ FPDMA QUEUED
60 80 70 60 68 25 0e 00 03:46:25.969 READ FPDMA QUEUED
61 03 68 60 36 a3 09 00 03:46:25.969 WRITE FPDMA QUEUED
60 40 60 10 cb e8 01 00 03:46:25.969 READ FPDMA QUEUED

Error 22856 occurred at disk power-on lifetime: 7374 hours (307 days + 6 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 2c 7f e4 40 Error: WP at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 18 a0 28 7a 01 00 03:46:22.588 WRITE FPDMA QUEUED
61 08 10 b0 32 7b 01 00 03:46:22.588 WRITE FPDMA QUEUED
61 08 08 90 28 7a 01 00 03:46:22.587 WRITE FPDMA QUEUED
61 08 00 98 28 7a 01 00 03:46:22.587 WRITE FPDMA QUEUED
61 01 f8 c8 d8 ff 02 00 03:46:22.586 WRITE FPDMA QUEUED

Error 22855 occurred at disk power-on lifetime: 7374 hours (307 days + 6 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 2c 7f e4 40 Error: UNC at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 28 80 08 7f e4 24 00 03:46:19.106 READ FPDMA QUEUED
60 38 78 3a 80 91 12 00 03:46:19.105 READ FPDMA QUEUED
60 80 70 10 67 25 0e 00 03:46:19.105 READ FPDMA QUEUED
60 20 68 40 36 dd 01 00 03:46:19.105 READ FPDMA QUEUED
60 38 60 62 e0 86 01 00 03:46:19.105 READ FPDMA QUEUED

Error 22854 occurred at disk power-on lifetime: 7374 hours (307 days + 6 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 2c 7f e4 40 Error: UNC at LBA = 0x00e47f2c = 14974764

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 40 0e 07 a7 01 00 03:46:15.868 READ FPDMA QUEUED
61 08 38 a0 28 7a 01 00 03:46:15.868 WRITE FPDMA QUEUED
60 1b 30 16 07 a7 01 00 03:46:15.868 READ FPDMA QUEUED
61 08 28 98 32 7b 01 00 03:46:15.867 WRITE FPDMA QUEUED
60 28 20 08 7f e4 24 00 03:46:15.867 READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 60% 7378 31108065

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


allend 03-19-2013 02:43 AM

Yes - the disk is bad. If you do not have backups already, consider ddrescue ASAP.

alaios 03-19-2013 07:11 AM

Can it be some other problem or should I just replace the hard disk or it might be also the motherboard or something else?

H_TeXMeX_H 03-19-2013 08:10 AM

The HDD is definitely failing because of the short test and there is no reason to suspect any other component at this time.

alaios 03-19-2013 10:04 AM

Are there any limitations on what hard disk I can install on a laptop?
Actually I am thinking between those two


http://www.amazon.de/Western-Digital...3705159&sr=1-3

http://www.amazon.de/Seagate-Momentu...3705162&sr=1-1

have a look at the thumbnails where the achieved speeds are written.
What is the process now I should follow to copy the current partitions to the new external disk, before I replace it to the laptop? I have already these atapi/sata to usb cables.


after edit: The model I already have
http://www.ebay.com/itm/WESTERN-DIGI...-/190577925523

rknichols 03-19-2013 11:17 AM

Quote:

Originally Posted by allend (Post 4914247)
From http://en.wikipedia.org/wiki/S.M.A.R.T.

Quote:
Reallocated Sectors Count
The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future.[
and
Quote:
Multi-Zone Error Rate
The count of errors found when writing a sector. The higher the value, the worse the disk's mechanical condition is.
and

Those comments are referring to the raw values, which were not shown in the screen capture. Applying that interpretation to the normalized values is dead wrong. For the normalized values, which are what is shown in the "Value" column, high numbers are good and values below the threshold indicate failure.

From the data shown, the disk does not appear to be in perfect health, but without the raw values it's hard to make a judgement. (I really hate fancy tools that suppress important information.)

[Edit]: I just saw the followup post that does show the raw values. 111 reallocated sectors and 112 more sectors pending reallocation and currently visibly bad to the OS. Yes, it's bad.

H_TeXMeX_H 03-19-2013 11:31 AM

I would get the seagate drive, but it's a matter of personal choice. I don't like WD drives.

alaios 03-19-2013 12:08 PM

Can it be that my laptop does not support the new one_ Please have a look above on the model I gave so to suggest me what to do.

regards
Alex

H_TeXMeX_H 03-19-2013 12:35 PM

It looks like this is your current HDD:
http://www.newegg.com/Product/Produc...82E16822136197
So my recommendation is:
http://www.newegg.com/Product/Produc...82E16822148599
Any 2.5 inch HDD with SATA 3.0Gb/s (revision 2.0) should work.

However, I do NOT guarantee that it will work. You never know with an old laptop. I replaced the IDE drive on my old laptop and it didn't recognize it, probably because of a BIOS issue.

alaios 03-20-2013 03:55 AM

I bought the disk. What is the procedure now to clone the old partition to the new one? As my linux is still running I was thinking to connect the new hard disk with atapi to usb cables to complete the clone first. I am more intrested in cloning that hidden laptop partition that is used to recover the official windows 7. Is there something special with that partition for cloning it?

Alex

H_TeXMeX_H 03-20-2013 04:22 AM

I recommend using:
http://clonezilla.sourceforge.net/
It can do a lot and is easier and safer to use than 'dd'.

alaios 03-20-2013 06:46 AM

Quote:

Originally Posted by H_TeXMeX_H (Post 4915026)
I recommend using:
http://clonezilla.sourceforge.net/
It can do a lot and is easier and safer to use than 'dd'.

Thanks for the suggestion, is there any recommendations for copying the hidden partition (i.e like flags that I need to set)?

rknichols 03-20-2013 09:38 AM

If you use clonezilla to read your disk with bad sectors, you will probably need to select "Expert" mode and use the "-rescue" option. Otherwise it will stop on the first failed read. The "-rescue" option in clonezilla is not as good as the error handling in ddrescue or gddrescue, so you might have to use one of those tools to copy partitions containing bad sectors.

The clonezilla live CD contains both those tools.

alaios 03-20-2013 12:52 PM

Quote:

Originally Posted by rknichols (Post 4915233)
If you use clonezilla to read your disk with bad sectors, you will probably need to select "Expert" mode and use the "-rescue" option. Otherwise it will stop on the first failed read. The "-rescue" option in clonezilla is not as good as the error handling in ddrescue or gddrescue, so you might have to use one of those tools to copy partitions containing bad sectors.

The clonezilla live CD contains both those tools.

Hi, how I can later to extend the partitions? The new hard disk would be larger than the one I currently have
Alex

rknichols 03-20-2013 02:17 PM

Quote:

Originally Posted by alaios (Post 4915357)
Hi, how I can later to extend the partitions? The new hard disk would be larger than the one I currently have
Alex

For the Linux ext2/3/4 partitions, it's easy. Make the new partitions the size you want, use clonezilla or whatever tool to copy the old filesystem into the new, larger partition. Then run resize2fs on the new partition, and it will automatically extend the filesystem to fill the partition.

For Windows, the NTFS resizing tools I've found do not seem to understand the notion of extending the filesystem unless they are also changing the partition size at the same time. So, you would need to make the new partition slightly smaller than intended, copy the filesystem over, and then use gparted, ntfsresize, or one of the available Windows tools to adjust the partition size and make the filesystem fit. (Perhaps you don't intend to change the size of your NTFS partition. That would be the easiest.)

For a swap partition, there is of course no reason to copy the old partition. Just run mkswap on the new partition.

alaios 03-21-2013 03:23 AM

Quote:

Originally Posted by rknichols (Post 4915404)
For the Linux ext2/3/4 partitions, it's easy. Make the new partitions the size you want, use clonezilla or whatever tool to copy the old filesystem into the new, larger partition. Then run resize2fs on the new partition, and it will automatically extend the filesystem to fill the partition.

For Windows, the NTFS resizing tools I've found do not seem to understand the notion of extending the filesystem unless they are also changing the partition size at the same time. So, you would need to make the new partition slightly smaller than intended, copy the filesystem over, and then use gparted, ntfsresize, or one of the available Windows tools to adjust the partition size and make the filesystem fit. (Perhaps you don't intend to change the size of your NTFS partition. That would be the easiest.)

For a swap partition, there is of course no reason to copy the old partition. Just run mkswap on the new partition.

I can not copy the windows partitions through clonezilla software?

rknichols 03-21-2013 08:33 AM

Quote:

Originally Posted by alaios (Post 4915780)
I can not copy the windows partitions through clonezilla software?

Yes, you can. The issue is that if you copy, for example, a 5GB filesystem into a 10GB partition, there is no tool that I have found that you can tell, "Expand this filesystem to fill the existing 10GB partition.) You would need to do something like, "Shrink the partition to 9.9GB, then expand the partition back to 10GB, adjusting the filesystem size each time." Personally, I try to avoid doing things that way. YMMV.

For ext2/3/4, using resize2fs to expand a filesystem to fill an existing partition is the default mode of operation.

clonezilla never changes the size of a filesystem. It will leave you with a small filesystem (same size as the original) sitting in your large partition.

alaios 03-23-2013 12:14 AM

Total Failure:
I have been launching clonezilla (which I found a terribly designed gui) and went to konsole

I entered root mode through sudo su -

and then I did e2fsck -fp /dev/sdb1

then I did

ddrescue -v /dev/sda /dev/sdb

that returned an error that /dev/sdb has data that would be lost and I have to use --force.
So I used
ddrescue -v --force /dev/sda /dev/sdb

when I returned back. The /dev/sdb had only three partitions out of 8.

I have read also those two tutorials here
http://www.ghacks.net/2010/08/01/clo...with-ddrescue/
http://dimitar.me/clone-disk-drives-with-ubuntu/

but I can not see why it failed so much.

Any help now?
Alex[COLOR="Silver"]

alaios 03-23-2013 02:57 AM

Hi, I would be happy if just the 320gb hard disk (source) is written as it in the 750gb (target) and leave the rest space unallocated, I will try to expand it later with other tools.

I tried yesterday launching with clonezilla (what a bad interface is that!!) and launched the terminal. What a total failure was that.


I entered root mode through sudo su -

and then I did e2fsck -fp /dev/sdb1

then I did

ddrescue -v /dev/sda /dev/sdb

that returned an error that /dev/sdb has data that would be lost and I have to use --force.
So I used
ddrescue -v --force /dev/sda /dev/sdb

when I returned back. The /dev/sdb had only three partitions out of 8.

I have read also those two tutorials here
http://www.ghacks.net/2010/08/01/clo...with-ddrescue/
Clone Disk Drives with Ubuntu using dd or ddrescue | dimitar.me

but I can not see why it failed so much.

Any help now?

my source disk now looks like:


Quote:

fdisk -l /dev/sda

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x7de47de4

Device Boot Start End Blocks Id System
/dev/sda1 2048 24578047 12288000 27 Hidden NTFS WinRE
/dev/sda2 * 24578048 24782847 102400 7 HPFS/NTFS/exFAT
/dev/sda3 24782848 351562415 163389784 7 HPFS/NTFS/exFAT
/dev/sda4 351563776 625139711 136787968 f W95 Ext'd (LBA)
/dev/sda5 351565824 392525823 20480000 83 Linux
/dev/sda6 420814848 625139711 102162432 7 HPFS/NTFS/exFAT
/dev/sda7 392527872 396623871 2048000 82 Linux swap / Solaris
/dev/sda8 396625920 420812799 12093440 83 Linux

and the target disk is the:
Quote:

fdisk -l /dev/sdc
Note: sector size is 4096 (not 512)

Disk /dev/sdc: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 11400 cylinders, total 183143646 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000395d3

Device Boot Start End Blocks Id System

H_TeXMeX_H 03-23-2013 03:18 AM

So, are you trying to clone the disk from /dev/sda to /dev/sdb or to /dev/sdc ?

alaios 03-23-2013 03:30 AM

From sda to sdb. After I tried with ddrescue that failed (as I described) the hard disk on the currently installed linux system (sda) was recognized as sdc (that is the reason I had to to fdisk -l /dev/sdc)

H_TeXMeX_H 03-23-2013 04:24 AM

Can you run fdisk on /dev/sdb.

alaios 03-23-2013 05:56 AM

No, because there isīno such disk in the system

I was also concerded why the kernel gave the disk the name sdc and not sdb.... When I also launch Yast-> Partitioner, there is no there sdb, only sda and sdc.

IF you want I can reboot but I think the main concern is how I make ddrescue clone partition by partition... and why it failed producing 3 non-sense partitions.

regards
Alex

H_TeXMeX_H 03-23-2013 06:08 AM

That is unusual. You probably should reboot and try again. Make sure that both disks are recognized before trying to clone the disk.

alaios 03-23-2013 06:25 AM

Quote:

Originally Posted by H_TeXMeX_H (Post 4917027)
That is unusual. You probably should reboot and try again. Make sure that both disks are recognized before trying to clone the disk.

Which command do you suggest me to run after both disks are recognized correctly as sda and sdb?

Alex

H_TeXMeX_H 03-23-2013 09:04 AM

Do take into account that SMART reported read failure meaning that cloning the partitions may not work no matter what tool you use. In other words, the disk is corrupt and trying to clone corrupt partitions will likely lead to corrupt partitions or it just won't work.

I recommend trying to backup your files and then just reinstall everything onto the new disk.

It may have been my mistake to assume that you were doing this to try to salvage your data. It is true that cloning the drive is a good thing to do, but you shouldn't expect the drive you clone to to be bootable and usable. Instead you should recover your files from there and then reinstall everything onto this new drive.

alaios 03-23-2013 09:53 AM

Quote:

Originally Posted by H_TeXMeX_H (Post 4917109)
Do take into account that SMART reported read failure meaning that cloning the partitions may not work no matter what tool you use. In other words, the disk is corrupt and trying to clone corrupt partitions will likely lead to corrupt partitions or it just won't work.

I recommend trying to backup your files and then just reinstall everything onto the new disk.

It may have been my mistake to assume that you were doing this to try to salvage your data. It is true that cloning the drive is a good thing to do, but you shouldn't expect the drive you clone to to be bootable and usable. Instead you should recover your files from there and then reinstall everything onto this new drive.

Indeed that might be true. I would try again with dd_rhelp and see if there is anything coming out, if not I would say that the minimum is to copy just the hidden partition where the windows 7 installation resides (my opensuse is already downloaded and my data are backed up). Do you have any tips on how to copy the first hidden partition? Is there something important about a hidden partition or is just a normal one? Alex

rknichols 03-23-2013 10:14 AM

The output from "fdisk -l" makes it appear that the new drive has a 4096-byte logical sector size. What is the make and model for that drive, and what is the output from "hdparm -I /dev/sdc | grep 'Sector size'". Drives with a 4096 logical sector size are only supported by recent kernels and tools, and even then are very bleeding edge. It well could be that clonezilla does not support them. (Drives with 4096 physical / 512 logical are not a problem except for alignment issues).

The drive probably migrated from sdb to sdc because you unplugged it (as sdb) while there was still some open reference to it. That leaves sdb in use, and when you reconnect the drive you get the next available device number.

alaios 03-23-2013 01:32 PM

Quote:

Originally Posted by rknichols (Post 4917156)
The output from "fdisk -l" makes it appear that the new drive has a 4096-byte logical sector size. What is the make and model for that drive, and what is the output from "hdparm -I /dev/sdc | grep 'Sector size'". Drives with a 4096 logical sector size are only supported by recent kernels and tools, and even then are very bleeding edge. It well could be that clonezilla does not support them. (Drives with 4096 physical / 512 logical are not a problem except for alignment issues).

The drive probably migrated from sdb to sdc because you unplugged it (as sdb) while there was still some open reference to it. That leaves sdb in use, and when you reconnect the drive you get the next available device number.

This is a normal 2.5 inches western digital 750gigabytes hard disk! If I did something wronng that should be easily fixable with some command line commands.
1. Which one should I try?

The target is just to clone only the first hidden windows partition to the hard disk and just restore windows from scratch. Installing linux then would be quite straightforward.


2. What is the ddrescue command for cloning the first partition of sda1 to sdb1?

3. Should I have in advance created an almost similar partition size to the target disk? If yes how I can do that with commands like fsck?

Regards
Alex

rknichols 03-23-2013 06:54 PM

What exact model number, please.

alaios 03-24-2013 03:22 AM

Western Digital WD7500BPKT Black 750GB . Where I can find the model number?

rknichols 03-24-2013 11:14 AM

"WD7500BPKT" is it. According to the Spec. sheet, that drive has 512-byte logical sectors ("User sectors per drive 1,465,149,168"), so I don't understand the "Note: sector size is 4096 (not 512)" output from fdisk. What does
Code:

hdparm -I /dev/sdc | grep 'Sector size'
report about the physical and logical sector sizes?

From what I've seen browsing the clonezilla forums, I'm not optimistic about it's ability to work with 4096-byte logical sectors, though no one has yet responded to my specific query. That's why I'd like to be sure that's not what you're dealing with.

alaios 03-25-2013 04:40 AM

Well it might went something wrong with clonezilla rescue operations. How I can "reset" the hard disk to the factory defaults before starting any rescue operations?

Regard
Aex

rknichols 03-25-2013 09:10 AM

It should be sufficient just to zero out the partition table.
Code:

dd if=/dev/zero of=/dev/sdc count=1
If your drive is not currently being seen as "sdc", of course, change that as needed. Do be sure to get it right. You really don't want to be wiping out the MBR of the wrong disk just now.


All times are GMT -5. The time now is 05:22 AM.