i use a 3rd party boot mgr.i installed jessie over etch on my old computer & only choice i saw for grub was sda & sdb where i wanted to install on sdb9.i tried installing it from my wheezy partition & it did but i ended up with 2 boots to wheezy.so i went back to etch.
my question is how to get grub on sdb9 like it was on etch.is there a trick or did i miss a prompt? on another note, that bug where the format hangs if you try & install over an old system is a little irritating. can't believe it hasn't been fixed.
I'm trying to run 'grub-install /dev/sda', it stays stuck on 'Searching for GRUB installation directory ... found: /boot/grub' after leaving it for an hour, nothing happens. I have tried removing all Grub related packages and installing grub-legacy several times, to no avail.
The machine is quite an old one and is an offline sandbox for a friends kid who likes to tinker with older OSes. The hard disk has failed in it so I have donated an old drive to get the machine back up and running for him, as the menu.lst is a lot easier to modify than the newer grub.cfg, he would like the older grub back.
I've done a few searches particular for Debian 8, but the closest I can find is for Ubuntu here, [URL] ....
I have tried to use both the grub rescue disk and the command line listed in the link above.
I've changed my /etc/apt/sources.lst file to use "jessie" repositories instead of "wheezy". I then ran synaptic and updated everything (there were loads of packages, something like 2000 to update).
After this I rebooted. The grub menu shows as usual with the background image I'd set and the operating systems as usual (including Windows 7) however there is no longer a 5 second countdown and when I select *any* menu option, it asks for a username and password.
I don't know what username and password it's asking for as I never used to have one set!!! I did have a username and password set up so that if you wanted to edit a grub menu option so I tried that but to no avail.
I have an issue with Gparted v0.19.0 (Jessie) which has replaced v0.12.1 (Wheezy) which works fine. I had hoped to ask this question in Gparted's own forum, but after three weeks and multiple attempts no-one has approved my account there.
Unfortunately, my existing partition structure (on two different laptops) seems to be invisible to the new version of Gparted. Since parted seems to be used by the Debian installer, the Jessie installer cannot install on these machines without repartitioning the entire disk. That means that on such machines, the only option is to wipe everything or install Wheezy, then edit sources.list to upgrade to Jessie.
Both Gparted v0.19.0 and the Jessie installer report the entire hard disk as a single Fat16 partition,The same partitions which are invisible to Gparted appear as normal in the Places sidebar, of either Thunar or the PCManFM file manager. They can be mounted and used, seemingly without issue (I have experienced the same problem under Ubuntu/Lubuntu 15.10). Below, is the shell output of fdisk, which can see the partition structure and parted, which cannot:
There seems to be no documentation on how to automount partitions and USB devices under systemd in Jessie. (Overall, systemd entirely lacks any useful documentation or GUI configuration tools -- all very cryptic and hidden.)
I created custom files to enable automounting. I put them in /etc/systemd/system -- this may not be the right place, but it works.
Kernel note: This does not work under the old Wheezy kernel linux-image-3.2.0-4.
To automount my Windows partition so I can access its files, I created: /etc/systemd/system/media-windows.mount
The name of the file must match the mount point -- in this case, /media/windows
My file notes the device and file type, plus an fmask option so all the Windows files don't seem to be executable:
[Unit] Description = windows mount to /media/windows [Mount] What=/dev/sda1 Where=/media/windows Type=ntfs-3g Options=fmask=111 [Install] WantedBy=multi-user.target
The file ownership must be root.root. Apparently it doesn't need to be executable.
After creating, enable with:
sudo systemctl enable media-windows.mount
and it will mount on the next boot.
I read elsewhere that the before running the enable command you should run a start command:
I believe this has something to do with an mdadm update which was included in the release. When I configured the array, I didn't partition the disk devices, so maybe that has something to do with it. I am thinking of rebuilding the array and partitioning prior to build, but a quick fix would be referable.
And also something appears to have happened to the raid device since the update.
Prior to update, the array was /dev/md0 - now it is /dev/md/0 which is a symbolic link back to /dev/md0.
mdadm --detail --scan now reports /dev/md/0 where previously it reported /dev/md0
I created a new RAID1 array on a fresh system and immediately after the create, these messages appear at 5 minute intervals.
I want to install grub on the ubuntu root partition because I have another boot loader (boot-us). But when I reach : device for boot loader installation and set the device to the root partition (/dev/sda3) the OK button is not highlighted, I can use the windows partitions but not ubuntu root partition, what goes wrong?
Because 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
First upgrade to 11.3 no problem. Then I got a disk issue. so got an old 80 gig sata drive, config new partition table, format etc. Install perfect as ever.
Then grub failed ....no grub menue.
I changed to MRB boot. this worked but initrd takes a long time and sometime hangs ?!? What could be the issue ? Harddrive?!
So I need to become the root user in order to edit a grub file in a seperate partition, so I can get back into this partition. How can I become and stay as root user in the desktop environment? (I know you shouldn't do this, but I need it.)
As recommended, I'm creating a new thread for my configuring GRUB problems commented first hereWe are setting up a new version of a custom system, we are migrating to Ubuntu Karmic from another distribution (Slackware). Besides small differences between these systems (most of them from the most recent versions of software used by the latest Ubuntu, such as GRUB 2), it has been decided that the new system will run an union root partition using aufs and tempfs, basically, we are following the steps provided heree install the system to a new hard drive from an already running Ubuntu Karmic system, usingdebootstrap/chroot, we move the disk to another sytem, so we have to correct disk references, we are able to run this system and it behaves correctly the first time it boots, it bypasses the GRUB menu since there are no other systems detected. However, after halting the system and booting it, the GRUB menu appears with a new "recovery" option, we've managed to remove this recovery option usingGRUB_DISABLE_LINUX_RECOVERY=trueBut then, the GRUB menu appears again, this time with only one option to boot: our system installation. But when this GRUB menu appears, it has no default timeout and so it stays forever unless ENTER is pressed to boot into the selected entry.
The main problem is that we are unable to configure GRUB inside the new installation because it always returns this message:grub-probe error cannot find a device for /If we boot the system "normally" (mounting root to a normal partition), we are able to configure GRUB properly, but it does not behave the same when using the union file system as /We are only looking for a way to bypass the GRUB menu and boot our system, do you have any advice on how to properly configure the GRUB menu for our system
I'm booting to Kali 2.0 live from USB and wanted to add persistence, but I can't get OpenVAS setup. The setup script runs and eventually fails due to no more disk space. Here's my df -h output:
Here's gparted:
When the setup runs it fills up root (/) which is only 872mb. This is a 16gb USB so I'm wondering if there's a way to allocate some of the 11gb of unallocated space to root? I couldn't tell how to do this with gparted, would I need to build a custom Kali iso or something with different partitioning?
I am running Wheezy as my main OS in the first drive in my desktop. I use the 2nd drive for data. I am trying to add another OS to multiboot. When I ran grub-update in Wheezy, I am getting device letter for the root device instead of UUID in grub.cfg, in the os-prober section. Like this
i want to ask is it safe to ad more space to my root partition with gparted ?I ask friends and they all told me if i change the root partition is possible to have problems to start my Debian.
I have Linux Mint (LMDE) on another partition and I guess I need to do some 'fixing' so I need to mount the partition. I can't, though, not by just clicking the partition (obviously?). I assume this is because I need root access to mount it.
how I can do this?:
1) CLI - mount via CLI by mounting at some point - for e.g., mine is /dev/sda3 so mount as ?
2) Use an 'editor' or file manager - such as Dolphin - how would I do this?
3) Use a Live CD/DVD - I think this way is unnecessary but it's a way, right?
Anything I missed? I guess gparted could mount it?
Which method would you use?
I think one could ssh into it but I'm not able to do that yet.
I need to exit the xorg.conf file which is recently really messed up.
I recently installed Lenny and used the "Guided - Use Entire Disk" option.I made separate partitions for root, /etc, /var, /home, /usr and swap.I trusted that the auto partitioner would choose sensible sizes but possibly that was a bad move, root is only 340Mb and is full.
The RAID level 1 interested me because of its redundancy in both drives. And I successfully made it in a couple of partitions. But, I always did it after Linux installation. Then, I create both partitions, use 'mdadm' to create raidtab and RAID device (md0, for example) and then I format the RAID device with 'mkfs' and mount it.
Until there, it's all OK.
But my problem is to mirror ALL the hard disk, inclusive root partition. To do that, I guess I need no Linux installation, then create the RAID (md0, raidtab, etc) and after that install Linux in RAID device created.
But I'm new in Linux world and I have no idea how to do that.
I use Debian Lenny, so I need a solution that uses only the first DVD of this distribution.
Is 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.
I 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 ?
For a fresh installation using manual partitioning, one single disk (IDE).
If I selected:
For the root partition, I would like to use ext4, 10GB, but by default, the partition type 'extended' is suggested. Would there be any difference (advantages, inconveniences) if I selected the primary partition instead?
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?
I'm trying to manually boot (from the GRUB console) into a system set up as follows: crypt partition -> LVM -> root LV, and I'm having some trouble figuring out how to do this from the GRUB console.
I have successfully manually booted a system which is set up as just LVM -> VG -> root LV. All I have to do is load the LVM module. In GRUB, that partition shows up as (hd0,gpt5). Once I load the GRUB LVM module, I can see the logical volume within the LVM as well. (My volume group name is "caesar", and the single logical volume is named "root".)
Code: Select allgrub> ls ... (hd0,gpt5) ... grub> insmod lvm grub> ls ... (lvm/caesar-root) ...
It's fairly simple to manually boot:
Code: Select allgrub> set root=(lvm/caesar-root) grub> linux /vmlinuz root=/dev/mapper/caesar-root grub> initrd /initrd.img grub> boot
Where I am having difficulty is in trying to insert crypt before LVM. I can set up such a scheme, and put a minimal installation on it, without issues. It's booting into it upon reboot that I can't figure out. Once I load the GRUB crypto, cryptodisk and luks modules, I can mount the crypto partition:
Attempting to decrypt master key... Enter passphrase for hd0,gpt5 (<long hex string here>): <type my password> Slot 0 opened grub> ls ... (crypto0) ...
At this point, GRUB sees the crypto partition as (crypto0). But the GRUB LVM module doesn't see "inside" of the crypto partition, so I don't see the root logical volume within the LVM listed; all I see is (crypto0).
Code: Select allgrub> insmod lvm grub> ls ... (crypt0) ...
Setting it as root doesn't work:
Code: Select allgrub> set root=(crypto0) grub> ls / error: disk `crypto0' not found.
So, How do I get GRUB to "see" LVM inside the crypto partition?
Ok. I have a media server running debian amd64. when I installed it I made separate partitions for root (/) home (/home) var (/var) and swap.
I'm adding some new hardware (mobo and ram) and want to reinstall debian. I would like to keep my home and var partitions intact and just reinstall everything in root (/) partition.
I'm unsure of how to do this during the installation. Do i need to format? how do I tell it to use the /var and /home partitions?
A while ago I moved partitions from sda1 to sda6 because the original partition wasnt big enough. So when I update grub (now grub 2) it resets everything to sda1 and I've no idea how its doing it. Does anyone know where grub 2 gets the default partition from or does it just select sda1 automatically?
I am new to Debian but have some basic experience with Linux and am currently trying to triple boot Windows 7, Fedora 16, and Debian on an HP Pavilion dv7. I have the Windows Boot Loader on my MBR because I've heard that Windows updates can cause boot issues if GRUB is installed there. This means that I've been installing GRUB in the /boot partition for each Linux distro and creating corresponding entries in the Windows boot menu.
This has worked in the past with both Fedora and Ubuntu, but I have not been able to work around it with Debian. When I choose my Debian option in the Windows boot loader, it loads GRUB but hangs after it prints "Welcome to GRUB!", and I have to restart the computer. I would like to hear what more experienced Linux users have to say both about why this isn't working for Debian and about if keeping the WIndows boot loader is the right way to go.
Also, here is my partition layout:
Partition 1: SYSTEM (HP pre-installed) (209 MB) Partition 2: Windows Partition (472 GB) Partition 3: Extended (160 GB) 1: /boot for Fedora (524 MB) 2: Physical Volume for other Fedora partitions (79 GB) 3: /boot for Debian (749 MB) 4: Physical Volume for other Debian partitions (80 GB) 118 GB free space Partition 4: HP_TOOLS (HP pre-installed) (108 MB)
