My root filesystems flooded so I'm trying to move it to another (bigger) partition but I'm not sure of the best method. I just tried to use "dd if=/dev/sda1 of=/dev/sda6" to copy it but all that did was give me a brand new partition with no freespace available presumably because the filesystem is smaller than the partition. Is it possible to make the filesystem bigger?
View 8 RepliesI've setup a filesystem on a RAID 0+1 and am looking at moving root filesystem from a single disk to the new one. I could not install CentOS on mirrored filesystem as the RAID card did not have a pre-built driver for CentOS 5.3, so I had to compile the driver after installing the system.What I'm going to do now is:
1. Mount the new mirrored filesystem under /root1
2. use find | cpio to copy everything from the existing / to /root1
3. use grub to create a boot record on /root1
4. edit /root1/etc/fstab to point / to the new disk
5. reboot the system and keep my fingers crossed
Is this the way to go? Am I missing anything?
Ive setup a filesystem on a RAID 0+1 and am looking at moving root filesystem from a single disk to the new one. I could not install CentOS on mirrored filesystem as the RAID card did not have a pre-built driver for CentOS 5.3, so I had to compile the driver after installing the system.
What Im going to do now is:
1.Mount the new mirrored filesystem under /root1
2.use find | cpio to copy everything from the existing / to /root1
3.use grub to create a boot record on /root1
4.edit /root1/etc/fstab to point / to the new disk
5. reboot the system and keep my fingers crossed
Is this the way to go? Am I missing anything?
Have been running 11.1 on a generic notebook (eRacks) just fine until a few days ago when CUPS couldn't be reached. Rather than futz more with 11.1, I decided to install 11.2 (which has been on my desktop). Using the same CD, which continues to check ok, the install has failed many times at about the same point: 87% through "copying root filesystem" in yast2.
Specs: Intel P4 2.4 GHz, 1.5 GB RAM, ATI radeon PV250Lf
The HD was partitioned into /, swap, /home, and an extended partition of /opt, /var, /usr. Only / was ext4 and the rest were ext3. Tried various options:
* no apic
* no acpi
* "noapic acpi=off" entered manually
* Vesa instead of 1024x768
Each time had to edit partition table to mount the extended partitions. Always formatted /. At first didn't format the extended patitions, later formated all but /home. Then set yast2 to format / as ext3, to match the other partitions. In the sysinfo page the / partition is now shown as /mnt containing 723.6 MB out of 7 GB, still formatted as ext4. On rescan by yast2 partition manager, / shows as ext3. The install halts every time with an error while "copying root filesystem." Tried booting from the CD direct to install and to the Live OS followed by install--same result. So, hours later, went back to 11.1--which installed in minutes.
I was just copying a large (50GB) file from one mounted partition to another mounted partition (a USB drive), but before the operation completed, my root filesystem, on a separate partition, filled up.Because it filled up I also couldn't get past the login when I rebooted. I think this is because there is no room to load temporary files. I'm expanding the root partition to temporarily fix this. how can I avoid my root file system filling up when copying a massive file between mounted partitions? the file is being cached in root during the transfer.
View 3 Replies View RelatedI thought this might interest someone out there:[URL].. I used SD cards with MBR formatted as ext2 for backup. After I read these articles, I reformatted my cards with GUID Partition Table and ext4 format. Now I make my backup in half the time!
View 2 Replies View RelatedIs there a way where I can take like 50GB from my home folder (I have 375 avail., but using only 22GB) and put it to the root partition? Twice now my system has almost ran out of space on root, so luckly I was able to clear out old stuff so I don't have login issues after finding the hardway the first round lol. I just want to make sure I can login with out being forced back out because root don't have space to let me login.
View 11 Replies View RelatedI made a mistake in Gnome Disk utility tool. Instead of changing the options for a USB key, I changed the options of the root partition.
In Initial state, automatic options were desactivated. I just activated them. And after desactivacting them, I realized my mistake and switched back to "non automatic options".
By doing this, I suppose that defaults values were used since now, the system starts in command line mode and no more in graphic interface mode.
When I try the "startx" command, I get a "read-only" error.
With the command "sudo mount -o rw,remount /" the graphic interface is started.
Below is the configuration of the partition under the gnome disk utility tool :
"Mount at startup" is checked
"Show in user inteface" and "Require additional authorization to mount" are unchecked
Mount options : nosuid,nodev,nofail,x-gvfs-show
Mount point : /mnt/eb11d4d6-75db-XXXx-XXXx
Identify as : /dev/disk/by-uuid/eb11d4d6-75db-XXXx-XXXx
Filesystem type : auto
I do not want to change anything that could leat to a critical error. So what do you think I should do ?
I have the partition like below. Now i want merge the /home partition into /dev/sda1 partition .
[Code]...
/dev/sda 74.53gb. Here are two partitions sda1 243.13mib (33.92 used), flags 'boot', and sda2 74.29gb flags 'lvm'. Filesystem for sda1 is ext2, for sda2 'unknown' and it gives a warning "Unable to detect filesystem". At last shut down I also notices red text that said something about logical volumes and lvm.
[Code]...
I want to move my / partition to the end of my drive (sda). To do this with gparted, I have to unmount it, but I'm not comfortable with the idea of unmounting root partition... Should I do it from a live cd? More important : is the operation safe?
View 5 Replies View RelatedBecause I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here:[URL]31So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. But now when I try to boot, I get my old grub menu but after selecting my kernel version it hangs
View 15 Replies View Relatedi want to know that if i install linux on to my pc with SWAP/ boot as partition and after that i want to convert them to LVM2 type configuration .how can i do that.i want to create a system having logical volumes from that system without reinstalling these partitions should convert into two LV's
LV 0 for root
LV 1 for swap
both in one volume group.
I need a reliable+fast filesystem for root and boot partition. It will be used in Debian x64. So far I only tried ext3 and ext4. What do you reccommend? (this has been probably asked many times, but I need updated information)
View 2 Replies View RelatedI'm running Debian Wheezy on a Dell XPS M1530 laptop, 64-bit.
I'm having a boot problem after moving my /usr directory out of the root partition and into its own partition.
I followed the "easy way" here: [url]
Basically, I moved the contents of /usr to a new partition -- renamed /usr in root to /oldusr -- and edited fstab and tried to reboot... but the boot process wasn't able to find the new /usr.
After using /dev/sda7 in fstab (to no success) I ran blkid to find the UUID and used that (again, to no success).
My fstab is below:
For what it's worth, grub is also looking different -- none of the debian backgrounds that were there previously remain. While it lists the same kernels to boot into the boot (as described above) fails.
I just got a new hard drive and figured I might as well do an installation of Squeeze (and was previously using Lenny). That went fine, and then I decided that I should copy over my old Lenny installation to the new disk -- mostly to have a working backup without bothering to do a new installation on a partition of the new drive. My partition scheme was a smaller /boot partition and then a much larger / partition with everything else standard (and a much larger /data partition rather than storing everything under /home). So I copied /boot over to a new partition on the new disk, and the same with /. That was done from the Squeeze installation, so the Lenny install wasn't active at the time. I modified all the appropriate entries in /etc/fstab to use UUIDs rather than partition numbers and ran an update-grub.
It detected everything on the old and new disks without a problem. When I went to try and boot up the transferred Lenny installation, it hung on trying to activate the root file system (I've forgotten the exact messaging). Not entirely unexpected, mind you. I went and took a look at the grub.cfg file. It does list that the transferred Lenny is on partition sda8 (correct), it has the correct uuid for the boot partition... but it seems to be setting the root incorrectly. Specifically, the root is still set for the old disk (though in its new position of hd1 instead of hd0), and the "linux" line sets a root for the old device. Or more specifically, this is the menu entry I get, with a few // comments.
menuentry "Debian GNU/Linux, kernel 2.6.26-2-amd64 (on /dev/sda8)" {
insmod part_msdos
insmod ext2
set root='(hd1,msdos2)' // <------ This position is the *current* location of my old Lenny disk/partition
search --no-floppy --fs-uuid --set [the correct /boot UUID]
linux /vmlinuz-2.6.26-2-amd64 root=/dev/sda5 ro vga=795 // <----- that root=/dev/sda5 line is what it was on the old device.
initrd /initrd.img-2.6.26-2-amd64 }
The odd thing there is that it sets the root according to the *current* position of the old install disk (maybe some trickery with detecting the correct UUID before setting the root), but the "linux" line refers to the *old* partition. The two lines will never match up no matter what. Now if I edit grub.cfg manually, I can make it boot (and run) normally, as I've verified. For example, I made a couple manual changes to do this:
menuentry "Debian GNU/Linux, kernel 2.6.26-2-amd64 (on /dev/sda8)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)' // <----------- First hard drive, partition sda3 is where I put /boot
search --no-floppy --fs-uuid --set [the correct /boot UUID]
linux /vmlinuz-2.6.26-2-amd64 root=UUID=[the correct / UUID] ro vga=795 // <--- Changed it to the UUID here; could be /dev/sda8 instead
initrd /initrd.img-2.6.26-2-amd64 }
And that works perfectly, the installation works just fine. Of course, the problem is that those changes will/would be lost every time I run an update-grub. So my question, in a nutshell, is how can I configure things so that update-grub sets things properly to the new devices? Or in other words, where in the copied installation are the variables I need to change? I did note one thing odd -- the existence of a vga=795 line. For the new Squeeze installation, I'm using gfxpayload and there's no vga=anything line anywhere. My old installation, of course, had its own grub installation where I did use vga=795 to set the console resolution properly.
So my first guess was that update-grub (for Grub2) was pulling config information out of the Lenny /boot/grub folder (grub legacy). Unfortunately I tried several changes there and it made no difference. Then I deleted the entire /boot/grub folder entirely from the copied Lenny installation and ran update-grub again (the Squeeze grub version). It changed absolutely nothing. That's very confusing for me, since I have no clue where it could be getting vga=795 from, *except* the now-deleted Lenny /boot/grub folder. Where in the copied Lenny installation, I can change something to make it so that update-grub picks up the correct information?
I have an older system that has been running testing for about 4 years. Originally I was running testing for several packages that were not yet available in stable. However, now that this system has a more crucial role in the network I have considered moving it to stable in hopes that it I can gain some insurance on it's uptime. It is important to note that I have never had a problem with the testing distribution and would be quite content to continue running it; I do want to know my options though.
I have not yet updated the system since the stable release of squeeze, I am considering to change my sources from testing to stable and just let apt take care of the rest. Anyone have any experience with such a thing? After searching Google I have found some solutions to force a downgrade, but that is really not what needs to be done here. I suppose I should have switched my sources to squeeze some time ago and this probably would have worked itself out.
A similar question is what happens a couple of years from now when another release happens. Have you had good luck updating from old stable to stable? I've run testing on several machines now for several years and have went through freezes and dist-upgrades several times with no major problems at all. Will I see the same stability if I move to the stable distribution?
I ping my router. If I keep my mouse moving (or i'm typing) I get a 5ms ping.If I stop typing/moving my mouse, it times out.
- I disabled NetworkManager for the inteface eth0 but it doesn't solve the problem.
- I'm having the same problem using a Ubuntu 15.01 bootable image
- I'm having the same problem usign an Ethernet PCI Adapter
- I'm having the same problem usign a Wifi PCI Adapter
lsb_release -da
Code: Select allDistributor ID: Debian
Description: Debian GNU/Linux testing (stretch)
Release: testing
Codename: stretch
[code]....
I want to move my old system to a new drive. Currently I have Debian installed with following configuration:
I have an encrypted system where everything is encrypted except /boot. Currently I've /boot and / installed on a 16 GB mSata SSD and /home on a regulard HDD. I've got a 500GB SSD for Christmas and want to move the whole system to the new SSD.
I just wanted to ask if I've got the process required to to this down:
1. backup root-directory (/) without and /boot /home using tar keeping file-permissions and owners to ext. hard drive
2. backup /boot and /home separately using the same method
2. replace HDD with SSD remove mSATA SDD.
3. boot via live-usb
4. create appropriate volume groups, partitions, setup encryption etc.
5. extract backups to appropriate partitions
6. chroot to old /.
7. edit fstab
8. reinstall grub
9. create new init ram img.
I'm pretty sure I've got steps 1.-6. down but I'm very shaky on what to do next.
I have switched recently from Ubuntu to Debian and overall I am enjoying it. However I was just wondering, does Debian, like Ubuntu check the filesystem at boot periodically or if damaged, because it is doing neither in my case? How do I get it to do this
View 6 Replies View RelatedMy laptop has a dual boot Debian + Ubuntu installation.
In particular I am using Debian 8.0 with stock kernel 3.16.0-4 (or equally 4.1.10 custom compiled, I tested it and it does not make any difference for the subject of this post).
Ubuntu is 14.10, with stock kernel 3.19.0-15.
In both installations I have nvidia nouveau drivers and intel integrated graphics drivers installed and loaded. This is the default for both installations.
In both installations I have xorg automatically configured (no xorg.conf file present in /etc/X11). In both systems the content of /usr/share/X11/xorg.conf.d is the same for what moitors are concerned (differences in mice and trackpad entries).
Unfortunately, the video configuration in Ubuntu 14.10 works out of the box. In particular I can plug in an external monitor/projector and it will fire-up the nvidia card (nouveau drivers) to power that monitor.
Debian 8.0 on the other hand does not even detect the external monitor.
I don't know where to start to solve the problems.
The hardware is as follows: the laptop (lenovo W530) features both an Intel integrated graphics card and an Nvidia K1000M. The VGA port is connected only to the Nvidia card (this is according to my online research, as I don't know how to check this).
This my scenery:
1 pc windows 7.
1 pc linux debian jessie.
From jessie, mount a share folder in windows 7, in this way: mount -t cifs //windows7/sharefolder /mnt/windows7 -o user=pychi,password=mypass,uid=pychi,gid=pychi
And work fine, the user pychi and root, copy to windows share folder perfect and fast, but the big problem is:
when i copy a big folder, example 40 gb, after 30% or similar, stop the copy, and this is a list of different errors:
- It's not possible change file proprietary on destiny.
- not enough space
- can't fix attributes, date, time, proprietary, group.
I installed Debain Lenny as a dual boot with ubuntu 10.10. Chose not to install Grub legacy in the mbr or in any partition because I thought grub2 could handle it. All went well, updated grub2 in ubuntu and it found Debian, but when I try to boot into Debain it hangs at - waiting for root filesystem. I've searched, but can't fathom why this is happening, much less how to fix it without just reinstalling it.
View 9 Replies View RelatedBecause I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here: [url]
So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. I updated UUIDs in grub's configuration as suggested in this thread:[url]
But now it fails to boot with the following error:
Code:
I checked the filesystem on this partition and its fine. I tried to recreate the initramfs from Knoppix:
Code:
But it didn't change anything.
How can I either fix it or install a different kernel on this drive so I could boot into it and re-install my default kernels?
I have a system in which I want to have /etc in a read-only filesystem. What can I do with mtab? It gets write at /etc/init.d/mountall.sh (that is, /etc/rcS/S35mountall.sh)
View 3 Replies View RelatedWhen I try to boot to OpenSUSE I get the following error during boot-up: unknown filesystem type 'reiserfs' could not mount root filesystem - exiting to /bin/sh$
This only started happening quite recently - before this I could boot to Linux quite happily.
[code]...
Well, let's suppose the file is very large, say 10 GB of disk space it is consuming. We perform the above steps. Which operations: cp (copying) or mv (moving) will be more efficient and less time consuming? The inode number 1566966 which was pointing to the file in my home directory is now pointing to the same file which is in some other directry, i.e. /tmp/. Isn't the inode value getting modified in some ways to point to the correct location / beginning of the data block on the hard disk? If the the physical location of the data would not change then we would not be able to free up space in our home directory. That means the mv operation is copying the file into some other location. In other words, it is also performing the cp operation first and then deleting the file from its original location, my home directory in the case above. However, when a file is copied it's inode value changes. But the mv operation is retaining the same indoe value. So, how to determine which operation - mv or cp - is more CPU-friendly or more efficient in terms of performance and time taken to perform the action?
whenever I copy (or move) files from one place on my hd to another One or two of them dont copy, and I get an error similar to " There was an error copying the file into [location]. Show more details> Error splicing file: Input/output error. The file is always an .avi file and always between 600MB and 1.4GB in size, how can I fix this problem?
View 9 Replies View RelatedI've upgraded my squeeze box to linux kernel 2.6.32-5. But it shows mounting "here is the uuid of / " on /root failed: Device or resource busy while booting.Here is the menuentry of linux kernel 2.6.32-5.
[code]....
A few days ago I upgraded my debian sid system, and since then systemd does a filesystem check on every boot which takes over two minutes, disobeying the existing settings I had. How can I set systemd to do a filesystem check only once every a set number of mounts, like I had set up before the upgrade?
View 5 Replies View Related