Yesterday I ran an extremely dangerous command by mistake:
Acctually I intended to dump the iso to a usb disk. Soon I found the "of" is incorrect, but 1 second has passed...
Since everything happens in 1 second, only MBR and /dev/sda1 has been affected. The filesystem of sda1 is ext3.
So, can I get any luck trying to recover data from the broken partition?
I'm wondering if anyone knows what will be Squeeze's default filesystem. Will it be the proven ext3 or the newer (sometimes faster, sometimes slower) ext4?
I currently have ext4 and I have nothing to complain about. In fact, my overall experience has been very positive. Ext4 is definitely faster when fsck runs during boot.
What would be the cons of having ext4 as default in Squeeze?
How to recover ext3
Quote:
A HP Netserver LP2000r, with original SCSI controller and HP NetRaid-2M controller, 3x 36GB Ultra3 HDD in RAID5, Debian (sarge/etch), has crashed after 992 days without reboot. From all that I can see, a hardware failure, most likely with the memory. The HP Diagnostic tools cannot find any problem, but everytime I boot into Knoppix, I get between 2minutes and 2 hours of runtime, and then either a kernel oops or just a complete and sudden halt.
Well, the box has earned its money. However, there is some data on the drives that I need to recover (yes, I have beaten myself up properly about not backing up that data, don't even go there !). There are three partitions: sda1 is /, sda2 is swap and sda3 is a LVM volume with 3 logical volumes on it. As far as I can tell, the hardware defect must have been creeping in and has made a total mess of the inodes in all these partitions.
After booting into Knoppix, I can restore the volumes using pvscan, vgscan, lvscan, vgcfgrestore and vgchange. If I try and mount them: mayhem. So I try and check them, using fsck.ext3. All sorts of interesting nonsense, such as a completely empty inode 11 (the first inode) and then obviously from there on all else is pointless. I tried using debugfs, but the information on what to do with it is somewhat spurious.
P.S.: Tomorrow I will go and get myself a 16GB Flash Drive and then hopefully I will be able to dump the partitions one by one onto that drive and transfer the images onto a different computer for analysis and data recovery.
recover deleted files using "debugfs" & "extundelete" by running:Code:sudo debugfs /dev/sda3
and find inode number of deleted file using "ls -d" command and then running:Code:sudo extundelete /dev/sda3 --restore-file <inode#>but when my desired file was in a deleted folder I can't find my desired file inode number using debugfs
Now am terribly frustrated because i reinstalled my linux installation(Ubuntu 8.04) after falling prey to an inode error. So i reinstalled stuff under my root partition under which i had some files which i obviously lost.I have tried recovering the files (mostly mp3 files) using photorec and the max file size i managed to recover was 4.0MB. the rest fall in the tune of 300kb.My question is, is there a way to make a full recovery of the above files seeing that they indeed can be recovered?
View 1 Replies View RelatedI wanted to upgrade from Intrepid to Jaunty. I opted for a format/reinstall as I figured upgrading usually sucks. To save my important data, I resized my partition (partition A), formatted the empty space with ext3 (now partition B), and moved the necessary files from partition A to partition B. Then I went through the install process and installed Jaunty on partition A, telling the installer to NOT format partition B. It gave a warning about the installer deleting system folders (var, usr, etc) but I figured it didn't apply. I was wrong.
So now partition B is "empty." I know it didn't format it, but I need to get those files off of there. I have created an image of partition B using ddrescue, but I don't know where to go from there. I tried using foremost, but it won't recover things like my virtual machines and completely nukes the original file structure I had. And I've tried mounting it (using sudo mount -t ext3 -o loop /home/user/recovery.img /mnt), but that doesn't seem to work. The mount command completes successfully, but nothing shows up in the folder I mounted it to.
I have accidentally removed vmware virtual disk, my host operating system is RHEL5.2 with ext3 file system, i have used photorec, magicresue and foremost but still no luck to recover the vmdk file. i have seen in foremost configuration file that there are some predefined files (ex- doc, pdf, jpg, avi, zip, etc),
1. is there any way to add vmdk file extension on that configuration file?
2. if yes how can i do ?
3. by adding vmdk on configuration file, can i specifically use recover option for vmdk?
By mistake I formatted an ext3 partition on my external hard-drive. Now it has turned into a vfat filesystem. Is their any chance of recovering the lost data?
View 4 Replies View Relatedi want to know how can i recover deleted files in ext3 partition manually(not using any tools)?? probably using the 'grep' command. if someone know pls tell me...
(i have recoverd deleted files in an ext2 partition with debugfs and dump . but dumping doesnt work for ext3)
I am using CentOS 5.5.I suppose this is an oft repeated question. I accidentally deleted, using rm command, 2 wmv files. The files were in a single ext3 1Tb drive, with just 1 partition --- the ext3 one. Each file is 600 - 800mb. The 1Tb drive has only about 20Gb data.Immediately after deleting the files i unmounted the drive (/dev/sdc1). Thereafter i searched the the net and came to know of the recovery tools foremost and photorec. I have installed both of them. I am currently running both of them as root --- foremost is just showing a lot of * signs on the terminal and photorec has managed to find some txt and png files --- but no wmv.For foremost i used: /usr/sbin/foremost -t wmv -i /dev/sdc1For photorec i followed some instructions available on the web.
In the meantime, based on some post on the net i ran debugfs as root, then cd into the directory where the files were deleted. Then on typing ls -d i managed to get the inodes of the 2 deleted files and the names of the deleted files are also correct. The instructions on the net http://www.theavidcoder.com/?p=3 tell me to run fsstat and dls both of which i am unable to find in /bin, /usr/bin, /usr/sbin and /sbin. So i am unable to proceed further.
When installing fedora 10 from scratch on an acer aspire one 150L, which filesystem should be used? ext2 or ext3? a basic explanation of the reason would be great too.
View 3 Replies View RelatedI was running ubuntu as a live cd and I wanted to format my pen drive into an ext3 filesystem. I put in sudo mkfs /dev/sda1, but know im thinking that sda1 was my HDD!! I removed the cd from my computer, and it wont boot up into windows anymore!The only thing that is giving me hope is that the mkfs took about 1 min to format whatever it was formatting (my pen drive or my hdd!!) and my hdd is 500gb big. Is there anyway that I could have accidentaly formatted my HDD?
View 9 Replies View RelatedI run an upgrade and an update on a lucid lynx beta 2. --- got no problems. but about the filesystems i have some questions because it seems for me that at every system boot the system will run an fsck. somtimes it's shown up, somtimes not. but in /var/log/messages and in syslog
I have always following messages ( occured in beta 2 too ).
But first before i continue - here my disk layout:
And here my filesystem types:
This is my problem because those values are seems to be static ! ( note: this partiton is mounted but not in use ) and last not least: the drive is an external usb scsi disk. but on the other side lucid lynx is running fine on my box.
This question is about windows xp but since I rarely use it and dont care about to sign up for some xp related forums
View 1 Replies View RelatedI was looking in a dir I haven't used for a while (I use it for data storage) and found a directory was repeated - that is, two directories with the same name. I renamed one of them, on the assumption that one of them has a non-printing character in its name, and that worked without a problem, but ls -i lists their inodes as the same. ls -l says they both have two inodes (. and ..), and the files they contain have the same names. The inodes of the files is the same (that is, the inode of a file in dir A is the same as the file of the same name in dir B.) Each file in each dir is listed as having only one inode, but it's the same as that in the other dir.
View 1 Replies View RelatedI've scoured the list of options for FS type in cfdisk for ext3 or ext4 to no avail. How then do I set the filesystem type for my partition to ext3?
View 3 Replies View RelatedI am facing a serious problem.I installed UBUNTU 10.04 and encrypted it during installation. I accidentally erased some of the necessary files from root folder. now the the OS is NOT booting.luckily i still have the encryption key i have some important documents in that drive (desktop folder).
PS: I have tried to run Live Ubuntu it shows the Root, but it does not enter any of the folder.
I've ran fsck -c on the (unmounted) partition in question a while ago. The process was unattended and results were not stored anywhere (except badblock inode). Now I'd like to get badblock information to know if there are any problems with the harddrive. Unfortunately, partition is used in the production system and can't be unmounted.
I see two ways to get what I want: Run badblocks in read-only mode. This will probably take a lot of time and cause unnecessary bruden on the system. Somehow extract information about badblocks from the filesystem iteself. How can I view known badblocks registered in mounted filesystem?
I have a external HDD with eSATA and USB connectors available. I want to use this HDD to store my backups. The HDD should be encrypted (my main system is as well).
So here is what I did so far:
1) I used the following code to create the encrypted LUKS partition with EXT3 Filesystem:
Code:
cryptsetup -c aes-xts-plain -s 512 luksFormat /dev/sdb1
cryptsetup luksOpen /dev/sdb1 luks
mkfs.ext3 /dev/mapper/luks
The system always hang when I executed the "mkfs.ext3..." command, so I switched the HDD from eSATA to USB and then it worked fine.
2) When I switched on the ext. HDD the first time, the drive was recognized automatically and Nautilus asked for the password. I typed it in as checked the checkbox to remember the password in the future. For the backup I use a nice script that I found in another forum, where I can define a mountpoint and then the script will check for previous backups and only make a incremental backup based of the latest version. The script also mounts the drive automatically. In order to always have the same mountpoint, I want to make an entry in the /etc/fstab using the UUID of the ext. HDD.
Whatever I tried, it doesn't work. What am I doing wrong? Here is my current /etc/fstab
Code:
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/mapper/ubuntu-root during installation
UUID=2ea47421-73ce-4c66-9606-8a1db81ae640 / ext3 relatime,errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=dbdeb793-1d4e-43ea-8986-7b37fdbc9674 /boot ext3 relatime 0 2
# /home was on /dev/mapper/ubuntu-home during installation
UUID=42702091-83e6-43eb-aad1-108f43eedf9d /home ext3 relatime 0 2
# swap was on /dev/mapper/ubuntu-swap during installation
UUID=e225bcf9-908b-4226-a963-6b02ee658df1 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# Eintrag wegen iPhone
none /proc/bus/usb usbfs devgid=125,devmode=666,nodev,nosuid,noexec 0 0
# external HDD
UUID=913977f7-8fa6-416f-af79-b5f913b68f53 /media/backup-hdd ext3 noauto,users 0 0
I made the "none /proc/bus/usb..." entry because it was recommended to ensure correct behaviour of the iPhone. Not sure if I need it though.
I created the mountpoint with this command:
Code:
sudo mkdir /media/backup-hdd
Now it seems the mountpoints owner is not root - strange right?
Code:
2 4 drwxr-xr-x 3 michael michael 4096 2010-01-15 02:45 backup-hdd
How should I mount this drive correctly? It will be automounted as every USB device, but that should not be the case. I want the script to mount and unmount the drive.
I just got a new hard disk so that my "/" and "/home" partitions would be located at their own separate drives. All was well until i tried to expand my "/home" partition to fill up the entire drive that used to also have the "/" and swap partitions on there. Let me sketch the before-and-after scenario in GParted,
Before:
What actually happened after:
Gparted gave an error prompt after which i found out that the entire ext3 partition (/home) had been moved to the left but not yet expanded to the right, which is of course not a problem. However, for some reason it has labelled the entire ext3 partition as a swap partition!
I'm still running ubuntu from the usb flash drive, because i dont want to risk that the (120GB) swap area will actually be used and cause my data to be lost.
I guess my question is, can i relabel the swap partition as ext3 like it was before without formatting (ie without losing data)?
Here's the output of "fdisk -l", which doesn't show the swap area (the drive in question is "/dev/sdb"):
Code:
I have installed ubuntu to my pc. i made 3 partitions. one for system, one for data and one for swap. two of them were ext4. after some time i have reinstalled ubuntu again. but this time i didn't put to format the second partition, but just mount it using ext4. after that i cannot open my files. checked with gparted shows that 2GB used, but with df 188MB. and in properties writes ext3/ext4 filesystem. i used chown, chgrp but didn't help. please help, these data are ver important. i cannot lose them.
View 7 Replies View RelatedWe have 3 RH5u4-64 servers. Server 1 is a standalone server. Servers 2 & 3 are clustered filesystem servers running Veritas CFS 5.0mp3.
Server 1's filesystem is EXT3 and was cloned from a Sun server running Veritas 5.0mp3-VXFS. Filesystem size returned from 'du' 'df' show about 428GB on both the Linux Standalone Server(EXT3) & the Sun Solaris Servers (vxfs).
We then cloned Server 1's filesystem (EXT3) to the 2-node CFS servers. Cloning was successful, but the filesystem sizes returned by 'du' 'df' show 128GB. Block Size for the EXT3 filesystem is 4k while blocksize for the VXFS filesystem is 1k.
Where did that other 300GB go?
I can see VXFS/CFS being slightly more efficient than EXT3 because it's been around much longer, but that can't possibly account for the vast difference.
Is that possible, I mean when I upgrade F10 to F11 with yum upgrade is there a way to 'upgrade' the filesystem to ext4 for example (with the exception of boot partition)? Or I have to reinstall fedora like new?
While changing the filesystem can I do it by parts? what I mean is for example: I have 2 partitions like '/' and '/home' with ext3, so I backup data in '/home', change '/' to ext4 then mv files from '/home' to '/' and change '/home' to ext4 and finally mv those files from '/' to '/home'. Is that possible?
I have two ext3 partitions within an encrypted lvm2 volume. when i start up my system it says that there are 0.3% non contiguous blocks.
This is my steup:
When i want to repair with repair system from dvd it tells me that the repair and check operation for encrypted LVM devices is not supported. so how can i fix my filesystem?
I am trying to figure out a totally odd behavior of the ext3 filesystem mounted in Ubuntu 9.10. There is a Korn Shell script, part of which does the following in the loop:
while ((1)); do
mv dir1/file dir2;
if [[ ! -r dir2/file ]]; then
echo "ERROR"
ls -l dir1/* dir2/*
exit 1
elif
echo "OK"
fi
done
Given that dir2/file always exists and that I do not move it asynchronously with "&", my script should never hit the "ERROR" statement. The odd thing is that it does, and quite randomly (no pattern at all). However when it does hit the ERROR case, ls -l prints that file is in dir2 and it is readable! I tried using "-e" instead of "-r" test - no luck. I never seen anything like this in 10 years of my programming experience. Same script worked fine on Fedora 11, and yet it wouldn't work on Ubuntu.
At boot time, before entering Runlevel 3 the HDD will go mad when mounting tmpfs on /dev/shm...
Code:
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
INIT:Entering runlevel 3
It will go on and on at the tmpfs on /dev/shm type tmpfs (rw) until i press ctrl-C...then I will stop whatever it is doing, let the hdd rest a bit, and resume normal boot..
i got stuck while booting my LINUX box.it looks likes filesystem(EXT3) currept.recover the filesystem or the altrnative to it. I have IMP data in my machine
View 1 Replies View RelatedWhen I rebooted my system (RHEL 5.3 x86_64), I got the following error when it was booting up:
Code:
Full screenshot of the bootup error messages here: previous bootup error
So to try and fix this, I booted from the OS disk and did a linux rescue.
Here's some of the results of the commands I did:
Code:
Here's a screenshot of the output from fsck after it's done, notice it says 0 bad blocks but the system was modified:fsck results
I then reboot but now I get the errors:
Code:
Full screenshot of the startup errors I get now here: current bootup error
Does anyone have any ideas on how I can fix this? Was the fsck I did initially the correct thing to do to fix that initial group descriptor error or did I make things worse?