Displaying 6 results from an estimated 6 matches for "olddisk".
2007 Sep 07
2
LVM problem
...e CentOS 5.0 which use an old hard disk. And recently I found
there are some bad sector on it ... I try to backup my data to other
CentOS 5.0 box ....
What I did is. I remove the old HD (with bad sector) and install it as
a slave IDE on a working CentOS 5.0 ... I try to mount the old HD as
/mnt/oldDisk but since it's a LVM, the "mount -t ext3" doesn't work.
I'm new to LVM ... could someone help me on this.
Also, there is a problem I found. Both HD have the
same VG called /dev/VolGroup00 ...
server:[root]/dev> pvscan
PV /dev/hdb2 VG VolGroup00 lvm2 [76.22 GB / 0...
2006 Mar 10
2
installing/updating R packages: apt-get vs. install.packages() and .libPaths()
I recently had to rebuild my entire debian system to correct some severe
dependency
conflicts and security issues. I installed a new harddisk, linux kernel
and started from
scratch, keeping my old disk mounted as /olddisk. In the process I
switched from unstable
to stable distros as recommended by a local sysadmin to avoid such
problems in the future.
Now I want to be able to install and update R and R packages with ease
and with minimal
confusion about different versions in different libraries, so that I can...
2008 Dec 17
11
zpool detach on non-mirrored drive
I''m using zfs not to have access to a fail-safe backed up system, but to easily manage my file system. I would like to be able to, as I buy new harddrives, just to be able to replace the old ones. I''m very environmentally concious, so I don''t want to leave old drives in there to consume power as they''ve already been replaced by larger ones. However, ZFS
2017 Mar 31
6
[PATCH 0/3] Fix some quoting issues.
Fix some quoting issues by introducing Unicode quotes.
Note this intentionally only affects end-user messages and documentation.
Rich.
2012 May 07
53
kernel 3.3.4 damages filesystem (?)
Hallo,
"never change a running system" ...
For some months I run btrfs unter kernel 3.2.5 and 3.2.9, without
problems.
Yesterday I compiled kernel 3.3.4, and this morning I started the
machine with this kernel. There may be some ugly problems.
Copying something into the btrfs "directory" worked well for some files,
and then I got error messages (I''ve not
2015 Jun 14
2
[PATCH] pod: Use F<> for filenames instead of C<>.
...t a typo.
-This should copy C</home> from the guest into the current directory.
+This should copy F</home> from the guest into the current directory.
=head2 Run virt-df.
@@ -349,7 +349,7 @@ Using L<virt-sparsify(1)>, make a disk image more sparse:
virt-sparsify /path/to/olddisk.img newdisk.img
-Is C<newdisk.img> still bootable after sparsifying? Is the resulting
+Is F<newdisk.img> still bootable after sparsifying? Is the resulting
disk image smaller (use C<du> to check)?
=head2 B<*> "sysprep" a B<shut off> Linux guest.
diff...