Ubuntu :: Format Pen Drive Into An Ext3 Filesystem?
Mar 6, 2010
I 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?
how to reformat my Bufalo USB drive to EXT3 format so that I can use it as a secondary drive for my Humax PVR. I am a new user to both Linux Ubunto and Gparted I have downloaded Gparted and connected the external drive to my laptop which is running Ubunto and can see the external drive I have never partitioned or formatted a drive before.
I have a 160Gig and a 40 Gig drive.I would like to install the system on the 160 Gig, and use the 40 Gig drive as a storage for backups or whatever.It appears in the installation process that I am required to use a mount point, which would then turn the drive over to the root system, which would not allow it to be totally available to me.I just want to format it to ext3 filing system.Coffeecat, if you are out there and see this, strange things are happening to the 40 Gig drive - it says it is using 2 gig, but it is totally empty of all system files, hidden files, trash, etc. and it is being imaged in the media folder in root. I believe I have messed this install up to the point of no return and think I should go ahead and start over.
I 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.
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,
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"):
I want to format an USB disk with ext3. If I do this with gparted, it will be formatted, but I cannot write to it. Reading is no problen, at least it shows the lost+found folder. I guess its a problem with access rights. It would be sufficient if user "papa" would have access on one ubuntu karmic machine. But I cannot solve this graphically. The purpose of the operation is to be able to copy my /home directory onto the USB disk as a backup, before I upgrade to the current version of Ubuntu. FAT32 is no option as some files are too long.
I 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.
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.
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 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.
We 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.
I am going to install CentOS 5 on my pc , for3d modeling , and i have some doubts about partitioning the system.
I know that i can have /, /var , /tmp , /home and other directories as individual partitions. I know that i can use ext3 , or xfs ( i know that anaconda doesn't let to use xfs, but i know a way of migrate partitions to xfs after installing) or ext4 , and others , without problems.
But i could for example, once installed all with ext3 , have for example / on ext3 , and /var and /home on xfs.
For me it would be very interesting have /home in a another partition and as xfs (migrating it later from ext3) as mostly i will save in /home a lot of big files ,images,dvd isos,renders , binary maya files and like, and i see a advantage of use xfs with /home.
But a lot of people also use xfs for / as well , but as / has a lot of small files , perhaps use xfs on /var and some other directories, could be good (because xfs performance deleting files or other features), and leave / as ext3 for example.
So is it possible to have different filesystem type for some directories under / ,(for example /var and /home as xfs, the rest as ext3 in / ) , without having any problem ?
(not counting using xfs for a directory that won't see improved his performance because has a lot of static small files or like)
Today I add hard disk and tried to make partion tion as extended. but i could not format it as ext3. and I could not also access the drive using fidsk /dev/sdb1. It rerurns error as: /dev/sdb1 unable to read .
I have a lv image = /dev/vg0/server01. I create a partition using fdisk /dev/vg0/server01. Now, i have a partition under lv image = /dev/vg0/server01p1. how do i format /dev/vg0/server01p1 to ext3, it seems that the system doesn't recognize the partition under /dev. the purpose of this is to fully restore filesystem on domU (xen).
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've had a look at some similar threads but as I'm very new to linux they're already a bit technical for me. Sorry, this calls for someone with patience. I gather from other threads that disconnecting an external drive without unmounting is a no-no, and this seems to be the likely cause. Now the disk is read only and I'm unable to change any settings through the usual control panel on ubuntu. I'm just not familiar with the terminal instructions. I tried to cut and past a few command lines from other threads but I got some warnings that proceding could damage data. Like this one: WARNING! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
During the file system check of an ext3 partition at boot I get the following output:
The super-block could not be read or does not describe a correct ext2 filesystem. If the device is still valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate super-block:
I'm then forced to login in as root and given the following prompt:
I'm reluctant to do as advised by the output and run e2fsck -b because it is not an ext2 filesystem.
Although I can still enter runlevel 5, it doesn't seem to recognise mouse and keyboard input in KDE so my system is effectively redundant at the mo. For this reason any short term workarounds are welcome, but a fix is needed. This problem is part of a longer saga to do with recovering a Windows Vista installation which started failing to boot. I have used both Vista and SUSE tools to try and recover my bootloader to no avail, and this has been the result. If more detail about this is needed please ask and I can explain what I have done.
I have been having problems with filesystem corruption on my eeepc 1000H for a long time now. I have tried using different filesystems, kernels and distributions (arch, slackware) to no effect. I am starting to grow suspicious that this problem lies somewhere else, as I haven't seen anyone else having similar problems in such a variety of scenarios.
I have tried testing my ram using memtest86+, didn't come up with anything after a full run through. I also have tried using e2fsck -c to check for bad blocks, it finds none. I had a go at using smartctl but wasn't really sure what I was doing. I did a long test and it came up with nothing anyway.
This problem is in addition to the problems I've been having with my intel graphics chip and KMS. A lot of the time there are lockups when booting into X, which can only be gotten out of by a hard reset. This is sometimes what causes the original filesystem errors. I've stopped messing around with KMS for now to eliminate this but my current system in unbootable. I'm guessing my disk is wrecked but have as yet seen no definitive proof. Can anyone recommend anything that I should do?
I am currently on ext4 with a custom kernel 2.6.33-rc6 (the stock kernel shipping with slackware does not have the elantech extension for psmouse included). When I was using arch, I was just using the stock kernels.
fscheck is quite annoying, since it usually occurs when I reboot my system performing administration tasks. do I actually need fscheck if Im using the ext3 file system? if not how would I extend the period between checks or just turn it off altogether?
I need some assistance in trying to format a USB hard drive to vfat format but can't seem to do so. I am currently using RHEL 5.3. I have tried the following commands and they all come back as "command not found"