Well, the command (thanks, guys!) shows a sufficiently large disk (see below). So it's simply a resizing issue?
# Disk /dev/sdb: 250.0 GB, 250059350016 bytes # 255 heads, 63 sectors/track, 30401 cylinders # Units = cylinders of 16065 * 512 = 8225280 bytes # Disk identifier: 0x0f800000 # # Device Boot Start End Blocks Id System # /dev/sdb1 1 30401 244196001 83 Linux # # Disk /dev/sdb1: 250.0 GB, 250056705024 bytes # 255 heads, 63 sectors/track, 30400 cylinders # Units = cylinders of 16065 * 512 = 8225280 bytes # Disk identifier: 0x00000000 # # Disk /dev/sdb1 doesn't contain a valid partition table
How/when was it formatted? I know there are drive size issues under XP and such. Linux should work with a drive at its actual size after boot and detection by the running kernel, unless the size cap jumper is set on the drive. ;)
Jon.
On Jan 14, 2008 4:32 AM, Greg Brooks [email protected] wrote:
Well, the command (thanks, guys!) shows a sufficiently large disk (see below). So it's simply a resizing issue?
# Disk /dev/sdb: 250.0 GB, 250059350016 bytes # 255 heads, 63 sectors/track, 30401 cylinders # Units = cylinders of 16065 * 512 = 8225280 bytes # Disk identifier: 0x0f800000 # # Device Boot Start End Blocks Id System # /dev/sdb1 1 30401 244196001 83 Linux # # Disk /dev/sdb1: 250.0 GB, 250056705024 bytes # 255 heads, 63 sectors/track, 30400 cylinders # Units = cylinders of 16065 * 512 = 8225280 bytes # Disk identifier: 0x00000000 # # Disk /dev/sdb1 doesn't contain a valid partition table
Kclug mailing list [email protected] http://kclug.org/mailman/listinfo/kclug
On Monday 14 January 2008 04:32, Greg Brooks wrote:
Well, the command (thanks, guys!) shows a sufficiently large disk (see below). So it's simply a resizing issue?
# Disk /dev/sdb: 250.0 GB, 250059350016 bytes
^^^^^^^^^ The total capacity of the drive agrees with your expectation so thats good.
# 255 heads, 63 sectors/track, 30401 cylinders # Units = cylinders of 16065 * 512 = 8225280 bytes # Disk identifier: 0x0f800000 # # Device Boot Start End Blocks Id System # /dev/sdb1 1 30401 244196001 83 Linux
^^^^^^^^^^ The only existing partion is 244196001 blocks X 512 bytes per block (sector) = 125,028,352,512 bytes, which agrees with your du results and is good too, and indicates about half the drive has been left unpartitioned.
Short answer: probably yes (see last below). You could use the tools that Bryan mentioned. Back it up first for insurance :). Since you have quite a bit of free space on / you could use something like "tar -czvpf /tmp/media.tgz /media". This would archive your /media to /tmp/media.tgz. The /tmp/media.tgz could just be deleted after you're satisfied that the resize went okay.
Or, just create another partition in the unused space and mount it somewhere convenient. The fdisk tool can do that also. Or, cfdisk is more friendly.
The reason I said "probably" above is that I'm not sure what device your "/dev/mapper/plattsburg-root" actually is and I'd want to make sure that there is no conflict with /dev/sdb through LVM or RAID or something.
Finally, sorry if any of this was like teaching my grandfather to suck eggs :).
Good luck. -Shawn
Hi,
On Mon, Jan 14, 2008 at 04:32:03AM -0600, Greg Brooks wrote:
Well, the command (thanks, guys!) shows a sufficiently large disk (see below). So it's simply a resizing issue?
# Disk /dev/sdb: 250.0 GB, 250059350016 bytes # 255 heads, 63 sectors/track, 30401 cylinders # Units = cylinders of 16065 * 512 = 8225280 bytes # Disk identifier: 0x0f800000 # # Device Boot Start End Blocks Id System # /dev/sdb1 1 30401 244196001 83 Linux # # Disk /dev/sdb1: 250.0 GB, 250056705024 bytes # 255 heads, 63 sectors/track, 30400 cylinders # Units = cylinders of 16065 * 512 = 8225280 bytes # Disk identifier: 0x00000000 # # Disk /dev/sdb1 doesn't contain a valid partition table
I share Shawn's concern about your "/dev/mapper/plattsburg-root". This should be logical volume "root" in volume group "plattsburg". This SHOULD be somewhere on /dev/sda. You can verify this with the "pvs" command and "fdisk -l /dev/sda" should show a partition with "Linux LVM" in the last column.
After you have backed up all your data as many ways as you can the command to expand your filesystem to fill the partition is either
resize2fs -p /dev/sdb1 or ext2online -v /dev/sdb1
This assumes you are using an ext2/ext3 filesystem. I haven't seen any indication of your filesystem type. The ext2online command only allows you to enlarge the filesystem but it will work on a mounted filesystem. The resize2fs command only works on un-mounted filesystems but will allow you to shrink the filesystem, too. The "-p" and "-v" flags just specify verbose output. Since this operation can take a while it is nice to know your machine is still alive.
Before you take this step wouldn't you like to know what caused your machine to be in this state? The answer could save you lots of work.
-
Greg Brooks -
Jon Pruente -
Shawn C. Powell -
Uncle Jim