OpenSUSE Install :: Mounting EXT4 Partition As Drive In Win7
May 22, 2011
I would like to ask you if there is a robust way to mount as a drive a ext4 partition inside windows 7 and if it is possible to use it also to storing window's 7 data.
I am new to linux , I installed Suse 11.3 a week ago on my new iMac 27'' core i7 and my experience have been wonderful so far. However I would like to install windows beside Suse (for games and windows only apps). I used bootcamp to create a 200G partition for Suse, and I would like to partition the bootcamp further to install windows beside Suse, and choose the OS at boot time using rEFIt. I searched google and couldn't find a guide for installing windows 7 when linux is installed first.
1- I want to learn how to partition the boot camp drive using suse to create an empty partition for windows install. 2- I want to learn how to install windows 7 on the mentioned partition without harming any boot configurations, as I said I want to be able to choose from the OSes at boot time using rEFIt bare in mind that the current installed OSes are suse 11.3 and OS X.
I have a very simple question I am creating a new partition for storing files, installers, documents, etc, I am going to make it ext4, now my question is, do I have to specify a mounting point?? I would not like to do that, but if I do not specify a mounting point, will I be able to access that partition? So in what cases you specify mounting point and when you do not specify mounting point?
If you have a contiguous partial piece of an ext4 file system (assuming it's perfectly clean), starting from the beginning of the partition, is there any way to check it, or to mount it to get the files whose parents, inodes and data are all completely contained inside?
Have (or maybe had) a very large 11TB RAID 6 array, filled with a single large ext4 partition. Something strange happened when a single drive failed and the array ended up failing 13 out of the 11 drives. I had trouble getting the array restarted, and got to the point where I exhausted all of the options I considered completely safe. I considered a few things that may have worked, but mdadm doesn't seem to have a definite "do not change anything" option. So I decided the only way to be absolutely safe would be to clone the disks before proceeding - then I realized how much time that would take and sent the drives off to a recovery service so they could image them and check it out.
Before doing so, I copied the first 2GB from each disk. I XORd the images from the working drives to reconstruct the data chunks that were on the failed disk, manually assembled the chunks, and am very confident that I have 22GB of "correct" data in a single file. The parity and Q syndromes all matched (with RAID 6 you can still check with only 1 missing device). I've learned the fine details of ext4 from [URL], and have looked at lots of raw data from the reconstructed partition, and it all looks good. The recovery company says that they're not finding many inodes, but I found a lot of them, exactly where they're supposed to be. I tried to mount and e2fsk, but both processes seem to be extremely unhappy that the device size doesn't match the size implied by the file system geometry.
I considered hacking the superblock to manually reduce the size, but I figure that wouldn't work because there would then be more group descriptor blocks than it would expect after the superblocks. I might try doing that and compensating by incrementing the "reserve block count" to compensate. Alternatively, if there is some way to make the file appear to be the expected size with nothing but zeroes after the end of the actual data, maybe I could mount it and not get any errors until I cause the kernel to read past the true end of the file.
I decided to install windoze 7 and it finally worked. It was complicated, I have two HDD's on cable select and the one I wanted M$ installed on was second in the series. So I changed that around and it finally installed. I then changed it back to the way it was and now of course grub works for SUSE but not M$. I get error #13. My Windows drive also does not show up in sysinfo:/. I went to terminal and ran fdisk -l and
Code: Disk /dev/sda: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0004924b Device Boot Start End Blocks Id System /dev/sda1 * 1 262 2104483+ 82 Linux swap / Solaris /dev/sda2 263 9726 76019580 83 Linux
Disk /dev/sdb: 472.3 GB, 472345632768 bytes 255 heads, 63 sectors/track, 57426 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x30ceb02f
Disk /dev/sdb doesn't contain a valid partition table. And that is the outcome.
currently my fstab entry for a partition is this:/dev/sda6 /media/Media ext4 defaults 0 0 But that seems to not give me any permissions on it, i can't create/copy/paste or anything with files onto it
The default partition manager which OpenSUSE DVD 11.4 uses (Expert Partitioner) is not creating any logic partition with / mount because another system is already using it, is there anyway to fix this?
I am currently installing 11.2 on a new 1TB hdd.the opensuse installer does not allow me to create a / partition (ext4) >20GB. Does anyone know why and how I can get around this limitation?
After installing the recent kernel update and rebooting my machine I have found a horrible fact, my computer won't boot anymore. It seems my root partition was corrupted, and running fsck on it just sends me through a endless loop of "Ignore Errors {y}:" and "Force overwrite {y}:". I have already tried the use the repair system on the installation DVD but that doesn't do anything, the pop up asking if I want to repair the file system keeps coming up when I click repair.
I have done it quite often. Inserted and run the computer from a live CD so that the hard drive is not mounted an changed the partitions. It worked on the old reiserfs when I wiped the windows partition on my laptop to increase the space, it worked on ext3 partitions. Now I resized the swap partition and reduced the NTFS partition on my desktop - no problem. But it does not increase the ext4 partition. No error message it just does not do it. I tried several times with the suggested maximal setting, with a custom setting, etc. It just does not change size. Just for interest I booted into Suse11.0 live CD and tried from there. There I get the answer cannot resize partition as the file system does not allow resizing. Is something wrong with the system or does the partitioner not work with ext4?
I have a system running OpenSUSE 11.3 using the bare server configuration.I had a partition for my /srv directory. All was fine until earlier today. I shutdown my system (to remove an old floppy drive from it). When I rebooted, /srv is emtpy (no files nor directories). This is somewhat vexing, as I had several sites running from there, as well as a fair amount of data.The appropriate partition (/dev/sda3) appears using fdisk. However, there is no mention of it in /var/log/messages.Does anyone know how to recover an Ext4 partition?
I installed opensuse 11.2 some 6 months ago as an alternative to windows 7, on a 44GB partition. Having become my primary OS, I am looking forward to expand the ext4 partition from 44GB to the maximum possible. I have some 24GB unpartitioned space, and free space on NTSF partitions (one of which could be deleted if necessary). What is the best and safest procedure to perform the partitioning.
Tired of fat32 fragility, I reformatted a 4GB pen-drive as ext4 using Yast's partitioner. I chose format as ext4 and checked fstab options "can be mounted by user", "no access time" and "ordered journaling". I thought that these fstab options would be ineffective since a removable device won't be added to fstab. when I insert the pen-drive it auto-mounts and the folder /media/EMTEC is created (EMTEC is the volume name). The relevant mount entries are:
There's no fstab entry, as it should be, and there is a mtab entry corresponding to the pen-drive, /sde1. However the /media/EMTEC as created (by udev, I suppose) is owned by root, I can't write to it. But if I change (as root) the /etc/EMTEC folder permissions so it belongs to the regular user, i can (obviously) write to it *and* it stays so *between* remounts. Haven't tried a reboot yet. What I'm not sure is if ordered journaling is OK for a pen-drive - or any kind of journaling, for that matter. Or will this significantly decrease flash memory life? Also, the fstab options set in Yast appear to be remembered by whatever creates mtab, as well as /media/EMTEC permissions. Is that so? Where are these settings kept? How does this work?
I am not sure this is the right forum, its more about partitions, but it is a bit like it. This is the problem; I have a problem concerning my partitions; I run Opensuse 11.3 KDE 4.4.4 (standard issue) 64 bit.When I installed suse I had only attached one harddisk. A 1.5 Tbhardisk. In that I had made a 50 Gb partition and installed Windows. I tried out linux mint, just for the fun, and thenI installed Opensuse, let it erase mint and gave it another 50 Gb In that it made home etc. The rest Suse also formatted in ext4. Somehow it didn't get a mount point.I then attached second and third harddrive, and gave them mount points Windows/E and F respectively. (They are formatted in ntfs-3g)Yesterday I decided to give it a mountpoint, and gave it /windows/DI changed my mind and changed it to /home2In both these places I could access it but only as read only. And most weird of all, it had a lot of files in them, very much looking like root.
My questions are; How can I access and use that partition?What might these files be? Can I delete them? How would I best mount them? This is a picture of yast expert partitionerImageBam - Fast, Free Image Hosting and Photo Sharing
Some times ago i add Tumbleweed repo to my Open Suse 11.3 64bit system & try to update. On every update with kernel by zypper up it make output like this
I upgraded opensuse to its latest version. After the upgrade I can not any more mount my remote folder.I contacted network administrator and informed that there was no change in the network operation.
I have got a Acer Aspire 9300 which came with one of Bill Gates unreliable operating systems and a recovery partition in case something goes wrong. I surely installed linux (now on opensuse 11.4) as quickly as possible. mounting this hidden recovery partition under linux? All I can see is this from "fdisk -l"printout:
Disk /dev/sda: 120.0 GB, 120034123776 bytes 255 heads, 63 sectors/track, 14593 cylinders, total 234441648 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: 0x34fe34fd [Code]....
I assume that the partition in question is between blocks 0 and 2047?
I'm having some problems with a hosted openSUSE 11.2 server. It was running fine until I did a "zypper up" to apply patches. This included a kernel update.
On reboot the root partition does not mount the / partition giving the following error:
Unrecognized mount option "defaults.noatime", or missing value mount: wrong fs type, bad option, bad superblock on /dev/md2.
Through an Ubuntu rescue disk (this is what Hetzner provides) the disk can be mounted without problems.
( I installed a fresh openSUSE 11.2 with a similar configuration and got the same results after the update)
The server is a hosted installation from Hetzner in Germany with just the basics for LAMP setup.
The disk setup is as follows using software raid1: swap /dev/md0 (/dev/sda1 /dev/sdb1) /boot /dev/md1 (/dev/sda2 /dev/sdb2) / /dev/md2 (/dev/sda3 /dev/sdb3)
I am having trouble getting my portable hard drive to mount after partitioning it for VFAT. I originally had it partitioned as NTFS but I realized that my Xbox 360 will only mount VFAT filesystems. I believe that I partitioned it correctly with yast. However I am still having trouble mounting it. Below is the output of fdisk, mount and dmesg.
# fdisk - l Disk /dev/sdc: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x1e371e37
I have a x64 OpenSUSE server with two hard drivers installed. The first one is used for the / and /home partitions and the other is for backups. Ironically enough it is the backup hard drive I am having trouble with. I was having trouble writting to the drive and unmounted it to preform a fchsk, however now when ever I try to mount it I get the following error:
Just installed 11.3 on my computer, however when I connect an external NTFS harddisk I receive an error message. When I open dolphin to connect to an internal NTFS partition I receive the message:
I just picked up a 1.5TB external drive. I want to wipe the NTFS partition (I assume that's what it is) that is there and replace it with an encrypted ext4 partition.
is there a way of sharing an ext3/ext4 formatted partition on an external USB drive between different users (uids) on different Linux machines without creating a group for this purpose, setting the group ownership of the partition to this group and adding each respective user to the group on every machine?This would mean that I need to have root privileges on every machine... which I may not have in some cases.I'm using the partition to store the code I'm developing on Linux and I would like the option to be safe... if possible.I could use a vfat partition but then I have no control of the rw rights + I cannot develop directly in the dir: I would always have to tar.gz the directory, extract, work, tar.gz, copy to the external drive.
I've a flash drive that it's partitions formatted as fat32, ex4 and encrypted ext4. It works fine on the system that I've formatted it on, but when I try to use it on my other Linux distributions I get these problems:
* ext4 partition accessible by root only. * after entering my pass-phrase I get
Code: /dev/mapper/udisks-luks-uuid-***** uid1000 is mounted What I'm asking for is a way to create the ext4 file system without being attached to some UID and to be accessible by any user.
I just installed F13 x86_64 on a system that used to be running Windows 7.
The boot drive is a SATA drive attached to the motherboard which is working fine.
However, my data drive is an NTFS partition filling a 3.6TB SATA raid.
It's GPT--Gparted sees 3 unknown partitions, and gdisk shows:
Code:
How do I mount this in Fedora 13? I had intended to shrink the NTFS partition so that I can create an ext4 partition to move the data to. Will this be possible?
I've got a LOT of valuable data on this drive, and nothing else big enough to store it.