Formatting Corrupted WD HDD

> Ubuntu can fix just about any problem with an NTFS file system.  

Ubuntu cannot fix hard crash problem. If the OP's drive had a head crash into the platter as I suspected, he should not use it for storing important data.  The head could have damaged, or bit of particles from the platter still flying around.

The controller might be worth saving for repairing another drive.  Is it 2.5" or 3.5"? What model?

On 8/19/2014 11:22 PM, edward.ming.lee@gmail.com wrote:
>
>> Ubuntu can fix just about any problem with an NTFS file system.
>
> Ubuntu cannot fix hard crash problem. If the OP's drive had a head
> crash into the platter as I suspected, he should not use it for
> storing important data.  The head could have damaged, or bit of
> particles from the platter still flying around.

There is no conclusive evidence that this has, in fact, happened.
Modern drives are pretty smart when it comes to parking heads,
allocating replacement sectors, etc.

Verify that the drive *appears* to work -- assuming NOTHING about
its contents -- before deciding that it is trash.

> The controller might be worth saving for repairing another drive.  Is
> it 2.5" or 3.5"? What model?

On a sunny day (Wed, 20 Aug 2014 12:49:09 +1000) it happened David King
<dking@interphase.com> wrote in <8928v9taeh2it0i7j9bhocfiim306hek7r@4ax.com>:

>
>Please excuse me for restarting this thread, but the other was quite
>long and there has been a slight delay from my side due to personal
>circumstances.
>
>I have done as Jan suggested, which is to connect the HDD to my Linux
>machine and enter DMESG. This is what shows:
>
>
>[   66.672060] usb 1-1: new high-speed USB device number 2 using
>ehci-pci
>[   67.100075] usb 1-1: new high-speed USB device number 3 using
>ehci-pci
>[   67.233229] usb 1-1: New USB device found, idVendor=1058,
>idProduct=07a8
>[   67.233233] usb 1-1: New USB device strings: Mfr=1, Product=2,
>SerialNumber=3
>[   67.233236] usb 1-1: Product: My Passport 07A8
>[   67.233239] usb 1-1: Manufacturer: Western Digital
>[   67.233241] usb 1-1: SerialNumber: 575845314134333137303433
>[   67.284711] usb-storage 1-1:1.0: USB Mass Storage device detected
>[   67.284800] scsi4 : usb-storage 1-1:1.0
>[   67.284878] usbcore: registered new interface driver usb-storage
>[   68.284758] scsi 4:0:0:0: Direct-Access     WD       My Passport
>07A8 1042 PQ: 0 ANSI: 6
>[   68.285250] scsi 4:0:0:1: Enclosure         WD       SES Device
>1042 PQ: 0 ANSI: 6
>[   68.285495] sd 4:0:0:0: Attached scsi generic sg2 type 0
>[   68.285643] scsi 4:0:0:1: Attached scsi generic sg3 type 13
>[   68.289487] sd 4:0:0:0: [sdc] Spinning up disk...
>[   69.292047] .ready
>[   69.311994] sd 4:0:0:0: [sdc] 1953458176 512-byte logical blocks:
>(1.00 TB/931 GiB)
>[   69.314000] sd 4:0:0:0: [sdc] Write Protect is off
>[   69.314004] sd 4:0:0:0: [sdc] Mode Sense: 53 00 10 08
>[   69.315366] sd 4:0:0:0: [sdc] No Caching mode page found
>[   69.315369] sd 4:0:0:0: [sdc] Assuming drive cache: write through
>[   69.320747] sd 4:0:0:0: [sdc] No Caching mode page found
>[   69.320750] sd 4:0:0:0: [sdc] Assuming drive cache: write through
>[   69.321144] ses 4:0:0:1: Attached Enclosure device
>[   69.332119]  sdc: sdc1
>[   69.335236] sd 4:0:0:0: [sdc] No Caching mode page found
>[   69.335240] sd 4:0:0:0: [sdc] Assuming drive cache: write through
>[   69.335243] sd 4:0:0:0: [sdc] Attached SCSI disk
>

So, the hardware is OK, drive IS recognized,
it is just some sectors messed up by Microsoft windows.


>Assuning the drive ID is 07A8, I then entered fdisk /dev/07a8 but it
>was not found.

Your drive is /dev/sdc

By the look of it windows (you mentioned it was an ext2 fielsystem),
modified that to one of its own....


***** If you do not care about the data [1], type: *****
fdisk /dev/sdc

To delete partition 1 type:
d

To make a new primary partition type:
n
1
accept defaults for start and end.

To set the partition ID type:
t
For linux: use ID 83.

To write the new configuration to disk type:
w

To make a filesystem ext2 on /dev/sdc1 type [2]:
mke2fs /dev/sdc1

Mount it:
mount /dev/sdc1 /mnt/sdc1

To see if you have the 1 GB space back type:
df

That should be it (you lost your data though).
           ***********

[1] There are tricks to try to recover or better make the MS windows 'modification' undone.
[2] You can make any other filesystem you like in Linux on /dev/sdc1

<disclaimer>
if you use fdisk to remove and make partitions MAKE SURE YOU USE THE RIGHT DISK,
typing dmesg just before you use fdisk helps to make sure.
This because you could have plugged in some USB stick or SDcard in the meantime,
and disk numbering would be different.
<YOU DIDIT>

> [   67.233236] usb 1-1: Product: My Passport 07A8
> [   67.233239] usb 1-1: Manufacturer: Western Digital
> [   67.233241] usb 1-1: SerialNumber: 575845314134333137303433
> [   67.284711] usb-storage 1-1:1.0: USB Mass Storage device detected
> [   67.284800] scsi4 : usb-storage 1-1:1.0
> [   67.284878] usbcore: registered new interface driver usb-storage
> [   68.284758] scsi 4:0:0:0: Direct-Access     WD       My Passport
> [   68.285250] scsi 4:0:0:1: Enclosure         WD       SES Device
> [   68.285495] sd 4:0:0:0: Attached scsi generic sg2 type 0
> [   68.285643] scsi 4:0:0:1: Attached scsi generic sg3 type 13
> [   68.289487] sd 4:0:0:0: [sdc] Spinning up disk...
> [   69.292047] .ready
> [   69.311994] sd 4:0:0:0: [sdc] 1953458176 512-byte logical blocks:
> [   69.314000] sd 4:0:0:0: [sdc] Write Protect is off
> [   69.314004] sd 4:0:0:0: [sdc] Mode Sense: 53 00 10 08
> [   69.315366] sd 4:0:0:0: [sdc] No Caching mode page found
> [   69.315369] sd 4:0:0:0: [sdc] Assuming drive cache: write through
> [   69.320747] sd 4:0:0:0: [sdc] No Caching mode page found
> [   69.320750] sd 4:0:0:0: [sdc] Assuming drive cache: write through
> [   69.321144] ses 4:0:0:1: Attached Enclosure device
> [   69.332119]  sdc: sdc1
> [   69.335236] sd 4:0:0:0: [sdc] No Caching mode page found
> [   69.335240] sd 4:0:0:0: [sdc] Assuming drive cache: write through
> [   69.335243] sd 4:0:0:0: [sdc] Attached SCSI disk
>
> Assuning the drive ID is 07A8, I then entered fdisk /dev/07a8 but it
> was not found.
>

the device is:  /dev/sdc
it has one partition:  /dev/sdc1

> The HDD shows in My Comp, but cannot be mounted of formatted. The
> following message appears:

> At this stage, I would be happy just to be able to format the drive
> back to NTSC.

do you mean NTFS ?

> Any advice on how to do so from here would be most appreciated.

dd if=/dev/zero of=/dev/sdc count=4000

then unplug it and reformat.

-- 
umop apisdn


--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

On Wed, 20 Aug 2014 01:31:03 -0400, Neon John <no@never.com> wrote:

>On Wed, 20 Aug 2014 13:49:00 +1000, David King <dking@interphase.com>
>wrote:
>
>
>>I would like to but Linux will not mount the HDD. 
>>
>>Is there a way to format or re-partition without mounting?
>
>Sure.  By definition, a drive has to be partitioned and have a file
>system on it before it can be mounted.  If you're on a character mode
>Linux installation, the command is parted which must be run as root.
>Not for the faint of heart.
>
>If you're using a GUI like Ubuntu, invoke Gparted from
>applications->system tools ->administration->Gparted.  It has a nice
>GUI that kinda holds your hand.  A little bit at least.  Just make
>sure you don't do anything to /dev/sda, your boot drive.
>
>But before you do anything else, read this page
>
>http://www.makeuseof.com/tag/fix-corrupted-windows-ntfs-filesystem-ubuntu/
>
>Ubuntu can fix just about any problem with an NTFS file system.  You
>can probably salvage your data by following instructions on that page.
>
>John
>
>
>
>John DeArmond
>http://www.neon-john.com
>http://www.fluxeon.com 
>Tellico Plains, Occupied TN
>See website for email address


Maybe hes not using Ubuntu.  NTFS is not nativaly supported under most
Linux flavors, as least in the past.

Cheers

On Wed, 20 Aug 2014 09:12:08 GMT, Jan Panteltje
<pNaonStpealmtje@yahoo.com> wrote:


>Your drive is /dev/sdc
>
>By the look of it windows (you mentioned it was an ext2 fielsystem),
>modified that to one of its own....
>
>
>***** If you do not care about the data [1], type: *****
>fdisk /dev/sdc
>
>To delete partition 1 type:
>d
>
>To make a new primary partition type:
>n
>1
>accept defaults for start and end.
>
>To set the partition ID type:
>t
>For linux: use ID 83.
>
>To write the new configuration to disk type:
>w
>
>To make a filesystem ext2 on /dev/sdc1 type [2]:
>mke2fs /dev/sdc1
>
>Mount it:
>mount /dev/sdc1 /mnt/sdc1
>
>To see if you have the 1 GB space back type:
>df
>
>That should be it (you lost your data though).
>


Thanks for your detailed reply. I will try this first thing tomorrow
since the PC is at another location.

I am now hopeful of at least getting my drive back. Next time I will
buy the one with the reset button ;-)

Davd King

On a sunny day (Fri, 22 Aug 2014 12:35:39 +1000) it happened David King
<dking@interphase.com> wrote in <fuadv9pq48rgppregcq7pt4id8t7bmtsdk@4ax.com>:

>On Wed, 20 Aug 2014 09:12:08 GMT, Jan Panteltje
><pNaonStpealmtje@yahoo.com> wrote:
>
>
>>Your drive is /dev/sdc
>>
>>By the look of it windows (you mentioned it was an ext2 fielsystem),
>>modified that to one of its own....
>>
>>
>>***** If you do not care about the data [1], type: *****
>>fdisk /dev/sdc
>>
>>To delete partition 1 type:
>>d
>>
>>To make a new primary partition type:
>>n
>>1
>>accept defaults for start and end.
>>
>>To set the partition ID type:
>>t
>>For linux: use ID 83.
>>
>>To write the new configuration to disk type:
>>w
>>
>>To make a filesystem ext2 on /dev/sdc1 type [2]:
>>mke2fs /dev/sdc1
>>
>>Mount it:
>>mount /dev/sdc1 /mnt/sdc1
>>
>>To see if you have the 1 GB space back type:
>>df
>>
>>That should be it (you lost your data though).
>>
>
>
>Thanks for your detailed reply. I will try this first thing tomorrow
>since the PC is at another location.
>
>I am now hopeful of at least getting my drive back. Next time I will
>buy the one with the reset button ;-)
>
>Davd King

It is OK to experiment with fdisk,
nothing will really happen until you type 'w'.
Control C or 'q' will quit anytime.
If you did not type 'w' then restarting fdisk will show the old configuration.
Read the help menu (type 'm') and experiment.
Once you are sure how it works and made a new primary partition,
then use 'w' to write it to disk.

If you have some old small size SDcard or USB stick you can practice on that too.
For example I have some 128 MB USB sticks, something really antique...
Great for tests.
Do not forget to check what disk it is with 'dmesg' EVERY TIME before starting fdisk.

> I am now hopeful of at least getting my drive back. Next time I will buy the one with the reset button ;-)

Not with reset, but with power down.  I have seen too many bad drives with corrupted FAT area (beginning of the disk).  Probably with people pulling the plug while updating the FAT.  You have to be very careful with any removable media.

On 8/22/2014 8:14 AM, edward.ming.lee@gmail.com wrote:
>
>> I am now hopeful of at least getting my drive back. Next time I
>> will buy the one with the reset button ;-)
>
> Not with reset, but with power down.  I have seen too many bad drives
> with corrupted FAT area (beginning of the disk).  Probably with
> people pulling the plug while updating the FAT.  You have to be very
> careful with any removable media.

A reset button on any device with complex firmware is probably a good
idea.  (this applies to the PC as well).  Apparently, there is a very
high percentage of disks that are claimed to be defective (even by their
own diagnostics) that, in fact, are not -- on subsequent examination.

I suspect they just "get confused" at some point and persistently
misbehave.

The bigger the disk, the bigger the problem (because there is more
data at risk/to be restored/recovered) -- think: "large data centers"
(i.e., "technically savvy" users!)

In article <21520dd6-9a8d-400e-8d63-704c064d3348@googlegroups.com>,
 <edward.ming.lee@gmail.com> wrote:
>
>> I would like to but Linux will not mount the HDD. 
> 
>> Is there a way to format or re-partition without mounting?
>
>Have you try fdisk /dev/sdb?
>Be sure not to do it to you main drive.

WARNING! it was /dev/sdc in the original posting, check CHECK check
which drive you are killing there :)

See what [sdX] it shows up at when you connect next time. It may
not be [sdc], it could move on to [sdd] ...


-- 
--------------------------------------+------------------------------------
Mike Brown: mjb[-at-]signal11.org.uk  |    http://www.signal11.org.uk

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---