Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When setting up Fedora Core 6, I mistakenly decided to continue to use this extra 30GB drive I had.
Well, the system randomly shutdown a couple of times and then I was getting the SMART error for the drive at bootup. This is my dev/hdb drive.
My hda drive has a boot partition (hda1) and a second partition (hda2) that was dedicated to the LVM Volume.
So, I went out and bought a new Seagate drive today and partitioned it as hdc1 (bootable and ultimately to replace my primary drive as well since it is getting old, too) and a second very large hdc2 partition. I then ran the commands to add it to the LVM volume. Up until this point everything was going fine.
I then used the LVM gui to try and move the data off of hdb1 and the system suddenly froze and ultimately had to be rebooted.
Now when I boot up I'm getting the following at the LVM initialization phase:
"...error creating dirty log..."
"...reload ioctl failed: Invalid Argument..."
Then a message saying that two logical volumes in "VolGroup00" active.
"...hash received Sigsegv Backtrace..."
Then some HEX codes
Then, "Kernel Panic - not syncing: Attempted to kill init"
So....My question is...Is my installation toast and should I just pull out the two old drive, leave the new Seagate 300GB in there and start from scratch? I'm just not sure how much I can get from the drives as it is.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,605
Rep:
I gather you did no LVM snapshots? Pity...
I am no expert here, but you might want to install on your new HD with both old ones disconnected. When you have a running system you might reconnect and try to rebuild step by step, starting with fdisk and the LVM tools. Good luck...
Though make sure your home / root directory is large enough. Then you can reload the contents back without extraneous material from a /dev/hdc partition (in contrast to a file on hdc) by just reloading the entire files and nothing else (else you'd need to use exactly the same parameters with dd).
If money is of no or little concern, get new hda / hdb.
Alternatively you might use a live CD to clone your dying drive to your present hdc and then switch the drives on the bus.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,605
Rep:
Well, you'd boot from the live CD.
Details depend on the actual partitioning of hdc.
<edit> See post below. What do you want to do exactly? </edit>
Open a console and
Code:
mkdir /storage
mount -t auto -o,remount,rw /dev/hdc1 /storage
{please look for the correct syntax in man mount}
dd if=/dev/hdb of=/storage/hdb-in-a-file
That should be it. As long as you don't touch (the data) on hda and hdb nothing untoward can happen.
Last edited by JZL240I-U; 01-10-2007 at 06:32 AM.
Reason: changed sequence of commands
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,605
Rep:
Attention please, the above post is incomplete.
If you want to interchange hdb and hdc you must first create a partition (slightly) greater than 30 GB (e.g. 32 GB). For simplicity I assume here, that you have just one partition on hdb.
Then you create more partitions to your liking on hdc to store images in files there. Note down the geometry very very consciously what you do, just in case (you might want to re-create it with fdisk later). Make a backup of the MBR
If everything looks normal you can reclaim the rest of hdc with fdisk, thereby obliterating your earlier backups. Do them again to be on the secure side .
Well, you'd boot from the live CD.
Details depend on the actual partitioning of hdc.
<edit> See post below. What do you want to do exactly? </edit>
Open a console and
Code:
mount -t auto -o,remount,rw /dev/hdc1 /storage
{please look for the correct syntax in man mount}
mkdir /storage
dd if=/dev/hdb of=/storage/hdb-in-a-file
That should be it. As long as you don't touch (the data) on hda and hdb nothing untoward can happen.
Well, replacing hdb (which only has one partition) is the critical issue. Ideally I'd like to replace both hda and hdb with hdc. However, so far I haven't found a way to do it...So, replacing hdb with hdc is sufficient at this point. I guess I'll see what happens after following yours and the other instructions.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,605
Rep:
Again attention: I changed the sequence of commands in post #6.
Okay, then try it as suggested in #7. When all is well you should be able to create a partition behind [ex-hdb on hdc] and move the physical volume from hda there.
Last you could again exchange ex-hdc into the first master position and install GRUB in the MBR.
Please keep us notified how your project advances .
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,605
Rep:
Huh? What was the error message here? You might also have a look at the man pages whether "dd" has a verbose switch ("-v") to get more information -- or use "hdparm" to disable DMA to slow down the data transfer...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.