I am building a 10.04.1LTS server. I am putting the /root filesystem into a Software RAID1 partition. I want to keeo my /boot partition outside of RAID.Is there a way to have a boot partition on both sda and sdb so if one drive fails the second boot partition will work away - or should this be kept in with RAID also.
View 6 Replies
I have minor problem with upgrading a hard drive. I am running an old pentium lll with two hard drives. On the first hard drive I have two partitions of around 90GB each. On the first partition is installed winXP and on the second partition I have Suse 10.3, both booted by grub and living happily side by side. My second hard drive (which is formatted for windows is only 4GB.
My problem arises when I try to replace the 4GB with a 80Gb hard drive. When I disconnect the 4GB drive the system fails to boot up and complains with error 21.
I have an Ubuntu 9.10/64 Server configured with LVM in a 1Tb sata disk in my home server. For a simple server, LVM adds complexity if you need to recover your system, so I decided to migrate from LVM to normal partitions. I have another 1Tb disk to copy my system disk. In the backup disk, i have created same size partitions and trasfered files from /boot and root volumes with rsync, presenving perms etc... and excluding /dev /proc /sys etc... I have then modified /etc/fstab to mount new UUID's and reinstaled grub via live CD and chroot.
At this point, when I replace my system disk with backup one, the boot process start as usual, but when it starts loading services the boot process does not continue. The system is not "frozen". If I press intro, there is a line feed on screen. If I mount the backup disk in another system, there is nothing writed to /var/log/syslog or dmesg files during the boot process. I can change terminal with <alt>F2 but there is no login. In console, with backup disk I get:
Code:
....type 1505 audit.... operation="profile_load".....
Done.
fsck from util-linux-ng 2.16
/dev/sda1: clean ......
fsck from util-linux-ng 2.16
/dev/sda5: clean ......
* Stopping remote control daemon(s): LIRC
* Loading LIRC modules
lircd-0.8.6[1057]: lircd(default) ready, using /var/run/lirc/litcd
* could not access PID file for nmbd
And with original system disk:
Code:
....type 1505 audit.... operation="profile_load".....
Done.
fsck from util-linux-ng 2.16
/dev/sda5: clean ......
fsck from util-linux-ng 2.16
* Stopping remote control daemon(s): LIRC
* Loading LIRC modules
lircd-0.8.6[1057]: lircd(default) ready, using /var/run/lirc/litcd
/dev/mapper/coll-root: clean ......
* could not access PID file for nmbd
* Setting preliminary keumap...
Ubuntu 9.10 coll tty1
coll login:
Having an issue I've been unable to resolve for for a week now. I've 2 drives, SATA1 for OS and operating files, SATA2 for media storage. came home last week to an update manager window present and error in Transmission stating unable to second drive due to "Read Only" status. the drive was never set to read only status but following the update manager a reboot was needed. once rebooted, the GRUB menu came up (dual boot system), selected Ubuntu then booting stopped. blank black screen with blinking cursor. rebooted several times, checked bios recognition of both drives, replaced cables, switched power to drive to separate cables, used different SATA ports but nothing worked. finally removed the second media storage drive and Ubuntu booted normally. now any time i connect the second drive and reboot it fails to boot into ubuntu or XP. i removed the media drive and installed it in another computer and it worked normally. have searched everything i can but no answers have been found so far. wondering if anyone here has had similar trouble or has idea for what to try.
I'm using Ubuntu 10.04 64 bit with current 3.6.32-28 kernel
I just fresh installed openSuse 11.3. Am trying to install Hupervisor and Tools but during the install I get the message that xen itself can't be installed while it needs 20MB space.My boot partition is already maxed. At least that is what the partitioner is telling me that 70MB is the maximum setting.
View 2 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?
Tonight i had the bright idea to upgrade from the previous LTS release to 10.04 LTS on my physical collocate in texas.
Ran do-release-upgrade --proposed per the ubuntu LTS upgrade guide, everything went smoothly, few random package issues with spamassasin and my apache configs but nothing that made me weep. Rand a apt-get -u dist-upgrade after to make sure nothing was missed and all was right in the world.
....Until i rebooted. Now my machine fails to boot and falls through to a (initramfs) prompt.
everything was hosted off this box and i'm desperate to get it back up. After hours of googling all i can find is info for DomU's with the same issue....but that has to due with the ubunut developers making 10.04 incompatible with older dom0's or something....and again this is a phyiscal machine.
My hosting provider has me booted into a RIPlinux rescue disk to work on this
Here is my fstab
Code:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
#/dev/sda2
code....
I have a 1.0 ghz G4 eMac running Tiger. Using Ubuntu 10.04's Live-CD I installed 10.04 on a 8-gig USB flash drive and it worked very well despite spending nearly five hours to download its files via DSL and a pokey USB 1.1 port. The flash drive's 10.04 installation worked just fine on my eMac and 900mhz G3 iBook except for Airport wireless non-connecting issues.(I like Ubuntu 10.04 because unlike Mint for PPC, you're not hassled or barred from accessing your Mac HD and its files.) THEN, to resolve my wireless issues, I decided to upgrade to 10.10 which took nearly 12 hours, and it seemed to've installed well until I tried booting the flash drive and it doesn't work. I get the Ubuntu icon in the Startup Disk screen but it keeps returning to it even after I select Ubuntu. The error screen I get reads code...
View 5 Replies View RelatedFinally updates are broken - I've been able to use my upgraded F12 system for some time, faithfully keeping up with f10, then f11. Just yesterday it finally broke:
Test Transaction Errors: installing package kernel-2.6.31.12-174.2.22.fc12.i686 needs 10MB on the /boot filesystem
It would appear that the most recent kernel update has broken the 10MB barrier initially set by the version I first installed (for the boot partition). Needless to say, I have quite an investment in this machine, and of course no time to back it all up and do a fresh F12 install. I am hoping someone out there can give me a bulletproof way to steal some space and expand the boot partition...
I'm using the RAID1 setup, which is configured in the BIOS, as it is a HP Proliant server. i have 2 500GB hard drives configured in a mirror. when booting the install, it recognises this, and deals with it fine.
The problem is, when it gets to the section of installing the grub2 boot loader, it just stops and gives me the "ubuntu installer main menu" where if i select grub boot loader install it just loops back, and if i select LILO installer, it errors, saying an installation step failed.
It has the option to skip installing boot loader, but then, can i get it to boot a different way? can i boot manually into the server install and then install GRUB and hope it works? can i install grub1 rather than grub2?
Debian 8 "Jessie"
AMD CPU
EFI motherboard
System was working reliably. Moved components into a new case. Now system will not boot. Either gives error that the disk is not bootable or displays the motherboard configuration screen.
I am able to boot Debian with a USB drive and have attempted fixes in "rescue mode".
I confirmed that the system is booting to EFI mode.
I have tried re-installing the grub-efi package and re-creating the Grub config file with update-grub.
When re-installing Grub I receive "Discarding improperly nested partition ..." warnings but the installation succeeds. I have searched this warning message and the forums seem to say that it can be ignored.
I have tried re-setting the motherboard NVRAM using the jumper block.
The computer shows "debian" as a boot choice in addition to the usual raw drive model listing. However, neither of the choices will boot successfully.
I'm very new to Linux and recently setup a desktop PC with Puppy 5.2.5. only. I chose to have a permanent install on the hard drive and loaded additional PETS and utilities as I thought needed for my use. Last night after immediately booting up the PC I had a power cut lasting a few minutes. When power returned and I repowered the PC, I found during Puppy's boot sequence it reported an error and remained in what appeared to be a console mode - did not carry through and load my desktop. So I inserted the Puppy CD and booted from that but I'm afraid I'm not familiar enough with Linux to understand how I can get back my original desktop setup and run once again from my hard drive without having to go back to scratch.
View 5 Replies View RelatedI have a flash drive that I want to mount as my root filesystem at boot time. When I'm in linux, I can run `mount /dev/sda1 /mnt`, and the kernel will mount the ext3 FS on the flash drive at /mnt with no problems. From this I assumed I could boot my system with the kernel option 'root=/dev/sda1', but this doesn't work. My kernel has no initrd, and is booted directly by a bootloader. It has no modules, so I know that's not the issue.
The current setup that works consists of a ramdisk that the bootloader loads into RAM before booting the kernel. The kernel detects this ramdisk and the current kernel root option ('root=/dev/ram') mounts the ramdisk as the root fs with no problems.I can see where the kernel detects the flash driveat startup, and I can't think of a reason why I couldn't just mount it as root. I can copy/paste startup logs here if necessary.
I'm completely stumped by a problem with httpd in Fedora 13. It fails to start on boot: I can see: Starting htpd: FAILED, in /var/log/boot.log, but I can't find anything else in messages, audit.log or anywhere else that gives me any clue why. The weird thing is that running:
run_init service httpd start
after boot _works_ and the server runs fine, but even when it's running OK,
service httpd status
reports
httpd dead but subsys locked
I'm guessing that the problem somehow relates to selinux, but I can't find anything in the audit logs that gives me a clue. How to turn on more logging so that I can get closer to the problem. I finally discovered the cause. This system was originally configured to use network services directly, without NetworkManager. It had been upgraded a number of times since installation. It seems that over time, if you have turned off NetworkManager, the defaults have changed. Used to be that the network services was 'enabled' by default (hence started at run time). Now, the default is 'disabled'. Httpd couldn't start because there was no network to start on. Enabling network services at boot time fixed this. I guess I should have noticed this. But one might think that httpd failing to start because of the lack of a network might at least give a warning message in the logs about the reason.
It seemed that it would be simple enough: take the 'f' option in the expert menu of fdisk to put partitions in order after a gap had been created by a deleted partition and then make corresponding changes in /boot/grub/grub.conf because the root partition was shifted.
Well, it didn't work out that way. No matter what I try, I either see the error 15 at Stage1.5 or the error 28, which is even stranger (file does not fit into memory). All this before I even see a grub menu. It just does not get that far.
Does anyone want to take as stab at guessing what might have happened here and whether I have a chance at recovering without having to reinstall? I can provide concrete data, if anyone would be kind to give it a try. Hoping that this is a known problem and something can be guessed from what I stated here but I can be as specific as needed, just don't want to generate noise if there are no takers.
Yesterday I was on my Windows computer doing homework. Once Football came on, I hit the Standby button on my keyboard and walked out of my room. Came back at halftime to discover that my system never went into Standby. I turned on my monitor and saw a bunch of code repeating. I don't remember it all, but it was something to this effect
Super Block not compatible with current BIOS
scanning for *insert system file here*.... not found
scanning for floppy drive... not found
scanning for cdrom1... not found
So I hit the restart button on my tower. When it restarted, I was brought back to the same screen. So I unplugged the power cord from my computer and counted to 10. I plugged it back in and this time I got my mobo logo screen and the system appeared to start up fine, until I got to the SATA drive scanning screen. When my computer would scan for my SATA hard drive, it would idle for several minutes, during which a series of periods (".") would show up until eventually I get a message that says: WARNING! - Something wrong with your hardware!
I have troubleshooted a number of things so far:
1) I took my SATA Hard Drive out of my computer and plugged it into my Linux computer and the system booted fine! I used the same SATA cord, so I know both the drive and the cord ARE WORKING!
2) I tested the power cord from the power supply that runs to my HD and it is working just fine.
3) I plugged the HD back into my Windows computer (the original one it was in when I started having this problem) and I ran GParted. When the GUI came on, I could not see any drives and there was a message at the bottom of the window saying that no devices could be found. This was no surprise to me because I watched the verbose mode as GParted booted and it gave error messages when it tried scanning for my hard drive.
4) I have also tried plugging it into the other SATA ports on my motherboard.
5) I tried flashing the mobo BIOS. The flash worked just fine (or at least it appeared so), but the HD is still not being found on the system boot scan.
Bottom line, I know the hard drive is fine because it worked in my Linux computer. So I am thinking it has to be the motherboard. But before I go out and buy a new Mobo and CPU (and possibly new RAM), I wanted to quickly jump on here.
I was yesterday evening experimenting inserting a script into /boot/grub/grub.cfg. Well I broke grub.cfg and had to try to boot from a grub2 prompt.I have separate /boot and / partitions on /dev/sda1 and /dev/sda2 respectively.Working out the correct syntax for the boot to work was a little complicated, so I thought it would be useful to post the correct procedure here, in case anyone else has the same set up that I do (separate /boot and / partitions)At the grub prompt code:
grub> set prefix=(hd0,1)/grub
grub> insmod linux
grub> set root=(hd0,2)
[code].....
I have the Samba server & users configured, I can access between Linux/Windows shares and both SMB & NMB services are set to be enabled at boot.Everything working.But when I restart the computer, I notice in services configuration that "This service is dead." for NMB. Therefore I have to enable it manually upon boot so that it works.I'm using Fedora 10, fresh installed and updated. I've noticed through search that others have had this issue as well throughout other versions of Fedora, yet I have not found a conclusive solution to this.
View 3 Replies View RelatedI have been looking around and cant really find a guide on how to do this, I have found guides on how-to put a live CD on a usb flash drive, but this isnt want i want to doI want to use a high-end USB flash drive as a sort of SSD to put my boot partition on, I think if i do this it will decrease my boot time significantly. If it works i am going to take the back case off of my laptop and install the guts of the flash drive inside my laptop, i think the mod would be cool, i just dont know how to do it on the software side
View 6 Replies View RelatedOpenSUSE is starting to drive me a bit nuts. Actually what I'm trying to do is simply install VMWare server on a recent as possible SUSE and run 2 virtual machines, both the same SUSE. Of course 11.2 32 bit doesn't run VMWare server 2 so it's back to 11.1. The trouble is, 11.1 won't install properly on my PC.
The install process, booted and installed from the 11.1 network install iso image on CD, runs fine. The PC reboots from hard disk and stops at the grub prompt. I've tried the auto-repair option and reinstalled it from scratch a second time always with the same results. It seems the root partition is hosed, and that's where my understanding hits its limits. Can anyone help?
Incidentally should anyone be able to advise on the VMWare conundrum I'd also be interested. Maybe in another thread...
I have a weird problem with an sata partition. This drive is onle volume of an md raid set, and has one partition filling the whole drive. of type "fd" ( linux raid autodetect). When my machine boots, the drive containing this partition is present as /dev/sdc. However, the partition is not - there is no /dev/sdc1. If I look at the partition table in fdisk, all appears to be fine. If I do anything that causes the partition table to be rescanned (such as writing in fdisk, or running partprobe, ... ), the partition shows up fine at that point and all data is present and when I assemble the RAID using it, its in sync. This drive is attached to the same (motherboard) controller as my other drives which have their partitions recognized just fine.
View 5 Replies View RelatedAfter running Lucid since it's release I decided to wipe out my Karmic partition yesterday in order to utilize that space better elsewhere. So I booted up with the Karmic LiveCD, using the option just to check out Ubuntu. Then I opened up Gparted, unswapped (unmounted) the swap partition, made sure nothing else was mounted, and proceeded to delete my Karmic partition which then provided me with about 40 GB of unused space.
Since I wanted to re-assign 10 of those GB to my primary Ubuntu software partition where I keep all of my personal data, I went ahead and resized that one to make it 10 GB larger. First I had to move the empty space over which took several hours, but that wasn't a problem. Resizing the partition wasn't a problem either. Then I wanted to re-assign the remaining 30 GB to my Ubuntu boot partition which contains strictly my Ubuntu system ... and that's where the problem is.
The remaining unused space on the hard disk is located directly next to my Ubuntu boot partition. No matter what I do while using Gparted via the LiveCD, it doesn't seem to be possible for me to enlarge that boot partition. Does anyone know how I can do this either via Gparted, the Disk Utility from Lucid, or even via the terminal?
I'm upgrading from a 250GB drive to a 500GB drive. I booted into the live-CD, ran gparted and created the necessary partitions:
/dev/sda1 ext4 /
/dev/sda2 swap
/dev/sda3 ext4 /home
then I used dd to transfer data from the old drive to the new drive. Now I am unable to boot into the new drive. I tried to boot again from the live-CD but fdisk reports that the drive has no partition table. I can still mount the devices (e.g. mount /dev/sda3 /mnt/sda3) and I can see all the files. But without a partition table, I can't set one partition to be bootable. Why doesn't gparted create a partition table? it created the filesystems just fine. how do I boot into the new disk? What do I have to do to make grub handle the new disk?
Old drive is dying, so I copied the system over to my new drive. I've moved /home and /tmp to separate partitions and updated fstab and grub with the appropriate UUIDs from blkid. Grub wasn't loading but that's been fixed now.
Problem:
The problem now is that when I boot I get the following screen:
Errors were found while checking the disk drive for /
Press F to attempt to fix the errors, I to ignore, S to skip mounting or M for manual recovery
F doesn't work, and in manual recovery the file system is read-only. How to proceed?
We had a drive failure on /dev/sda. Everything 'except' boot was on raid5 across sda, sdb, sdc, sdd. I know how to repartition a new drive and rebuild the raid etc, but I don't know how to regenerate the files that reside on the boot partition. I really don't want to re-install as we have lot of custom code and software that may depend on our current libraries and build environment.
View 1 Replies View RelatedI was upgrading our lab's dhcp server to Lucid and it totally died. I have it running on a Debian recovery cd right now. I ran into a bug in gtk which I seem to have fixed, but now I have more serious errors. If I boot without a CD, I get dumped into a busybox shell after the machine fails to boot. From the live CD, I tried dist-upgrading again and it dies trying to build and install rsyslog with a broken pipe error. I am at a loss as to what to do from here short of reinstalling (which is the last option as this server has a lot of custom configs on it)
View 6 Replies View RelatedI have/had a working system that took maybe 20seconds to boot. However due to an oops with hardware (power cable fell out) I lost 2 disks in a raid5...so I had to rebuild it, now the new partition wont mount on boot and it takes 180seconds Plus to get a control-d prompt. If I remove the mount from fstab and reboot and then mount manually after a normal boot its perfect and works....so it appears something in the boot/mount process is confused....
The q is where do I start looking to fix this?
I suspect its the LVM looking at the ext4 system and getting upset that its isnt LVM'd? Is that possible? The original partiton was /dev/i2o/hda1 and was not lvm'd and neither is the new....so i dont see why.. multiple 180 second timeouts!
I have been working in my spare time over the last few days, Had problems with the whole grub2 not installing on RAID 1. Then I found out that I had to have a separate non raid Ext4 partition on one drive with "/Boot" as mount point and install went though fine.
My question is, will the developers FIX this. I mean if I only have 2 x 2tb drives in teh pc as RAID 1, and the one fails with the boot partition the whole machine goes down. Kinda defeats the whole RAID feature huh.
I USED to run a windows network with RAID 5 servers, and windows never had a problem installing everything on the RAID. Or even setting up RAID 1 in the bios on the PC and installing XP or NT4 on the RAID 1. There was never a need for a separate non raid boot partition.
Do we need a separate RAID friendly/enabled Grub? I guess for now I will get a 250gb drive and install the Server OS to it, and setup RAID1 manually after the server OS boots. Then will make a ghost type image of the server in case that drive fails so I can quickly install a new drive and restore the image and get it back up and running again.
I have the following "setup:"
iMac (no internal drive/dead) --------- (Firewire) ------- [[MAC OS X]]
|
|
|[code]...
I routinely use the firewire drive to boot MAC OS X.However, I would like to boot from the linux partition of the USB drive. This linux partition had linux installed on it from a live cd, and during that process, I told the installer to install GRUB on the usb drive (which happened to be /dev/sdd).My question is, how do I get this disk to show up during the iMac option-boot? Currently, only the firewire MAC OS X option shows up. I have read about rEFIT, but that appears to install it to the Mac OS X disk (would that still work?)...Also mentioned was installing rEFIT to the internal EFI system partition, but I don't know if that is wise.
I am trying to install a box here where my /storage partition is about 2.5T.I had setup the partitioning with suse, while testing, and all worked well.Now when trying to install CentOs 5.5 it gives me an error, that my boot partition is on a gpt partition and this machine cannot boot that.Also I don't see the option to create XFS partitions from the installer.Can 5.5 support GPT @ install time?
View 1 Replies View Related
