I was trying to get the Windows one working again. Here's what fdisk -l reads:
[Code]...
I'll change these or do some grub configurations, if anyone knows what ones can work.
I recently installed Debian, and its great except hardware config, any way already fixed that, I reinstalled windows 7, and it removed Grub I tried reinstalling it, and reconfiguring it no luck I've booted into Debian using a boot CD.
View 6 Replies View RelatedMy computer initially had one hard drive, with Debian Lenny 5.0.4 installed. I haven't done any special configuration, so upon boot, I was presented with the GRUB kernel select menu, then gdm, etc. I think I used the Debian installer's 'use entire drive with LVM' configuration.
I then added a second hard drive, with the intention of installing Windows XP on it. After I installed XP on this second drive, I found out that it had overwritten the MBR on the first drive. (It was my intention do use the BIOS' F8-key boot menu to choose between the two drives, each with their own distinct boot loader. The two drives and OS's would be completely independent.)
Using my Debian installer CD, I think I have GRUB installed on the first drive again. I've found a number of tutorials which say I can use 'set' and 'linux' to boot the system, but the linux command always returns a file not found error.
I think my LVM filesystem is still intact, as the Debian installer's fdisk reports it, it can also chroot to it and my installation appears to be intact. 'ls' within GRUB shows (derek-swap_1) (derek-root) (hd0) (hd0,1) (hd0,2) (hd1) (hd1,1) (fd0) . 'derek' was the hostname I used.
I would like to simply restore the system to the way it was before: with the standard GRUB that comes with Debian 5.0.4, which then boots into the debian with my LVM filesystem. Is there a way to do this from the Debian installer CD? (I was hoping there would be a 'dummy install' command which would install GRUB and configure it properly, but leave all my existing partitions and filesystems intact.)
I have installed Windows 7 on my laptop . Now, it directly boot from Windows 7 . I think the MBR overwrote my grub . I have found two methods by google , but still does work .
1: boot from debian install CD, Alt +F2 switch to the console. "grub " "root (hd0,0)" "setup (hd0,0)".
2:boot from CD, mount /dev/scsi/host0/bus0/target0/lun0/part1 /mnt ; chroot /mnt ; grub-install /dev/sda.
I have a Knoppix DVD-ROM. I also have its image as k.iso at the second partition of HDD of my laptop. I use the DVD-ROM and write at the boot prompt the cheat code:
knoppix bootfrom=/dev/sda5/k.iso
I also have a folder Knoppix made during bootprompt by using the cheatcode knoppix tohd=/dev/sda5 and I can use the following cheatcode while booting from the DVD-ROM, like knoppix fromhd=/dev/sda5My laptop runs Debian Lenny 5.0.4, installed in the first partition of my HDD.
Can Grub be configured to boot from the Knoppix k.iso image, or the knoppix folder, which I use to use the Knoppix OS, so that I am freed from using the DVD, when I want to use the knoppix system?
I have Debian Squeeze amd64 and i install into same hdd in free space archlinux sda3 /boot, sda4 /
How set grub from debian for boot the archlinux?
I am trying to dual boot my system. MS Vista and Debian lenny 5.05. Installed Vista first, need vista for voice recognition software. Installed Lenny second but grub does not see Vista. Installed NTFS-g3 so I can read and write to /dev/sdc1 where my vista is. But grub still does not detect it. Installed grub2 and upgraded from legacy but still grub2 does not see the vista partition.
View 6 Replies View RelatedAfter updating my squeeze laptop today I noticed that grub from a few days back fails to --configure.
The dpkg log says
2010-09-09 18:52:45 startup packages configure
2010-09-09 18:52:45 configure grub-pc 1.98+20100804-4 1.98+20100804-4
[code]....
I have happily been booting debian through grub2 by chain loading it with efi (rEFIt), until today, and now get to begin another learning experience I've been using linux for a while, and kept seeing the guides for splitting up /, /var, /tmp, /usr, and /home, into different partitions, so I did just that when I switched from Ubuntu to Debian (I've realized that this was a little bit pointless because I formated them all as ext4, but at least it acts as a safety for mission critical drives when I overfill /home. I unfortunately didn't give /tmp enough space, and it kept crashing SimpleScan so I decided to use gparted to resize it.
The operation went alright as far as I can tell, and was straight forward because there was some free space behind it so I only had to append the partition. I synced the master boot record through rEFIt as usual, but when I booted the linux partition grub did load, and only a blank screen is presented. I eventually figured out I could use the gparted live cd to boot back into debian, and have been screwing around for a while with grub commands trying to figure out how to allow rEFIt to successfully boot GRUB on its own again. I ran grug-mkconfig to replace my /boot/grub/grub.cfg file and have rebooted but that did not help.
I tried reinstalling grub and grub-common with apt-get, but I didn't purge configuration settings for fear of losing something important. My current focus is on the command grub-install. I think i just need to run this command with the /boot device, like su - root; grub-install /dev/sda1 or some thing like that. wipe out the MBR on /dev/sda1, or screw up what good configuration is left in grub, so I want to make sure that I'm using the right /dev. Currently the gparted output looks like this:
/dev/sda1: fat32 - GPT (gpt from fdisk, gparted shows EFI with the boot flag)
/dev/sda2: hfs+ - MacOSx
/dev/sda3: ext4 - /root
[code]...
how the gnome live gparted disk would have been able to boot. I have access to a hard drive so I'll probably end up making backup images of as many of the partitions as I can, and then try more drastic bashing around, but if anyone has any suggestions/wisdom they could offer while I'm researching solutions I'd appreciate it. I eventually want to try to axe my osx partition and boot directly from GRUB2-EFI so I figure it is worth the investment in time to get to know grub a little bit more intimately.
I've been following grub-common bug #606845 and in coming to a solution for the issue, these guys are using dd as a brute force means of swapping out master boot records or trampling them, if you prefer. (Background: The issue is related to grub and certain xp installations)
An sample snip of code:
dd if=/mbrxp.bin of=/dev/sda bs=512 count=1
1) Is mbrxp.bin a back-up of the mbr taken before installation of squeeze (or grub in general)?
2) Am I fubar if I didn't make a back-up of the mbr before installing grub?
We had a server failure this morning because grub was throwing error 15 (file not found). We discovered that the disk had changed names from hd0,0 to hd1,0. Making the appropriate replacements in menu.lst fixed the problem, but I'm still wondering what could have caused the spontaneous name change.
here are some other possibly related tidbits: * the server had been down because of a power loss, but it is behind a UPS so i doubt there is any electrical damage * eth0 also temporarily failed but the system failed over to eth1
My current theory is that when the bios was configuring the hardware the loss of eth0 shuffled around the addresses of the remaining hardware on the pci bus, which somehow caused the hd0/hd1 confusion. The problem is that everything i've read [URL] says that the drive assignment should be based on the way the disk is connected to the motherboard (which in this case didn't change)
I installed Debian GNU/Linux and Debian GNU/kFreeBSD on the same system. I didn't reinstall grub with kfreebsd, because I figured running grub-mkconfig would modify grub.cfg. But it didn't.It recognized the Debian GNU/kFreeBSD as GNU/Linux (6.0.1):
### BEGIN /etc/grub.d/30_os-prober ###
Found Debian GNU/Linux (6.0.1) on /dev/sda3
### END /etc/grub.d/30_os-prober ###
Installed Debian 6 last night after using Ubuntu for close to 3 years. Couldn't believe how wonderful everything was put together and working, with some minor beginning glitches (like nvidea 3D drivers not working) which were to be expected.
But now I'm sitting back in Ubuntu because I can't get Debian started from Grub anymore. The Grub menu is still there and the selections work fine too. I honestly have no idea what caused this. Last thing I was doing in Debian took place in the Software Center where I was installing some GTK+ themes and looking for some general utilities. I did find a Boot Logo/Login changer, at least that's what I think it was, and when I clicked on install ... I received a message that that application was already installed (must have been by default or through synaptic perhaps).
Anyway, as soon as that message cleared out, perhaps 2 or 3 seconds later the screen crashed and everything went black ... I'm assuming that the xerver crashed. Did a CTRL, ALT, DEL which successfully restarted the system. Got back to the grub menu, selected Debian, and got the black screen again with a login for a user, followed by the password request. Knowing next to nothing about Debian I was obviously stuck at that point. Then I tried the recovery console, and exactly the same thing happened.
Rebooted again, got back into the recovery console, and this time, after adding my user name and password, used CTRL + D which caused a ton of text to appear on the black screen. Near the end of it came a FAILURE message ...
Startpar: service(s) returned failure: gdomap failed:
I have just installed and enabled plymouth, and during the process I had to update Grub. Something got messed up and I have the following issues:
1. Grub does not show Fedora15
2. Windows7 loader is listed as Windows Vista loader
I cannot log into Fedora15, though I can log into Windows... Please guide to the proper resolution of the above issue.
I am having no luck configuring ProFTPd on a Debian Lenny production server we use to host our MySQL databases and a few websites. I had originally set it up so I could login and manage our internal sites, but I have the need to allow a few clients in to access their sites that we host. I am trying to root the users in their site directory, which would be "/sites/www.whatever.com/".
It just hit me while typing this. Is it possible to create a user without a shell to prevent login via SSH and set the home folder to /sites/whatever instead of /home/username? That would allow me to continue operating with my current configuration and root them in their site while preventing SSH logins.
i have a HP MSA 2312fc SAN with 2 LUNs configured. The first LUN (LUN ID 1) is correctly connected to the system, but when i connect the second LUN (LUN ID 30), i find in the syslog this message: multipathd: 8:64: size 6835937472, expected 5267578112. Discard
Here is the multipath.conf
[Code]....
So I correctly see the two luns, but multipath doesn't create the relative devices. Under /dev/mapper I see: control mpath0 mpath0-part1 mpath0-part1 is the first lun, the one I mounted in a directory under filesystem. I can't find the device for the second lun
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
I have some errors when run the mount -all command: mount: wrong fs type, bad option, bad superblock on /dev/sdc5, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Failed to open /proc/filesystems: No such file or directory
[Code]..
I recently installed another Linux distro, Kali Linux, alongside my Debian 8 and discovered to my chagrin that my computer boots to Kali's grub rather than to the Debian grub. I had spent some time customizing Debian's grub and would hate to see that effort go to waste. Is there a way I can get my computer to boot to Debian's grub instead? I tried deleting Kali's boot partition with gparted but that did not seem to do anything.
View 14 Replies View RelatedI am thinking about maybe trying "LILO" [URL] ....
For my boot loader, from what I have read it sounds even more tempting.
I am totally sick of GRUB, even though it is what seems to be the most popular,and is what normally is used as the "default" when any linux system is installed, that is what the install ISO's use, but anyway, that is another topic, over the years, "grub failing", has been a problem for me , many times.
I saw this (From LILO to GRUB Howto).
I have a ~ 2008 notebook (Compaq CQ60-137EL) on which I had Windows 7 only (it was sold with Windows Vista installed).
Later I installed Debian Jessie 8.2.0 Stable ("Graphical expert install" from DVD), along with GRUB as a boot manager (I chose not to install it on the EFI removable media path).
Since then, if I select Windows 7 on the GRUB boot screen, I see "Starting Windows...", and after few seconds the screen flashes for a moment, and then the PC reboots: I see the bios screen, followed by the GRUB screen again.
What's even more weird about this is the fact it just happens only in like ~50% of the cases. In the other 50%, Win7 starts flawlessy.
I even tried to install Debian first, then Windows 7, then re-install GRUB, but I got the same issue, even with both system freshly installed.
On 6 attempts, 3 times it worked and 3 times it didn't.
On my desktop PC I'm in the same setting, but I don't have this issue. I think it may be related with the fact I have Win7 on a SSD and I installed Debian on a separate HDD, while on my notebook, as you can imagine, there's just one single HDD.
I decided to finally change the grub 1.98 splash image today and found a few tutorials on how to do so. They all pretty much said the same thing. Resize an image to 640 x 480, save it as a .tga, stick it in /boot/grub/images/desktop-base. I did so and opened /etc/grub.d/05_debian_theme and changed WALLPAPER="/usr/share/images/desktop-base/moreblue-orbit-grub.{png,tga}" to WALLPAPER="/usr/share/images/desktop-base/56871.{png,tga}". After that I ran update-grub. When it told me the image it found, it said it found desktop-grub. I don't know what I did wrong but it's not finding my image. Like an idiot I forgot to back up the original file but the only thing I changed was that WALLPAPER line, like I said. I had copied that version of the file and pasted it in another document before messing around with different parts of the file to see if I could get it to work. Everything ended in failure so I copied the back up in the other document and simply pasted it over the one I had been tinkering with. However, when I try to update grub I get a syntax error which I didn't before with the exact file I have now. The error reads:
/etc/grub.d/05_debian_theme: 65: Syntax error: end of file unexpected (expecting "}")
Here's my grub file.
#!/bin/sh -e
. /usr/lib/grub/grub-mkconfig_lib
# this allows desktop-base to override our settings
f=/usr/share/desktop-base/grub_background.sh
[Code]....
I'm completely lost at this point, both on how to actually change the splash image and why I'm getting a syntax error.
I'm configuring a machine with Debian 6. I booted from the DVD, took the defaults, and it eventually came up with a Gnome desktop. Everything worked as expected.
I then installed gcc, g++, the Debian kernel source, and built a new kernel with preemptive multitasking turned on. It built clean, I ran "make install" and it put the kernel files in /boot. I rebooted and got a kernel panic error, to the effect that it couldn't find the root filesystem.
/boot/grub/grub.cfg shows
"linux /boot/vmlinuz-2.6.32-5-686 root=UUID=1890437b-5884-4b83-97cf-62d39f63c872 ro single"
for the original install, but the entry for the new kernel has
"linux /boot/vmlinuz-2.6.30DW-preempt root=/dev/sda1 ro quiet"
/etc/fstab has
# / was on /dev/sda1 during installation
"UUID=1890437b-5884-4b83-97cf-62d39f63c872 / ext3 errors=remount-ro 0 1"
I've tried changing the grub entry to UUID, but the new kernel still panics. grub-mkconfig and update-grub just rebuild the split UUID=/sda1 grub.cfg. The new kernel still seems to be looking for /dev/sda1 even after changing grub.
Im running Squeeze (in VirtualBox on a Win host), and I need to clone my drive to a bigger one and boot from that drive. I used gparted from a live cd for the cloning, and got the following result with fdisk -l:
Disk /dev/sda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
[Code].....
I have a PC104 running debian. I have 3 hard drives (in addition to the one booting) mounted in fstab by UUID. I use the options defaults,error=remount-ro. However, this means that when I boot with the hard drives not attached, I have to press Ctrl-D to bypass when the boot discovers the drives are missing. Is there a timeout commandoption I can add to fstab so that it automatically continues booting even if the hard drives are not attached? I could not find anything on a timeout command. (I tried adding timeout=1000 but no-random guess)
View 5 Replies View RelatedA week ago I opened this thread viewtopic.php?f=17&t=61580 in "Board index ‹ Help ‹ Installation" and asked for a moderator to move this to here. Because it hasnt happened up to know, I am reopening the thread here. It would be reeeeally great if somebody could help me with my problem!
I own two computers, one netbook and one laptop. I want to boot my netbook as a diskless client via PXE.I set up a dhcp-, tftp and nfs-server on my laptop but when i boot my netbook, the follwoing messages are displayed:(to make it more clear, i uploaded the whole output and shortened the output below)
[Code]...
I am using Squessze and Gnome. When I try to use the gui System>Administration>Network or Users and Groups I get the error The configuration could not be loaded. You are not allowed to access the system configuration.Everything was working before. I read around a bit. In some cases,it was caused by mismatching group and password files after using the gui. I do not know how to check if they are matching. Of course I do not know for sure that is the problem in my case.
View 14 Replies View RelatedI'm having issues with a RAID array.
Setup is like this:
Debian Jessie, 2 hard disks, each having 2 partitions: /dev/sda1, /dev/sda2, /dev/sdb1, /dev/sdb2. Partitions were paired during installation, so they form /dev/md0 and /dev/md1. /dev/md0 is the root (/) partition, /dev/md1 is for /home.
At the end of the install process, I chose /dev/sda1 to carry Grub. And I think this is where I screwed things up.
After removing one of the hard drives, there was no boot capability. So, I installed Grub on /dev/sdb, too.
Now it displays the boot menu but cannot find the kernel. This is where I got lost in the process.
Do I need to reinstall the OS or is there a way to fix it? I suppose I have to edit Grub.
I installed Lenny on a computer and set up grub to boot windows by default with a timeout of 0 Is there a way to interrupt the boot process so I can boot linux? Or can I boot from a flash drive somehow? PS: nothing to do with topic, but I just found out that the top 24 supercomputers run linux , and more besides. That is way cool. check out [URL]..
View 4 Replies View RelatedI have recently installed Debian alongside Vista on the same boot menu using the GRUB booting device. Only problem is, I couldn't boot Vista at all any more, so I removed my Debian installation from that drive. But the GRUB boot record persists, I don't have the Recovery disk to restore my old system, so I have to find a way to manually remove the GRUB track and put the old record in its place. I assume there was a copy made of it by the installation program, now my only problem is to find that file and copy the content back in place (at the address at the very beginning of the drive) all that by using Linux code, since that is all I have left. Being new to this game, I have no idea how to begin writing the right command for a job like this
View 3 Replies View Related
