[Solved]Grow an XFS partition

I have /dev/system/home which has been enlarged by 20GB to 60GB, the XFS partition on it is 40GB in size. When I view the help section I don't know what option to use:
[root@JORDAN-CD3CDA3B jordanwb]# xfs_growfs --help
Usage: xfs_growfs [options] mountpoint
Options:
-d grow data/metadata section
-l grow log section
-r grow realtime section
-n don't change anything, just show geometry
-I allow inode numbers to exceed 32 significant bits
-i convert log from external to internal format
-t alternate location for mount table (/etc/mtab)
-x convert log from internal to external format
-D size grow data/metadata section to size blks
-L size grow/shrink log section to size blks
-R size grow realtime section to size blks
-e size set realtime extent size to size blks
-m imaxpct set inode max percent to imaxpct
-V print version information
Last edited by jordanwb (2008-10-13 00:33:49)

According to this site:
http://www.linux.sgi.com/archives/xfs/2 … 00008.html
You just run `xfs_growfs /dev/system/home` to let it fill the available space on the device

Similar Messages

[~SOLVED] 1 min hang during boot while mounting xfs partitions (LVM)

Hi all,
After the upgrade I did yesterday (which included linux-3.12.8-1 and lvm2), the boot time has increased by 1 minute as the system hangs while mounting two partitions formatted as xfs and residing on logical volumes.
$ systemd-analyze blame
1min 13.676s home-VDP76-videos.mount
1min 13.111s home-VDP76-VBox_VMs.mount
2.980s [email protected]
I have the fsck hook as second-to-last entry in my mkinitcpio.conf, but the fstab entries for these partitions include
... xfs defaults 0 0
so, as far as I undertstand, the partitions should not be checked, am I missing something!?
I have googled for similar issues but I did not find anything useful, any suggestion would be greatly appreciated.
Thanks
edit: I blame the check disk because of what reported on the system journal (note the time stamps):
Jan 23 00:10:37 ArchTP kernel: psmouse serio5: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
Jan 23 00:10:39 ArchTP kernel: psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
Jan 23 00:10:40 ArchTP kernel: input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio4/serio5/input/input25
Jan 23 00:11:47 ArchTP systemd[1]: Mounted /home/VDP76/VBox_VMs.
Jan 23 00:11:47 ArchTP kernel: XFS (dm-4): Ending clean mount
Jan 23 00:11:47 ArchTP kernel: XFS (dm-3): Ending clean mount
Jan 23 00:11:47 ArchTP systemd[1]: Mounted /home/VDP76/videos.
Jan 23 00:11:47 ArchTP systemd[1]: Starting Local File Systems.
Jan 23 00:11:47 ArchTP systemd[1]: Reached target Local File Systems.
I should also add that the involved partitions are ~20 Gb each and quite full...
edit2: I have freed up almost all space on the video partition and the time for mounting those partitions has now decreased to 8 sec...I will mark the thread as solved, but I still would appreciate an input on the reasons why the partitions are checked regardless of the fstab setting, for example, is this pertinent!?
dumpe2fs -h /dev/mapper/waldorf-video | grep -i 'mount count'
dumpe2fs 1.42.8 (20-Jun-2013)
dumpe2fs: Bad magic number in super-block while trying to open /dev/mapper/waldorf-video
Last edited by VDP76 (2014-01-22 23:38:25)

WonderWoofy wrote:I don't think that the fsck.xfs is really a fsck at all. It is there for compatibility purposes, and a real check can be done with xfs_check and xfs_repair. So the fsck.xfs will just always give an exit status of zero.
exactly..in fact the man page says
fsck.xfs(8) wrote:fsck.xfs - do nothing, successfully
so fsck.xfs simply exits with a zero exit status.
running xfs_check gives
xfs_check is deprecated and scheduled for removal in June 2014.
Please use xfs_repair -n <dev> instead.
and xfs_repair does not find errors on both partitions.
Still, I do not understand how nothing being done can take up so much time.
By the way, a short S.M.A.R.T. self-test did not report errors...
In the meanwhile, there has been another kernel upgrade and the timing issue persists, so I am assuming it has something to do with the last lvm2 upgrade.

[SOLVED] XFS partition or Harddrive failing

Hello
My /home XFS-formatted partition is in different disk (seagate 750G). Lately it has begun failing constantly when doing lots of copying/moving work with following type of errors:
- cannot read first 512 bytes
- mount: special device "dev/mount-by-label/home" does not exist
The last one happened during normal boot. After powering off, waiting a while and booting again all was good - until I tried to backup my data, when midway while copying I got:
FXS metadata write error block 0x403e880 in sdb1
I/O error in filesystem meta-data ("xlog_iodone") error 5 buf count 2560
Filesystem: Log I/O Error Detected
I tried to find solution from several forums, but all I got was to try "xfs_repair". It doesn't find any errors when the partition/drive is working properly, but after I tried backup my data and got those errors above, "xfs_repair" gives following:
[root@golved ~]# xfs_repair /dev/sda1
Phase 1 - find and verify superblock...
superblock read failed, offset 0, size 524288, ag 0, rval -1
fatal error -- Input/Output error
I am currently trying "smartmontools", but at leas now it doesn't work. Maybe after reboot it gives me some sensible output. Meanwhile, can any of you give me any pointers how to find out is the problem in XFS filesystem or in my year old Seagate Barracuda 7200.11/12(?) 750G harddrive? How about getting my data out, is there way to bypass the logging that xfs does? I am thinking about that because of those "Log I/O errors"... Currently, whenever the drive mounts properly, I can do some copying but it halts eventually. Maybe disabling logging and all other non-needed things from xfs would let me backup more data before I/O errors arise?
Last edited by mclang (2009-03-11 06:43:21)

Okay, after couple of boots smartctl gave following:
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11
Device Model: ST3750330AS
Serial Number: 9QK06CMQ
Firmware Version: SD15
User Capacity: 750 156 374 016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Sun Mar 8 18:42:27 2009 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 634) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 172) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103b) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 101 097 006 Pre-fail Always - 52655725
3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 26
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 2043
7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 8613925167
9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 8431
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 26
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 031 031 000 Old_age Always - 69
188 Unknown_Attribute 0x0032 100 099 000 Old_age Always - 8590065666
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 070 055 045 Old_age Always - 30 (Lifetime Min/Max 28/32)
194 Temperature_Celsius 0x0022 030 045 000 Old_age Always - 30 (0 21 0 0)
195 Hardware_ECC_Recovered 0x001a 047 022 000 Old_age Always - 52655725
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 4
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 4
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 100 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 100 occurred at disk power-on lifetime: 8426 hours (351 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 02 00:27:26.893 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 02 00:27:26.887 IDENTIFY DEVICE
00 00 00 00 00 00 00 04 00:27:26.733 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 02 00:27:21.427 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 02 00:27:21.420 IDENTIFY DEVICE
Error 99 occurred at disk power-on lifetime: 8426 hours (351 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 02 00:27:26.887 IDENTIFY DEVICE
00 00 00 00 00 00 00 04 00:27:26.733 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 02 00:27:21.427 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 02 00:27:21.420 IDENTIFY DEVICE
00 00 00 00 00 00 00 04 00:27:21.267 NOP [Abort queued commands]
Error 98 occurred at disk power-on lifetime: 8426 hours (351 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 02 00:27:21.427 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 02 00:27:21.420 IDENTIFY DEVICE
00 00 00 00 00 00 00 04 00:27:21.267 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 02 00:27:20.931 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 02 00:27:20.887 IDENTIFY DEVICE
Error 97 occurred at disk power-on lifetime: 8426 hours (351 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 02 00:27:21.420 IDENTIFY DEVICE
00 00 00 00 00 00 00 04 00:27:21.267 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 02 00:27:20.931 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 02 00:27:20.887 IDENTIFY DEVICE
c8 00 30 af 05 ae e3 00 00:27:17.797 READ DMA
Error 96 occurred at disk power-on lifetime: 8426 hours (351 days + 2 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 04 9d 00 32 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 02 00:27:20.931 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 02 00:27:20.887 IDENTIFY DEVICE
c8 00 30 af 05 ae e3 00 00:27:17.797 READ DMA
c8 00 40 e7 ce 4a e4 00 00:27:17.774 READ DMA
c8 00 10 a7 44 b9 e3 00 00:27:17.747 READ DMA
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 8428 6574443
# 2 Short offline Completed: read failure 90% 8428 184053
# 3 Extended offline Completed: read failure 90% 8428 6574443
# 4 Short offline Completed: read failure 90% 8427 184053
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
All errors seem to be same type, some kind of abort signals... Too bad I don't understand anything of this, so I my bag is out of solutions
That "dd_rescue" could work if I had 750G drive, which I dont. I think now my only option is mount the home partition as read only to prevent more damage, and try to copy remaining data in smaller pieces - maybe then the drive won't bork.

[fixed] /var on separate xfs partition

As for topic, I recently moved my /var directory to a separate partition, formatted as xfs, mounted in /mnt. Problem is: after that I experienced slowdowns when using pacman (with high disk activity). I think the problem might be xfs (as I've read pacman is slow on that) or maybe pacman has problem using the link in /var to my mounted partition?
I'd like to know whether there's some obvious problem before trying to change filesystem type (which one, btw?)...
edit: fixed by changing fs type
Last edited by sunriis (2007-09-22 15:30:40)

Hi,
Maybe it would be better to let the logfiles in /private/var/log untouched. You can rotate the logfiles to another disk, without having trouble. See /etc/weekly (daily / monthly) there you can edit the path.
Safer against updates is to create your own files in /etc/yourconfigfiles/ . I use this for rotating my logfiles, because logfiles like secure.log, system.log and asr.log grows very fast and I don't want xGigabyte big logfiles, which are often opened from my system.
Don't touch /etc/fstab , because it is deprecated and maybe this will disappear in next versions.
Write you rotatescripts:
/etc/yourconfigfiles/
daily.my
weekly.my
monthly.my
Edit rotate files:
/etc/daily
/etc/weekly
/etc/monthly
Put to them a line like following:
. /etc/yourconfigfiles/daily.my
if you want to exit manually before the system script does unimportant things, like rotating your rotated logfiles then do an exit after your . /etc/yourconfigfiles/* entry.
hope this helps,
sandor szücs
Mac OS X (10.4.6)

How do I grow an HFS partition on an external USB disk?

I have a USB disk, MBR partitioned, with one ext4 and one HFS+ partition. There is 250GB of unpartitioned space following the HFS+ partition, into which I'd like to grow for Time Machine use.
bash-3.2# diskutil list
-snip-
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *1.0 TB     disk1
   1:                      Linux Backup                  549.1 GB   disk1s1
   2:                  Apple_HFS Mackup                  233.1 GB   disk1s2
-snip-
diskutil refuses to touch the partition, probably because it's MBR ("FDisk") partitioned:
bash-3.2# diskutil resizeVolume disk1s2 limits
Error obtaining resizing information (is this a Mac OS 9 compatible "wrapped" HFS volume?)
How am I going to fix this? Assuming I am unable to copy the contents of my HFS partition to another temporary place.
Thanks

I replaced my MBR with a GPT partition table using gdisk on Linux.
Now diskutil correctly identifies it as GPT:
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk2
   1:       Microsoft Basic Data Backup                  549.1 GB   disk2s1
   2:                  Apple_HFS Mackup                  233.1 GB   disk2s2
however it still refuses to touch it
bash-3.2# diskutil resizeVolume disk2s2 limits
Error obtaining resizing information (is this a Mac OS 9 compatible "wrapped" HFS volume?)

[solved] automatically mount crypted partitions

Hey!
I have an encrypted partition on my extern esata drive. I'd like it is automatically mount it on plugging in the drive.
For that I have found an tutorial (unfortunately in German) about how to do it with udev:
http://michael.stapelberg.de/Artikel/au … setup_udev
But I'm using systemd, so this do not work this way.
Can anybody explain me, how it will be done with systemd? I have to write a systemd unit file, haven't I?
Thank you very much for some advices?
Last edited by smohr (2012-07-27 12:44:23)

I have solved it. Thank you Mr.Elendig!
For running more than one command in your udev rules, it is necessary to execute them in a bash script and connect them with &&.

[SOLVED] Mounting a logical partition

Scenario:
/dev/sda1 primary NTFS windows boot
/dev/sda2 primary NTFS windows home
/dev/sda3 primary ext4 arch /boot
/dev/sda5 primary ext4 arch /
/dev/sda6 logical ext4 arch /home
/dev/sda7 arch swap
Do I perform mount /dev/sda6 /mnt/home as if it were a "normal" partition?
EDIT: I would mount each logical partition as normal.
Last edited by tancrackers (2012-08-29 03:34:46)

shortcut144 wrote:
perbh wrote:
Assume your fat-partition is /dev/sda5 (just as an example)
sudo mount -t vfat /dev/sda5 /some/mount/point
Otherwise - as 's3kt0r' says - you can easily mount a ntfs-partition for read/write as well (using ntfs-3g)
Awesome, thank you. Marked as solved.
Should I put this command in my fstab, or just make a startup command for this?
You could do either ....
If it will _always_ be there and you always want it mounted - put it in /etc/fstab, -or- you could put it in /etc/rc.local (without using 'sudo' of course).
I'm a great believer in using rc.local because you _know_ that everything which might be needed (modules eg.) will be available by then.
If you use /etc/fstab, your entry would be:
/dev/sda5 /mount/point vfat defaults 0 0

Mount params to speed up XFS partition

I have Arch installed on a LVM volume using the XFS file system. I'd like to know what mount params I could add to give it a speed boost. This is what I have so far:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
/dev/fd0 /media/fl auto user,noauto 0 0
/dev/system/root / xfs noatime 0 0
/dev/system/home /home xfs noatime 0 0
/dev/sda5 /boot ext2 noatime 0 0
Now I know that the dump and pass params aren't correct for root. I don't know what to set that to either.
Also how would I hide the physical LVM partition from Windows XP?
Last edited by jordanwb (2008-08-27 22:14:15)

LOL @ the windows-advice!
You know I've been a linux convert since almost two years now (without looking back), and I'm only beginning to scratch the surface of the possibilities with linux, whereas my understanding of the (pre-vista) windows-environment was at a (very) high level. Seriously: this change of mindset (from pro to newbie) was the hardest part of the switch, and only in these last weeks I've been able to contribute to this community with some (easy) answers to problems I had encountered myself.
Glad my windows-knowledge serves someone in here

Solving bootcamp problems after partition

hey guys,
recently i got struck in a bootcamp problem,
this occurred when i installed b-e-t-a of recent os x 'ten' public,
bootcamp icon was not visible in alt-option boot drive selection
panel, but it was visible in startup disk in system preferences,when
i select windows as startup disk a screen saying "no bootable disk
insert and press any key..." used to appear, but later when i found
this Repairing Boot Camp after creating new partitionBy MacTavish_10, July 25, 2014
i solved it to a point in which i can make windows or bootcamp
icon appear in alt-option panel,but when i try to boot into it,
underscore starts blinking continuously but no windows starts booting.
please help....
macbook pro mid 2012, 500gb hd, windows 8.1, os x 9.4 to 10 b-e -t-a

The Apple Bootcamp implementation uses a Hybrid MBR, which has a limit of 4 partitions. OSX utilities use GPT, while Windows uses MBR scheme.
When you installed you-know-what, it removed the Hybrid MBR and put the entire disk into a Protective MBR as your fdisk shows.
Option 1.
1. Backup your Windows partition to an external disk using OSX side. You may not be able to use it again.
2. Please backup your Mavericks side via Time Machine.
3. Please remove you-know-what from your system, and the corresponding GPT partitions.
4. Erase your disk, and re-store from 2 and re-install Windows.
Option 2.
1. Backup your Windows partition to an external disk using Winclone. You may not be able to use it again.
2. Please backup your Mavericks side via Time Machine.
3. Please remove you-know-what from your system, and the corresponding GPT partitions.
4. Erase your disk, and re-store from 2 and re-install Windows via Winclone.
Option 3.
1. Backup your Windows partition to an external disk using OSX side. You may not be able to use it again.
2. Please backup your Mavericks side via Time Machine.
3. Please remove you-know-what from your system, and the corresponding GPT partitions.
4. Create a new Hybrid MBR, with appropriate information and bring up Windows, using Startup Repair, if necessary.
Option 4.
1. Backup your Windows partition to an external disk using OSX side. You may not be able to use it again.
2. Please backup your Mavericks side via Time Machine.
3. Create a new Hybrid MBR (different from Option 3), with appropriate information and bring up Windows, using Startup Repair, if necessary.

[SOLVED] The new 2-partition format vs the older 4-partition format.

Before, the automatic Arch installer would create 4 partitions (boot, swap, root, and home).
That is gone now, and the Beginner's Guide now tells you to create only two partitions (root and home).
Is it safe/secure/crash-proof to have the boot loader in the root partition instead of separately? Am I right to assume that the swap partition was dropped due to memory being abundant nowadays?
Last edited by amadar (2012-12-05 08:55:07)

I'll add that a separate /boot partition has historically risen and fallen in importance. Currently, we're at or near a low point for its importance, but it could be that it's rising again in importance, for a couple of reasons:
On older BIOS-based computers, a 2TiB limit exists in what can be handled by boot loaders under at least some circumstances. With 3TB (~2.7TiB) hard disks now available, creating a separate /boot partition that resides below the 2TiB mark could be important on such disks. Note that I'm unclear about just how common this 2TiB limit is on BIOS boot loaders. Most modern BIOSes are supposed to have much higher limits than that, but my one test under VirtualBox showed that GRUB 2 was unable to boot from a kernel placed above the 2TiB mark. I don't know if that was a VirtualBox problem or a GRUB 2 problem. There's a separate 2TiB limit on the Master Boot Record (MBR) partitioning system, but you can use the GUID Partition Table (GPT) even on bigger disks, so this BIOS boot limitation is independent of the 2TiB MBR limit.
On newer EFI-based computers, some boot loaders (ELILO and the EFI stub loader; but this also means the rEFInd and gummiboot boot managers) require that the kernel be readable by the firmware. Normally this means placing the kernel on the EFI System Partition (ESP), but with the help of existing ext2fs/ext3fs and ReiserFS drivers, the EFI can read kernels from those filesystems. Since most people have moved on to ext4fs, XFS, JFS, or Btrfs for their root (/) filesystems, having /boot on a FAT, ext2fs, ext3fs, or ReiserFS partition gives you added flexibility. Many in the Arch community are simply ensuring that their ESPs are big enough to hold several kernels and mounting them at /boot, which is arguably the simplest way to do it. Having a separate dedicated /boot partition (independent of the ESP) makes sense in some situations, though, such as if you're multi-booting with another Linux distribution. If each one has its own /boot, there's less risk of getting your kernels confused.
Because both over-2TiB disks and EFI are becoming more common, IMHO it's wise to begin re-emphasizing the utility of a separate /boot partition; chances are more people will start wanting or needing it in the near future. There are also some more exotic reasons to want a separate /boot partition, such as if you're using an encrypted root filesystem or GRUB Legacy along with a RAID or LVM setup.

[Solved]Mount windows encrypted partition

Hi,
I have encrypted the Windows 7 system partition fully using truecrypt. In Linux when i try to mount that partition [/dev/sda1] it says "incorrect password of not a truecrypt partition". I am entering the same password which I use while booting into Windows, that is pre-boot password.:/
Last edited by sHyLoCk (2010-06-15 14:12:53)

Do you use the same truecrypt version on windows and linux? also to be able to mount encrypted systems you have to activate a separate checkbox telling that the partition is using system encryption in truecrypts mount dialog (don't know where exactly it is since I didn't use truecrypt in a while), otherwise it will show the error you mentioned.

[SOLVED]root file system partition too small

O.K. so I have this stupid problem:
[rsw@myhost ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 2542076 2320972 92988 97% /
none 94784 0 94784 0% /dev/shm
/dev/sda4 12041420 2406244 9028324 22% /home
/dev/sda1 38888 8336 28544 23% /boot
When I set up my partitions I expected 2.5 gigs to stretch a little farther than this. is there any way to resize it without formating the drive and starting over?
Last edited by rsw (2008-10-16 00:52:02)

rsw wrote:
O.K. so I have this stupid problem:
[rsw@myhost ~]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 2542076 2320972 92988 97% /
none 94784 0 94784 0% /dev/shm
/dev/sda4 12041420 2406244 9028324 22% /home
/dev/sda1 38888 8336 28544 23% /boot
When I set up my partitions I expected 2.5 gigs to stretch a little farther than this. is there any way to resize it without formating the drive and starting over?
Yep, your home partition is directly after the root partition, so what I suggested should work, however, give good consideration to the size of each, considering you don't have another drive (according to df) to use for storage. Personally, I only have 12GB on my home partition (after resizing) and now have 23GB on root.
Here's mine.
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb3 22864180 7438764 14503608 34% /
none 517648 548 517100 1% /dev/shm
/dev/sdb4 11897496 5947088 5470708 53% /home
/dev/sdb1 38888 22534 14346 62% /boot
/dev/sda1 155059036 37878624 109365872 26% /media/thevault
/dev/sdc1 116294120 84739460 25693748 77% /media/music
Last edited by Execute_Method (2008-10-14 12:53:41)

[SOLVED] changes to swap partition

I didn't think my current partition set up through properly on install so I'd like to make some changes. Swap seems to be the obvious candidate as it doesn't involve messing with data. Does this plan sound like it will work or be a disaster?
1. swapoff -a
2. Run cfdisk, delete the swap partition, create an extended partition, format a swap partition in there with the same sdaX designation as it has now, add whatever other partitions are needed to the extended partition. Write the new partition table.
3. swapon -L /dev/sdaX
Do I need to edit fstab afterwards to ensure a later swapon -a doesn't cause problems?
Last edited by tasticorp (2011-11-01 15:51:43)

Sounds like it could work although you will need to edit fstab as sda4 will become the extended partition (and don't forget to add your new partitions to fstab if you want them mounted on boot)
You may want to use UUIDs though (see this wiki article: https://wiki.archlinux.org/index.php/Pe … ce_naming).
mkswap -U <uuid> /dev/sdaX
will give you a swap partition with a UUID of your choice. I found this, in combination with blkid, to be easier than editing fstab

[SOLVED] HELP: Can't partition drives

I'm doing a fresh install of my machine. I was running fakeRAID before and now I want to switch software RAID. But everytime I try to run cfdisk /dev/sda I get an error saying "FATAL ERROR: Bad primary partition 2: Partition ends after end-of-disk. press any key exit cfdisk". How do I remove the old RAID or deactivate it. I turned it of in the BIOS.
Last edited by fettouhi (2011-08-04 06:20:52)

gregor wrote:
fettouhi wrote:my installation is messed now with software raid. I have a pv named /dev/md127 inside my vg0 that I can't remove. I try to
pvremove /dev/md127 but I keep getting the error PV belongs to Volume Group vg0. How do I remove /dev/md127?
i advice an re-install ,it's not worth the trouble...
Yep, did that an usd the installer to delete all lvm and raid. Then I reooted and everything was back to normal.

[SOLVED] Please verify: swap partition needed for dm-crypt/LUKS??

Hi,
Can anyone confirm whether or not the following is accurate (from http://wiki.archlinux.org/index.php/Sys … artitions)
There are 3 required partitions for any encrypted system:
- The root file system: /
- The initial boot partition: /boot
- The swap partition: swap
Do I need a swap partition if I encrypt? I can't seem to find reference to swap being mandatory anywhere else.
Last edited by jwhendy (2010-10-12 13:27:12)

You don't need swap. The minimal required setup is having two partitions: boot and root, where /boot must not be encrypted and / can be encrypted.
Last edited by stfn (2010-10-12 12:45:22)

[Solved]Grow an XFS partition

Similar Messages

Maybe you are looking for