FSTAB Missing... Can't boot in Fedora Core

So I started this job around 2 months ago and even though this Software Development company had been around for 7 years they have never had someone hired on whose main duty was System/Network Administration & Network Security. So needless to say having a couple different people randomly doing things when they need to be done creates a huge unorganized mess after 7 years.

So besides trying to move into a network & organize everything as well as learn what's going on I'm having to deal with things that just quit working for no apparent reason except probably it was setup by someone who doesn't know what they're doing.

So anyways, we have this server that's running our wiki database, our bot controller, as well as some other random things. But last week most of the services on it went down so after some looking around I found that it had run out of space. It was using LVM file system and to tell you how long ago this was setup it was running Fedora Core 2 and was on a 160GB Sata 1.5 hard drive. Holy crap... It's also in some ancient dell tower which was sideways sitting on top of a switch that was mounted in the rack. ohhh me I have too much work to do here.

So anyways I cloned the disk over to a 1.5 TB drive and attempted to extend the Volume Group... I asked around on here and the directions I got seemed to match up with ones on other websites. I did the commands and I think I must have forgot something that has to do with fstab because now I'm getting this message upon boot...

So this is obviously on the new drive... (I accidentally left the old one I had cloned it too plugged into SATA and accidentally ran some commands that well... Also ruined the VolGroups. I'm awesome I know)

So /dev/sda3 was made by me following the directions I got. I created it with the rest of the unpartitioned space. Here are the commands I did... (Well pretty sure I did... maybe I left one of them out and that's why everything is messed up)

This is the output on the guys computer... So he's doing sdb and I had sda etc.. You get the drift.

Step 1: Create a new physical volume to take up all that lovely free space

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks

You can just accept the default values like I did, thats why it shows no reply to some of the questions, I just pressed enter and it will make a new partition that takes up all the space.

Also... now since I accidentally jacked my original install I still have it on a 1.5TB drive but the only issue is I told clonezilla to make the filesystem use the rest of the free space for the partition and now /dev/sda2 on that drive takes up all the space, but it's still saying it has 0 disk space. So I need to either make sda2 see all the rest of the space or extract all the information and somehow get it working properly.

Thanks in advance... This topic seems to always take a lot of work for both the person answering and myself. Lol

My guess based on the age and the size of the drive you are using that it is the issue.
you made the /boot partion the linux (83) type too big.

My suggestion would be to place the old drive back and boot into singleuser and cleanup the system to free up some space. My guess is that there is a huge log file that was never setup for logrotate and it grew too much.

Additional option is to add a drive if possible and then use find /path | cpio -pdvmu /mnt where /mnt is a new partition that will be mounted over the /path i.e.
mv /path /path.old mkdir /path, mount /dev/sdbx /path.

Well no... I know my post was hella long so it's easy to miss some of the details.

The original 160GB drive I accidentally ruined... The only working copy I have left is on a 1.5TB disk and supposedly sda2 is taking up around 900GB of space for it's partition but inside the file system it still shows it in it's 140 something GB form.

How do I make it realize that it has all that extra space? It's not unused anymore according to any partition viewer, but it's not able to be written to because I didn't set it up right with LVM I think.

Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.

Thanks so much for your help here arnold... Here's the information you asked for. As it looks like to me all the extra like 1.3TB of data are apart of one of the partitions but the LogVol00 isn't using it or something... Not 100% on it. My life will seriously be 10000 times easier if this can be figured out so I'm hoping it's fixable.

Just an update... I no longer have the FSTAB missing issue where I can't find VolGroups anymore.

I still have that issue on my original 160GB drive but I was able to get the OS back up on my 1.5 TB drive but the partition is still messed up. Still has the same partition size and I need to expand it out to have more free space. if at all possible.

Thanks again, just wanted to make sure that fact was clear. So it's not 100% necessary anymore to know how to fix the FSTAB. I'm going to be 100x more careful in the future with what I run and making sure I have a viable backup of something before making such dangerous changes to it.

I don't think I ever ran any of those commands on this drive... Wow. I thought my clone I had now had been taken after those commands were run.

Dude, I'm so sorry for giving you false information. I just realized what the story is now. I had so many different clones of it on different hard drives, trying to expand the file system that I got lost in my disorganization.

So if you're kind enough to hang with me still... I understand if not. But if you do here's the actual story as of now. The stuff I posted above was done to my hard drive that is cooked now... Also the sdb2 was the command the guy who was telling me how to do it used. My drive is and has always been sda except for in that other computer because it was using a different sata driver.

So the story as of now.

Had the 160GB drive that filled with disk space. Cloned it with clonezilla onto different drives trying to get clonezilla to automatically resize the partitions which obviously didn't work. So the drive it's on now was done by using clonezilla and telling clonezilla to fill the partition to the extent of the drive free space.

So even though clonezilla set the partition to take up the rest of drive obviously the filesystem knows nothing of this. it only knows of the original 149GB partition that it had on the previous drive.

So I will repost all the commands that you asked for above but this time getting the info from the drive when it's in the correct computer, with it's real names, and real info at the moment. And remember.... None of the vgcreate, vgextend commands have been run at all. So is there ANY way at all to make it be able to use any of that space?

I feel really really stupid by the way.. I can't believe I made that mistake and led you on this wild goose chase. I'm really sorry.

Ok so now that I realize I haven't actually told LVM to add the extra drive space in there like I thought and it was just clonezilla which added the extra data onto it. So technically can't we just take the data back from the partition or extend the filesystem onto that space if we know what block or cylinder the current LV's end on? Or am I completely off base.

Once again I'm sorry for the mis-information and hope you can still help me out.

So technically I should be able to take the blocks or something right? because the cylinders are off. It says it's using almost all the cylinders but it's obviously not seeing the data. I dunno this is kinda confusing me. I'm getting better but honestly haven't been actually digging into the linux file system for long.

The most I ever did before this job really was install Ubuntu or the likes letting it partition everything for me then install all the programs I needed for my ethical hacking & network security courses.

But i'm really starting to like using Linux but the beginning part of the learning curve is steep. All though I'm finding that once I figure out how to do something, or get help from someone the other things become a lot easier. It's just learning the basics that take a bit.

run pvdisplay
I would suggest you copy the data back to the 160GB drive. Just to be sure what you try after does not leave you without your data.

Then you would need to use pvresize to enlarge the space using the -setphysicalvolumesize 300G /dev/sda2
then use the pvresize http://linux.die.net/man/8/pvresize
one the pvdisplay reflects the size of the volume as larger, you would then use the vgextend and the lvextend.

This article shows how to use a free utility called 'Parkdale' to easily test the performance and benchmark any Hard Drive(s) installed in your computer. We also look at RAM Disks and their speed comparisons.

Learn how to get help with Linux/Unix bash shell commands.
Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…

To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention.
Multiple USB devices need t…