I know that boot partition is possible to create within debian distribution that has grub 2.0, as I have done before with ubuntu. I have been trying many different options with my preseed file but it keeps taking the boot partition out of LVM and creating and extended partition too and then creates the LVM primary partition. My preseed file is below:
code:
I know that boot partition is possible to create within debian distribution that has grub 2.0, as I have done before with ubuntu. I have been trying many different options with my preseed file but it keeps taking the boot partition out of LVM and creating and extended partition too and then creates the LVM primary partition.
### Partitioning.
# you can specify a disk to partition. The device name can be given in either
# devfs or traditional non-devfs format. For example, to use the first disk
[code]....
I know that boot partition is possible to create within debian distribution that has grub 2.0, as I have done before with ubuntu. I have been trying many different options with my preseed file but it keeps taking the boot partition out of LVM and creating and extended partition too and then creates the LVM primary partition. My preseed file is below:
code:
I'm trying to create preseed configuration for debian. Currently I'm working with Debian version: 7 (wheezy), Installer build: 20130613+deb7u2+b1.
What I want to achieve is to have different network configuration than during installation.
I have two preseed files, one in intrd and the second that is fetched through http (url argument to kernel)
In the initrd file there are settings required to get dhcp network settings that will be used during installation:
Code: Select alld-i netcfg/choose_interface select auto
d-i netcfg/get_hostname string unassigned-hostname
d-i netcfg/get_domain string unassigned-domain
Then in the preseed file that is downloaded from network i have this:
Code: Select alld-i netcfg/choose_interface select auto
d-i netcfg/disable_autoconfig boolean true
d-i netcfg/get_ipaddress string 192.168.56.199
d-i netcfg/get_netmask string 255.255.255.0
[Code] ....
IP address settings work as expected, at the end of the installation netcfg runs again and when installed system boots it has static address set (.199). However hostname stays the same, it is not reconfigured.
I have tried many different combinations like removing get_hostname and get_domain options form initrd preseed and appending 'priority=critical' to kernel boot arguments but no matter what I do it always fails.
Is there any way to do this? I know that hostname can be set by hostname= krenel boot arg or by using dhcp option but I'd like to avoid this.
I'm booting a usb stick with a custom initrd.gz, which contains a preseed.cfg at /. This preseed.cfg has the following initial lines:
d-i debian-installer/language string en
d-i debian-installer/country string BR
d-i debian-installer/locale string en_US.UTF-8
But the installer keeps asking for language/country/locale.
I'm trying to automate Squeeze 6 installation with preseed.cfg, but the keyboard configuration (fr) is not taken into account.Given the debconf logs, it seems that the language is set before preseed.cfg is read. So I added "console-keymaps-at/keymap=fr locale=fr_FR" to the syslinux.cfg kernel line.That skips the installer keyboard selection page. But in debconf logs I can seed "Setting debconf/language to en".What am I doing wrong ?Here are the related options I set in preseed.cfg. I can't find an exhaustive debconf options list, and their exact meaning ; does anyone know of one ?d-i debian-installer/locale string fr
# The values can also be preseeded individually for greater flexibility.
d-i debian-installer/language string fr
d-i debian-installer/country string FR
[code]....
I've run into a situation where when performing a pxe/preseed install the system boots up into the install without issue, getting a dhcp address, then the installer begins to configure the network and it gets to where it request a dhcp address and it instantly fails the install stating that we are either not using dhcp or it's slow.
I've added d-i netcfg/dhcp_timeout string 600 to the preseed file but it doesn't seem to be honoured here since it doesn't wait 600 seconds before failing. I have 2 other identical systems that install using the same preseed file but the installer completes as expected. This system has no issues installing centos just debian fails. I did try, once the install failed, to switch to the console and run udhcpc and the server received the address reserved for it.
Is there a method to force debian installer to wait a bit longer for the dhcp server besides what I've already done?
I am trying to get preseed working on a bunch of machines with multiple NICs but it doesn't pick the right interface and/or gets "no link" on all interfaces. My PXE kernel line looks like so (I have auto=true priority=critical and interface=auto)
label squeeze
kernel debian-installer/squeeze/i386/linux
append vga=788 initrd=debian-installer/squeeze/i386/initrd.gz auto=true priority=critical ramdisk_size=10800 root=/dev/rd/0 rw url=example.com/d-i/squeeze/preseed.cfg interface=auto netcfg/dhcp_timeout=60
[Code]...
I have a partition that I want to put Debian on, and I'm using UNetbootIn, and whenever I try to use it, I can't make it install to my drive. The only option is for my C drive. Can you tell me another way to install Debian to my partition. Do I need to make the partition a logical drive?
View 1 Replies View RelatedI noticed that when using the "daily built images" from Squeeze via Netinst, during the disk partitioner, I am un-able to make the /boot partition bootable.or some reason I can't enable the 'boot' flag on several different ISO attempts and differenthardware vendors. The only thing I can see is that this is an issue with the netinst ISO image from the daily built images. Has anyone seen this or is this a known issue / bug? I don't want to file a bug report if possible but I searched and couldn't find anything on this. I doubt I am the only one who's experienced this so far.
View 11 Replies View RelatedMy old computer started randomly rebooting so I went out yesterday and bought a new one. It's a standard Intel 64 architecture with 2gb ram etc.The old computer was running Lenny however I'm happy to upgrade, so I just went to the main Debian download site and downloaded:debian-6.0.1a-ia64.netinst.iso (this didn't work, apparently ia64 is for itanium and my machine is definitely not that), so I downloaded: debian-6.0.1a-amd64-netinst.iso, burnt the CD and ran the install. First time through I had a power failure.
Second time through (a complete fresh start - new partition and everything) it went all the way through to completion and reboot.Clicked 'Continue' to reboot and the machine reset as it would normally and the Grub loader started okay, prompted for the "Debian amd64" standard boot image, selected that and the first 6 lines appeared normal, then the messages wizzed by so fast that only superman could read them. Then they stop - here is some of the content...
[3.816673] Kernel panic - not syncing: Attempted to killl init!
Call trace:
get_empty_filp
panic
[code].....
Running it again I get similar stack stuff but it's a different place: [3.541816], [3.427502] And sometimes if I wait for a minute or two it will continue on further but appear to crash again. Hardware details (everything is onboard - no added cards):
G41M-S3
Intel G41 + ICH7 chipsets
CPU: LGA 775 for Intel Core 2 Extreme
[code]......
Is the amd64 the wrong image? Should I try i386? Is it a blip and I should just rerun the entire install again?
Hi all,
how can I make vncserver starts on boot?
Realvnc was installed by "apt-get install vnc-server" command.
There in NO start-stop script in /etc/init.d/ (is it ok? ), so I can't use update-rc.d. When placing
vncserver
or
/bin/bash -c "cd /root/ && vncserver :1" 2> /tmp/vncstart &
in rc.local it starts nothing but "vncpasswd //.vnc/passwd" (and YES, there is password in /root/.vnc/passwd)
Please, help!
I have a Redhat Enterprise Linux system and I want to re-make it as Debian. I downloaded the Debian netinst iso but can't seem to make a bootable CD out of it, and I haven't found any adequate explanations anywhere.
I tried burning the iso directly to a disk. i set up the boot order in my BIOS but when I restart the machine it spins the CD drive a few times and then moves on to the hard drive.
I tried expanding the iso into a directory, and then copying all those files into into the "Blank CD-R Disc" on my Gnome Desktop, burnt the CD, and still no boot.
I found some instructions using X3b, but X3b was giving me errors.
I just installed Debian on the unused part of my HDD. It did not pick up the other OS I have on this PC, but the installer said I could later edit GRUB to make the other OS boot again. I have looked around and done some searches with no luck.
View 14 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 would like to make a boot RAID0 LVM on a pair of SSDs (sdc and sdd). The system is already running off of a HDD. I built the RAID0 through the Asus BIOS on the Intel controller. I see:
# cat /proc/mdstat
Personalities : [raid0]
md124 : active raid0 sdc[1] sdd[0]
59346944 blocks super external:/md126/0 32k chunks
md125 : active raid0 sda[1] sdb[0]
222715904 blocks super external:/md127/0 32k chunks
[code]....
My challenge is that when I open Gparted, it only show one disk at a time. I would like to learn how to use Gparted to partition this RAID0 with a UEFI sector and LVM for the rest.
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)
I have been running Jessie on an EFI motherboard for a while, booting just fine from a GPT formatted partition on my 3TB hard drive.
I had to re-purpose that PC, and put the hard drive into a different system that uses a BIOS instead of EFI.
Now when trying to boot, I get a text at the top of the screen that says:Code: Select allGRUBÂ ...so it finds GRUB, but nothing ever happens. <CTRL>+<ALT>+<DEL> resets the system.
parted 2.3 says:Code: Select all 1   1049kB 3001GB 3001GB ext4        boot
 2   3001GB 3001GB 32.5MB           bios_grub, legacy_boot(I set the legacy_boot flag trying to fix this problem, but that flags the partition, not the MBR)
Is my problem that the "bios_grub" partition is at the end of the disk instead of the beginning?
I have read that newer versions of parted allow you to toggle the "pmbr_boot" flag directly in the MBR by using the command "disk_toggle pmbr_boot" or "disk_set pmbr_boot", but parted 2.3 apparently doesn't support this.
The pmbr_boot flag in the MBR seems more likely to be the problem than the partition at the end of the disk.
Do I need to find a newer version of parted that supports the pmbr_boot flag for MBR (if so, which version please), or do I need to move the partiton to the beginning of the disk?
so as my title implies I like to login to my headless debian box after it reboots yet havent found any info on that. Can someone please tell me of script which I suppose would be used to make vino start as a process right after boot
View 2 Replies View RelatedI like to login to my headless debian box after it reboots yet havent found any info on that. Can someone please tell me of script which I suppose would be used to make vino start as a process right after boot.
View 3 Replies View RelatedIs there recommended file system for boot partition. Debian default use ext2. Why? Can it be used ext4? I know the difference between ext2 and ext4. But why, currently in Debian, boot partition is ext2 and all others are formated with ext3...
View 3 Replies View RelatedI used gparted in PartedMagic to resize my /home partition from 360GB to 160GB, and create a new FAT32 partition out of the remaining 200GB.My /home directory only had about 9GB worth of files in it and as far as I can tell there was no reason for any of them to be anywhere near the portion which was deleted. So the resizing and creating the new partition seemed to go fine. Then I rebooted and it got stuck while booting into Debian.
I tried checking my BIOS for an IOMMU option but there doesn't seem to be one at all. I also only have 4GB of RAM so I don't know why it thinks I have 4.75GB.
I have a Dell PowerEdge SC1425 with two SCSI-disks, that I have tried installing Debian Squeeze on. This machine has previously been running Lenny (with grub 1), and the upgrade was done by booting a live-cd, mounting the root partition and moving everything in / to /oldroot/, then booting the netinstall (from USB), selecting expert install and setting up everything (not formatting the partition).
Both disks have identical partition tables:
/dev/sda1 7 56196 de Dell Utility
/dev/sda2 8 250 1951897+ fd Linux raid autodetect
/dev/sda3 * 251 9726 76115970 fd Linux raid autodetect
/dev/sda1 and /dev/sdb1 contain a Dell Utility, that I have left in place.
/dev/sda2 and /dev/sdb2 are members of a Raid-1 for swap.
/dev/sda3 and /dev/sdb3 are members of a Raid-1 for / formatted with reiserfs.
After installation, grub loads, but fails with the following message:
GRUB loading.
Welcome to GRUB!
error: no such disk.
Entering rescue mode...
grub rescue>
Doing "ls" shows:
(md0) (hd0) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)
I can do the following to get grub to boot:
set root=(hd0,3)
set prefix=(hd0,3)/boot/grub
insmod normal
normal
This will bring me to the grub menu, and the system boots.
It appears that grub has only found md0, which I believe is the swap partition, because ls (md0)/ returns error: unknown filesystem. I have installed grub to both sda, sdb and md1, and tried dpkg-reconfigure grub-pc and dpkg-reconfigure mdadm, as well as update-grub.
I manually added (md1) /dev/md1
to /boot/grub/device.map, but still no result.
I have run the boot_info_script.sh, but unfortunately I cannot attach the RESULTS.txt, because the forum aparently does not allow the txt-extension. Instead I have placed it here: [URL]. I am tempted to go back to grub-legacy, but it seems I am quite close to getting the system working with grub2.
I have an old version of DSL installed, followed by XP. On a further partition I installed Debian 6. Installation of Debian went smoothly, including the final detection of the other two OS for Grub. I had expected that the Debian-version of Grub would override/overwrite the one that came when I installed DSL.
It did not - when I boot, Grub comes up with the old DSL menu, in which Debian is not included.
From what I've been reading about Grub, there's two "fases", first in MBR, that points to the second part where the actual boot-commands are given, in my case stored in DSL.
When I open the Grub config-file in Debian, both DSL and XP are correctly listed.
Now I'm not sure what to do - I'm a bit hesitant to try and point grub-fase-1 to Debian (if I can write the correct lines at all, I'm very insecure on that) - if that fails, I cannot boot at all. But I'm not really sure either how to formulate a new rule in the DSL-grub, to make Debian boot from the existing menu.
in debian stable, what is the proper configuration to add in /etc/fstab in order to mount ntfs partitions automatically at boot time, for all users, and every user to have read, write and execute permissions ?
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?
One of my disks in my computer crashed, it was the one containing /boot and some data partitions. The other system and /home partitions were on a second disk, which is ok.
I was wondering, can I create a new /boot partition, and keep on using the rest of the system? Can I somehow do it with a chroot from a live/installer disk, run grub, and use my system again? I have another disk which I can put in the system, but there is even an unused partition on the disk which is ok (but it is rather big for /boot).
I have just installed Ubuntu (/dev/sda7) and Debian (/dev/sda4), but since I have updated all informations on Ubuntu, then Debian did not appear anymore on the grub list. There is an wiki I have found, but I an not really sure about what to do.
Here are the boot informations:
Boot Info Script 0.55 dated February 15th, 2010
Boot Info Summary:
=> Grub 2 is installed in the MBR of /dev/sda and looks at sector 488861020
of the same hard drive for core.img, core.img is at this location on
/dev/sda and looks on partition #3 for (,gpt3)/grub.
[Code]...
ps: on this file, it says that the /boot is installed on the MBR and /dev/sda3. I will remove the boot from MBR as I am now using /dev/sda3 instead. Sorry for my english
can i make an animated screen that appears when Debian boots up, i want it to resemble the Mac OS X splash screen with the apple logo in the center and a spiral but instead of the apple logo i want the Debian logo instead just thought it be a cool addition to add to my system it should look like this
[URL]
but i want the Debian logo in the place of the apple logo, is it possible to make a custom splash boot-up screen
I installed Debian stable and I see these errors in the xsession error file
/etc/gdm3/Xsession: Beginning session setup...
GNOMEKEYRINGCONTROL=/tmp/keyring-j0E6Br
SSHAUTHSOCK=/tmp/keyring-j0E6Br/ssh
GNOMEKEYRINGCONTROL=/tmp/keyring-j0E6Br
[code]....