LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 04-30-2012, 12:18 PM   #1
antares4141
LQ Newbie
 
Registered: Sep 2008
Location: truth or consequences, nm
Distribution: suse
Posts: 20

Rep: Reputation: 11
initialize ext3 disk by mistake


I'm not sure weather the drive I initialized:
http://i185.photobucket.com/albums/x...initialize.jpg
was ext3 or ntfs. I thought it was ntfs and that's why I clicked "ok". But now I'm not so sure. It shows up in drive manager as you can see from the link I provided. (since I clicked the ok button to this same dialogue once already)

On rare occasions in the past I've encountered this dialogue and I'm pretty sure I've clicked ok at least once and the system just recognized the drive it didn't format it or anything.

Searching windows forums for this hasn't provided much in the way of answers.

I've read conflicting post's, some say it formats the drive and others say it just makes it so the operating system can read it.

Does anyone know (for sure) what it does and what to do in a situation like this?

I can't see the drive (at all) in linux now, I've tried both f-disk -l and testdisk. With 3 physical drives attached I only see 2, (sda1 & sdb1) should be an sdc1 but there isn't.

Only thing I know to do now is try loading it up on windows and clicking "ok" to the initialize disk dialogue in drive manager.

drive obviously isn't dead, windows see's it, it's attached to the motherboard via sada port.
Robert Christ
 
Old 04-30-2012, 09:58 PM   #2
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,103

Rep: Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117
Read this - are you sure you want that as (Windows) logical disk ?.
 
Old 05-01-2012, 03:48 PM   #3
antares4141
LQ Newbie
 
Registered: Sep 2008
Location: truth or consequences, nm
Distribution: suse
Posts: 20

Original Poster
Rep: Reputation: 11
Quote:
Originally Posted by syg00 View Post
Read this - are you sure you want that as (Windows) logical disk ?.
No, I am not sure weather it's a ext3 or windows logical disk. I tried to find this out using the fdisk -l command but no trace of the drive. Same with testdisk, doesn't even aknowledge the drive exist's. But windows sees it and I have tried an external usb cable and even attached it directly to my motherboard via a sata cable so I am pretty sure it's not a hardware failure.

And as I stated in the first post my suspicion is that I tried to initialize the disk in windows "drive manager" when in fact it was an ext3 partition.

I'm looking for a way to see it on my linux platform so I can decide how I am going to rescue the data.

Robert Christ
 
Old 05-01-2012, 05:22 PM   #4
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600
Quote:
Originally Posted by antares4141 View Post
I'm looking for a way to see it on my linux platform so I can decide how I am going to rescue the data.
Attach the disk to your motherboard via SATA, check your BIOS and ensure no drive detection is masked, run your Linux distro, once its running type 'dmesg > /tmp/dmesg.log' as root. Then run 'cd /tmp; testdisk /debug /log /dev/sdc' (provided the disk doesn't appear as /dev/sda or /dev/sdb) as root, select the disk, select "none", analyze, quick search, deep search (if available) and quit. Now you have two logs to post (pastebin them): /tmp/dmesg.log and /tmp/testdisk.log. BTW a way to quickly determine if a disk has Windows-like content could be to grep for strings. This one-liner greps /dev/sdc for strings:
Code:
egrep -a -m30 -e "(MSDOS|NTLDR|AUTOEXEC|CONFIG.SYS|NTFS|hiberfil.sys|pagefile.sys|System.Volume.Information|HKLM|HKCU)" /dev/sdc
It stops after finding max 30 occurrences which should be enough to show if the disk does or does not hold a Windows partition.
 
Old 05-02-2012, 02:09 AM   #5
antares4141
LQ Newbie
 
Registered: Sep 2008
Location: truth or consequences, nm
Distribution: suse
Posts: 20

Original Poster
Rep: Reputation: 11
Quote:
Originally Posted by unSpawn View Post
Attach the disk to your motherboard via SATA...
Thanks, I'm out of town so it's going to be a day or two till I get around to it. Usually I can tell how the disk is formatted of course using fdisk -l. I'll post back after I've tried the things you mentioned.
Robert Christ
 
Old 05-02-2012, 03:01 AM   #6
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,103

Rep: Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117Reputation: 4117
Never having used Windows Dynamic disks, but these sort of things (LVM e.g.) generally write meta-data all over the beginning of the extent. Which trashes the filesystem - at least.
Disk scrpaers (like that one unSpawn suggested) might be the only option. Linux has a few, but by nature they are slow, and require similar space to create the recovered files.
Could be ugly.
 
Old 05-05-2012, 08:31 PM   #7
antares4141
LQ Newbie
 
Registered: Sep 2008
Location: truth or consequences, nm
Distribution: suse
Posts: 20

Original Poster
Rep: Reputation: 11
Well it looks like it was a simple mixup with cables which I find hard to believe cause I first started with a usb cable (type) controller and when I didn't see it there (in linux) I went straight to the motherboard which didn't work either.

But I just tried hooking it to my thermotake (drive dock) and it's working now. It's a linux partition and it's mountable and everything is good.

I tried it back on the motherboard again and that works too but I'm guessing I grabbed (by mistake) a cable that went to my esata bracket instead of one that went to the motherboard.

Thanks for all the suggestions

Robert Christ

Last edited by antares4141; 05-05-2012 at 09:38 PM.
 
Old 05-05-2012, 09:46 PM   #8
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600
Hard to believe but mix up you did. Anyway, good to see you got it back.

Last edited by unSpawn; 05-06-2012 at 05:05 AM. Reason: //
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
migrated from ext3-disk to a ext4 disk - now linux wont boot zilogZ80 Linux - Newbie 4 02-05-2010 03:19 AM
ext3 used as ext4 by mistake.. Any way to recover my data? Please help. DigiH Linux - Desktop 9 11-27-2009 02:27 AM
bonehead mistake deleted partitions on wrong disk gfem Fedora 1 12-08-2007 12:31 PM
Recovering ext3 from mistake "mkfs" chris_haragan Linux - General 2 09-05-2005 04:58 PM
Really dumb mistake - need a MDK 9.2 boot disk Delmarc Linux - Newbie 4 03-18-2004 04:39 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 06:42 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration