I am trying to set up an atom D525 low power PC 64-bit with a 40 GB solid state disk drive. Is it possible to specify ext4 during the install for proper SSD suupport? I read somewhere that after install I can place a -discard line in fstab to enable trim.
Edit: should I have asked this in the x86_64 forum, as I was planning on installing 64 bit?
It is any possibility to install centos 5.5 on ext4 by anaconda ? Is ext4 filesystem is secure for files server (samba) ?? In anaconda installer there is only ext2, ext3 choice.
View 16 Replies View RelatedI had 5.4 machine. Upgraded to 5.5 today via yum upgrade. All went fine. Rebooted. Wanted to convert root partition to ext4 (I have three partitions: /boot, / and swap). All of them on software RAID 1 (root is /dev/md2). I did the following for converting
yum install e4fsprogs
tune2fs -O extents,uninit_bg,dir_index /dev/md2
nano /etc/fstab # I indicated here that my /dev/md2 is of ext4
[code]....
We're planning to install CentOS on a new server that will be based on two Solid-State Disks in a RAID1 configuration. The RAID management will be handled by a hardware Adaptec controller. I've learnt that the TRIM function for SSD drives is supported starting from kernel 2.6.28.
View 1 Replies View RelatedDoes CentOS 5 support the ATA TRIM command for use with SSDs? Is the support automatic by default, or would I need to do something specific in order to enable the TRIM feature be used?
View 1 Replies View RelatedSummary of issue: EXT4 filesystem won't mount--with error = mount: unknown filesystem type 'ext4'. Is no ext4 in kernel the issue? Or is something corrupted?Really perplexed by this. I updated Centos 5.5 to 5.6 to get ext4 (5.6 is supposed to have full support of ext4). I built several arrays and put the ext4 filesystem on them. All went well until I tried to mount them. BTW, this array (below) is set up as a RAID6 using partition 1 of #8 2TB drives.Bear with me here; just trying to be complete and not waste your time.
Attempting to mount give this:[root]# mount -v /dev/md1 /asc/array1mount: unknown filesystem type 'ext4'Note: it does "fake" mount with ption (which apparently does everything except the system call):[root]# mount -f -v /dev/md1/dev/md1 on /asc/array1 type ext4 (rw,grpquota,usrquote)e2fsprogs:Package e2fsprogs-1.39-23.el5_5.1.x86_64 already installed and latest version (for Centos 5.6; CentOS 6x uses the 1.41...)
I'm using CentOs 5.4 (2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:30:06 EDT 2010 x86_64). I tested out ext4 on a partition for the last few months and it seems to work fine. The issue is that quotas dont seem to work correctly on it. Is there a way to revert back to ext3? Mainly the quota tools do not work on it.
View 1 Replies View RelatedI am noticing RHEL 5.4 is in beta. Does anyone know what 5.4's plans are for ext4? Is it still going to be a non-bootable addon? Or, will GRUB now boot off it?
View 1 Replies View RelatedWith the release of CentOS 5.5 ext4 is considered stable in this distribution so I decided to migrate to it. Luckily I started from migrating fresh server with CentOS 5.5 using some instruction I found on the internet. I think I shouldn�t say, that I screwed the whole thing up ;) After about 6 hours cursing, kicking, and crying I solved the task and figured the correct sequence of actions. The small problem with migrating root partition is that you can�t unmount it BTW.
During migration task, I found, that CentOS 5.5 rescue mode is somewhat broken a little in terms of ext4 support. It can mount ext4 partitions successfully. But its e2fsprogs package (tune2fs, e2fsck etc.) doesnt see ext4 partitions and say, that superblock is corrupted on a partition once is converted to ext4 (at least it did it for me. May be I should force filesystem type with -t ext4 switch?). Keep in mind, that if you screw your system up too badly, you will not be able to run tune2fs and e2fsck on it from rescue modeBut you will still able to mount it if it is not corrupted badly. In all below examples,Boot your system normally and login as root. Upgrade kernel if you wish (I usually use yum upgrade to upgrade all on new machines). Then upgrade/install some other packages
I have installed 2 extra 1.5TB drives on a stable Centos 5.5 system. They are set up with 2 unequal partitions on each - with 2 raid 1 arrays. The largest of the raid arrays is used as a new volgeoup with 2 unequal LVMs. The larger of the LVMs is around 1.3TB. I installed an ext4 filesystem (default parameters) on the larger LVM.I went to mount the LVM - the system hung. No keyboard or network response and no response to the soft shutdown button.It was the deadest I have ever seen it - and this system has been incredibly stable.
In the absence of any other suspects - I am tempted to blame ext4 - since I have never used it before - and since wikapeadia tells me ext4 isn't supposed to be in the 2.6.8 kernels...:
[URL]
I will do some more testing on this tomorrow to try to confirm my suspicions. I will try to repeat the crash - then try mounting it as ext3 to see if it behaves differently. Any other tests I should do?What is the status of ext4 in RHEL5.5. Has it been added to the 2.6.18 kernel by RH? Is this what is meant by a "back port"?
Which file system uses Centos 5.6 by default, Ext3 or Ext4? I have installed on Ext3, it's upgrade from 5.5, but howto convert into Ext4 without damage or lost data?
View 3 Replies View RelatedI got a problem booting ubuntu 10.4 RC but i solved it by replacing root partirion uuid in grub boot menu then I disapled totally uuid passing to linux from /etc/default/grub . but something else i noticed why grub choosed insmod=ext2 why not ext4 specially I use now ext4 .I tried by editing the grub boot menu replacing "insmod=ext2" by "insmod=ext4" it booted and the three lines error during booting that i used to see them science ubuntu 9.10 totally disappeared . really I dont understand can anybody explane for me.and if what i did was right ,can anybody tell me how to make grub always and permenantly detect ext4 as ext4 not as ext2.
View 6 Replies View RelatedI just trying installing OpenSuse 11.2 on a Dell Dimension 4500 2.0 Ghz with 512 mb memory and 40 gb hard drive.During the installation the following error was produced: "System Check for partition /dev/sdb1 contains no valid Ext4 file system". After the install process was completed, the keyboard and mouse were not useable
View 7 Replies View RelatedIs ext4 available in CentOS 5.3 ?
View 5 Replies View RelatedI am wondering if Ubuntu support ATA TRIM for SSD out of the box?
View 1 Replies View RelatedI was running it portable on a 4gb usb drive via virtual box which worked great unless I used a computer that had virtualbox on it. The portable version would remove files that the original version needed. I decided to try Qemu. The problem is that the portable version only allows 1gb of space to install regardless the size of a usb drive. so the question is: Is there was a way to trim ubuntu 9.10 down to less than 1gb of disk space? If not is there another portable emulator that could be used instead? the only uses for this are for the use of evolution and opera in a linux environment.
View 3 Replies View RelatedOk, Im likely to buy SSD 128gb drive and install Fedora 14 on it...but I have a question. If I go with ext4 will I get TRIM to work out of the box? Whats the status of kernel support on trim?
View 8 Replies View RelatedI have an OCZ Vertex SSD...the 30GB variety. recently I upgraded my kernel to 2.6.33. I have read that that is all that is needed in order for trim to just start working. Is there a way that I can verify that TRIM is working?I'm debating getting the Vertex2 100GB model because I love my SSD now, but would love to have a little more storage space. I just don't want to buy it without TRIM working.
View 4 Replies View RelatedFor anyone who is not familiar with it, I am talking about the trim functionality in the 2.6.33 kernel for solid state drives.
View 6 Replies View RelatedI followed this tutorial [URL] to enable my TRIM support and now my fstab looks like this:
Quote:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
[Code].....
but when I follow the second half of the tutorial http://lightrush.ndoytchev.com/rando...bledandworking to check and make sure it's working I don't get all zeros like I'm supposed. I tried waiting a while like I saw in another tutorial as well and check it again.. Still random numbers and no zeros.
First system specs. Gateway Solo Pro 9300, 433Mhz, 288megs. OS Slackware 13.1 32-bit and KDE.
As I get more comfortable with Linux I find that I am doing more waiting for the computer to catch up.
Would it be better to trim down KDE or change to a lighter GUI? If I change to a lighter GUI will I have to reinstall things I have installed under KDE?
I want to know if it is (a) possible to encrypt my Linux ext4 file system after I have installed the OS? (b) what is the best method/application to do this?Ubuntu gives an option to encrypt the partition via the installer. I would only like to encrypt the partition and not the drive because there are other partitions/OS's. I feel this is a necessary procedure for my portables (laptop, netbook) if they are stolen. I am predominately using Ubuntu 10.04 i686 with the ext4 filesystem.
View 3 Replies View RelatedI just bought a Samsung 850 Pro 250GB SSD drive and have since then found out that Linux has/had a faulty implementation of queued trim (which is a synonym for NCQ I think). I'm using kernel 4.1.0 (the default selected by the Debian 8.1 installer) and I've read that Samsung drives are blacklisted for queued trim by the recent kernels. However, the output of dmesg contains the following lines, with and without TRIM enabled for the drive (i.e. with or without the "discard" option in fstab for the drive):
Code: Select all[ 1.012287] ata6.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.013438] ata5.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 1.013440] ata5.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[ 1.015037] ata5.00: failed to get NCQ Send/Recv Log Emask 0x1
Since the depth is not 1 but rather 31, it looks like NCQ is enabled. I've disabled TRIM on the drive for now, and whether it's safe to enable TRIM or not.
Does Suse have any software based TRIM support available or that is in the works?I know there is to a degree new firmware becoming available that supports TRIM (although some are pretty rudimentary) but windows 7 does a fairly good job software side and upgrading the firmware occasionally involves the unbridled joy that is wiping the drive and starting again.
View 1 Replies View RelatedThere are not SSDs with TRIM support available in my region that fit into my laptop (1.8", IDE, ZIF). I'm running Ubuntu 10.10.
Most articles (or questions on superuser) I've come across concering TRIM (or the lack thereof) date back to 2009, when not many SSDs with TRIM support were available and OS support was still very fresh.
I'm interested in the current situation, but I couldn't find too much information about it.
What are currently the "best practices" for using an SSD without TRIM under Linux?
I've read about the wiper script included with hdparm. Do I understand correctly that I could use this to free unused blocks, e.g. by running it once a month?
Some sources state that HFS+ (the default-filesystem of Mac OS X) doesn't suffer as badly from lack of TRIM as other filesystems. How about linux filesystems? Are there filesystems that are better suited for SSDs without TRIM than others?
My partition /dev/sda3 on an SSD drive doesn't contain any filesystem, but it contains garbage. How do I do a TRIM/DISCARD operation on the whole partition?
View 2 Replies View RelatedThe situation with TRIM in Ubuntu has me utterly confused. I don't know whether I need to manually run it or not. Sources I've found are disparate and unclear. I have Ubuntu 10.04 with latest updates (including kernel 2.6.32-26). I have an Intel X-25M drive with latest firmware, and it is formatted as ext4. So, does TRIM support run automatically? If not, how do I check if I need to run it, and then how do I run it if necessary?
View 1 Replies View RelatedIn windows the only controllers that really work with TRIM is the onboard Intel ones, Jmicron, Marvell, Nvidia and AMD's don't pass the command to the drives if you use their own drivers. (And from what Ive read, the Micron sata6 controllers don't work with TRIM even using the default Microsoft drivers). In Linux do more then just Intel drives work with TRIM? I have a Nvidia 790i Ultra motherboard, the SATA controller is an Nvidia one which has 2 settings, ATA and Raid (if the drives aren't added to an array it runs them in AHCI) and has an additional Jmicron sata port.
If I enabled TRIM in the OS, would it work on either of those controllers? Also if anyone knows this, in Windows if you set an Intel controller to raid, you wont get TRIM on SSD's that are on the controller (but not in an array) with the default Microsoft driver like you would if it was set to AHCI, you only get it with the Intel RST drivers. Would a SSD on an Intel controller set to raid but not in an array get the TRIM command passed to it in Ubuntu?
Thinking of a re-install to remove LV and use Ext4 only. [Root is too large] Can I back up Home from the LV and move it to an external drive. If so will I be able to reinstall and Custom partition so I can use Ext4 and then copy the Home files back to my new Home partition. I have only a small knowledge of LV systems so just want to be carefull.
View 1 Replies View Relateddoes Debian Lenny 5.0.4 stable supports SSD TRIM? If not, what package i need to add if i buy a new SSD and dont want to loose Hard Disk Performance over time?
View 14 Replies View Related