For several days I stuck on a problem despite my various searches on the net. I just installed a machine in RC1 Squeeze.
My Partitioning
Disc 1
/ boot RAID 1
/ swap RAID 1 and encrypted
/ RAID 1 and encrypted
[Code]....
I am trying to install debian on a compaq presario 6000. When I try to boot off of the first dvd it just won't do anyting most of the time; one flat line keeps blinking. The first time that I booted it, there was that line that starts with isolinux, but that was only there the first time. now nothing shows up.That first time, I got several error messages: EDD: error 8000 reading sector 1360652 and the same thing 5 times over with different numbers at the end. Do these mean that the disc is corrupt in some way, or that the dvd reader is broken or something else?
View 14 Replies View RelatedHow can I build a debian boot disc with GNU Zebra installed on it?
View 1 Replies View RelatedI have just installed 11.3 x64. The installation went fine and worked for the first few hours. I ran the online update tool, and now it cannot find grub unless the installation disc is inserted and I select the "boot from hard disc" option.
I have read about the problem of the root partition being back, but not sure that's it.
sda1 - swap
sda2 - /
sda3 - /home
There used to be a repair tool in the installation disks. I could not find that in this media. Is that still available?
I'm running windows vista right now on my laptop and I can't boot into ubuntu, I tried downloading that one program from the disc to assist in helping it run from boot, but it still goes right to vista. I don't know what to do.
View 2 Replies View RelatedI have been having a problem with my 11.1 recently, in that it gets stuck at a point in the boot process that tells me "INIT cannot execute /bin/sh" then it says "INIT: id 1 is respawning too fast please wait 5 minutes" and tells me there are no more preocesses in this runlevel and repeats this no matter how long I wait. Since I couldnt find any information on fixing that, I decided to just upgrade to 11.3 with a boot disc. Now my computer wont recognize the disc to boot from it and still gets stuck at the same screen.
View 3 Replies View RelatedSo, I installed AGAIN Squeeze
And again boot fails
Now it shows error 15
I tried booting into a LiveCD (ubuntu) to see what is happening
But I can't open grub.cfg file (you're not the owner, it says)
What do I do to boot into my new squeeze?
Is usplash supposed to work? It hasn't worked correctly in squeeze (for me) for some time. It appears for like 2 seconds never to be seen again. And I never see it at shutdown. I tried splashy, but no splash. Plymouth has been no go with nVidia cards. I don't know if that's changed, but I get no splash with that either. usplash doesn't seem to be in the sid repos. Is it obsolete, or just not packaged yet?
View 5 Replies View RelatedI've been running squeeze for a couple of weeks now, no problems, just some minor sound issues but that is not important ATM.Everything was working fine until this morning i guess, the boot process goes as normal but at one moment it just freezes for no apparent reason it just says Starting K Display Manager:kdm. Has anyone experienced this problem before, or has a solution?
View 3 Replies View RelatedI am looking to build a server with 3 drives in RAID 5. I have been told that GRUB can't boot if /boot is contained on a RAID arrary. Is that correct? I am talking about a fakeraid scenario. Is there anything I need to do to make it work, or do I need a separate /boot partition which isn't on the array?
View 3 Replies View RelatedI cannot boot after installing Squeeze. /home partition is missing.
Here is the related information.
df -h
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 6.5G 4.5G 1.7G 73% /
tmpfs 1.7G 0 1.7G 0% /lib/init/rw
udev 1.7G 196K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /dev/shm
[Code].......
so I just installed Squeeze Alpha1 amd64, dual boot with MS Vista using Grub. Everything seemed fine, but I'm apparently missing about 40GB of space. It should be set up as so:
101GB NTFS /dev/sda1 - Vista
12GB NTFS /dev/sda2 - HP Recovery
45GB ext3 /dev/sda3 - / Debian squeeze
[code]...
I installed Debian 5.0.3 (Backport with .34 Kernel), because my server hardware (Dell PowerEdge R210) needs special firmware and drivers.However, the installation went quite smooth.I put the system on a RAID 1 Array with about 500 GB space.s I said the installation went well, however, it doesn't boot! No GRUB, nothing
View 4 Replies View RelatedI'm using Debian Squeeze on my Presario CQ40-115AU. Whenever Squeeze finished boot (when the login screen appears), there a loud beep sound come out. The same sound also come out when rebooting/shutting down my laptop and this had never happened when I'm using Lenny. Where can I configure so the sound won't come out ever again.
View 2 Replies View RelatedAfter doing a dist-upgrade today, my one year old install of squeeze will no longer boot. It stops with a black screen and has to be hard reset. Cant even get to tty1. The last line in dmesg is: cfg80211: Calling CRDA to update world regulatory domain
mike@vaio ~ $ lspci | grep Network 06:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100.Just wondered if anyone has any ideas before I restore from a backup?
Whenever I reboot, I get GRUB and the _ pinking, and that's it. With rescue cd I can have chroot shell, to troubleshoot I did the upgrade-from-grub-legacy and installed it to both /dev/sda and /dev/sdb In recovery I redid the upgrade-grub and grub-install commands but still have the same "GRUB and _ blinking".
Because the text "GRUB" and then nothing I didn't enouncter while googling, I need to ask here for further troubleshooting.
I tried installing a live version of Debian Squeeze 6.0.0 for the i386 architecture. I am using a first generation MacBook Pro (Intel Core Duo, not Core 2 Duo).
I managed to boot the live cd and install everything using the "guided installation" option, using the whole drive for Debian (I don't have the Mac OS X Snow Leopard disc so I just wanted to install a strictly Debian system). I installed GRUB to the master boot-record, but after finishing the installation and rebooting I was confronted with the dreaded "question mark". After doing a bit of reading, I found that I should have installed the EFI LILO bootloader to the MBR instead of GRUB, so I reinstalled everything, choosing this option instead. But that didn't work either. More question marks. I imagine I must have to configure either of these bootloaders in the shell, but I don't know how to go about doing this.
How to do this without using a Mac OS X installation disc.
i'm used eeepc here the situation i've already install squeeze AMD64 KDE but i want to try using i386 gnome which is more friendly for my eeepc spec. problem is there other boot in my pc. i'm currently using win7, ubuntu 10.10 32 gnome, and ubuntu ultimate 64 gnome and i don't have external HDD.
Question is i want to remove all linux OS and keep my win7 is it ok if i'm using Gparted to delete all linux OS and then installing deb squeeze i386. my next project is to build portable server on eeepc.
Before I ask I know what I'm asking is not recommended.
On Lenny It was possible to change the boot login to permit logins as root
I can't find how to do that since I installed Squeeze.
I've installed 6.0.1a on my xi3 box [URL] and it works great. However when I remove the monitor and keyboard it doesn't boot (I don't know how far it gets, there is no monitor...). I did not install, and do not want, any kind of GUI interface, command line only. This is going in a closet as a solid state rsync backup repo. I have another small system (not this exact one) running Lenny that runs just fine headless - is this some kind of Squeeze regression? Is there any way I can get this running headless (I can't run Lenny on this box because I don't think the Marvell GbE driver is there or is working in Lenny.
View 7 Replies View RelatedI've done the ordinary sources.list update (lenny to squeeze) and Code: sudo apt-get update sudo apt-get install dpkg apt aptitude.sudo aptitude full-upgrade However, udev failed to install, and I used..Code: touch /etc/udev/kernel-upgrade and did full-upgrade again. Everything was going fine, I went through several package configurations and suddenly, after 30-40 minutes of "Unpacking Setting up." I just heard two system beeps and got an error similar to a kernel panic. The SYSRQs did nothing. Did a hard reboot.I got two kernels in GRUB now. + the GRUB2 chainloading option. Used this one and got Code: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block It's all the same with the 2.6.32-5-686 kernel kernel panic. Using the older kernel didn't fail on the boot up, but showed many UDEV related errors and logging in was impossible - all I get were segmentation faults. Forgot to mention it - my FS is Reiserfs
View 7 Replies View RelatedIf you want, skip straight to the 'QUESTION' at the end of my post & refer to the 'EXPLANATION' later. EXPLANATION: Using Debian 6.01 Squeeze 64-bit. Just put together a brand new 3.3Ghz 6-core AMD. I had a nightmare with my Highpoint 640 raid controller, apparently because Debian Squeeze now handles raid through sysfs rather than /proc/scsi. The solution to this, of course, is to recompile the kernel with the appropriate module for /proc/scsi support. So I thought "screw that" and I've yanked out the raid card & went with Debians software raid. This allowed me to basically complete my mission. The raid is totally up and running, except for one final step... I can't get the raid to automount at boot.
My hardware setup;
- Debian is running totally on a 64Gb SSD. (sda)
- I have 3x 2Tb hard drives used for storage on a raid 1 array (sdc,sdd,sde)
[Code]....
I newly installed debian squeeze with software raid. The way I did was, as also given in this thread.
- I have 2 HDD with 500 GB each. For each of them, I created 3 partitions (/boot, / and swap)
- I selected the hard drive and created a new partition table
- I created a new partition that was 1GB. I then specified to use the partition as a Physical Volume for RAID. and used for /boot and enabled bootable.
- Created another partition, which is of 480 GB, and then specified to use the partition as a Physical Volume for RAID. and used for /.
- Created another partion and used for swap
Then RAID configuration:
Through Configure RAID menu -> create MD device ->
(2 for the number of drives, 0 for spare devices)
Next select the partitions you want to be members of /dev/MD0. I selected /dev/sda1 and /dev/sdb1 (for /boot)
Next select the partitions you want to be members of /dev/MD1. I selected /dev/sda6 and /dev/sdb6 (for /)
And no RAID for swap partitions
'Finish Partitioning and write changes to disk' --> Finish the rest of the install like normal. Everything is ok now, except I am not sure how to test my raid config. When I pull the power of the HDD, it only boots from one disk. I read in some forum that I may have to install GRUB manually on the other. In Debian Squeeze, there is no grub command. Not sure how to make my software raid bootable from both disk. I configured /boot partitions of both disks to be boot=yes. Not sure whether that is ok.
There seems to be a problem with Raid on Debian. I got a new Fujitsu Primergy TS 100 S1 server, with hardware Raid (and 2 disks) installed everything nicely over the net including GRUB - but when it comes to reboot the system does not boot.
Is there anybody here who knows about the problem?
Forgive the terseness. I'm frazzled with this issue, perhaps I should have asked earlier. Every weekend for the past 2 months has been an endless cycle of 'repair broken system' off the install disk.
Installed from Ubuntu server 10.04LTS x86_64, + xfce-desktop Here is uname -a Linux ournas 2.6.32-25-server #45-Ubuntu SMP Sat Oct 16 20:06:58 UTC 2010 x86_64 GNU/Linux If I add my raid + lvm to the fstab file, the boot stalls, (no error it, just hangs waiting, forever). So that's a not very user friendly to start with.
I've tried the suggestions about UUID in fstab tried using LABEL instead, or even /dev/xxx. Every time it hangs. I've googled this endlessly and not found a solution. So don't ask why... since I seem to have tried every odd suggestion to fix this, I've lost track. There seems to be some consensus that whoever gave us plymouth laid an egg. Forgive me if I'm wrong, but did we need a better graphical boot if it breaks everything else?
[Code]...
'rolling' release as redoing install /upgrade every 6 months is getting 'old' My machine is triple boot
Hard drive is 320 GB
Windows 7 - 167 GB
Ubuntu - Maverick - 73 GB
Ubuntu - Natty - testing version - 65 GB
I do not want to screw up my 'grub' as it's been trashed a couple of times recently and had to re-install everything, which went great with install setting up partitions. I am not sure where 'grub' is installed to. I did install Windows 7 first then let installer split hard drive in half to put Ubuntu on then while installing my second Ubuntu, I let installer split the Ubuntu partition in half, hence the 167 GB Windows and the 2 smaller partitions for Ubuntu.I was thinking to maybe let Debian install over my Maverick install. Would that work and not mess up my Grub and cause me to not be able to boot and have to fix the drama?
I am using Gnome and Squeeze. I am wondering if I have a problem of understanding, or a problem that I found with Gnome.
My configuration is with a 3 hard disk system.
disk1 (Debian)
disk2 (XP and Fedora)
Disk3 (W7 and a Data partition)
When I boot and log in, all partitions for disk2 and disk3 are mounted read-write. Only by going to command line am I able to unmount the drives with the following sequence
cd /media
umount *
umount *
I should be able to mount and umount a drive by providing or responding to a root password. But I am not given the option to present a password. My request is blocked.
I also do not want to see the drives remounted after a boot. I tried to find out how this was managed, but I was unable to discover the module and it's parameter list that controls or does this task.
I have just installed Squeeze on my laptap with a radeon mobility equipped laptop. When it boots, I see the following message:r600_cp: Failed to load firmware "radeon/RV635_pfp.bin".and some others, too, but it stalls at that point, and I cannot use CTRL-ALT-F2 to get a text-based prompt - in fact, I can only seem to get it back with a ALT-SYSRQ (R-E-I-S-V-B) sequence to force a reboot. It is a multi-boot system, with a windows partition, Ubuntu partition, and the new Debian partition. The Ubuntu and Windows partitions will still boot, only the Debian stalls.
When I boot into Ubuntu, I can see the Debian partition, and can see (for instance) the /var/boot/dmesg file, but it only says:"(Nothing has been logged yet.)"So, being new to debian itself (even though, I know, that Ubuntu has a debian base), how can I make it boot without X, which is I presume, the center of the difficulty? Can I change some file on the debian partition using Ubuntu to get the debian partition to boot in text only mode, and then try to fix the radeon driver?
Alternatively, can I put the proper files for the radeon driver *from* the Ubuntu partition *to* the debian partition and expect it to load and boot correctly? I did, at one point, download and install the proprietary ATI driver files on Ubuntu, so can I put them in a proper place on the debian install?
I messed up my install so now I can't boot it. I get errors. I doubt I'll be able to fix it. I messed up the upgrade of the kernel images... I'm not sure whether there's something I could do in the Grub config file... I have one other Linux OS I can use in the meantime (plus Windows OS) so I thought maybe boot that up and check the Debian partition in case there's any files I want to save/keep. If I re-install, is Debian Squeeze LXDE still a good choice? I'm going to install something different in the partition where the other Linux OS is. Right now, it's grub is handling the boot loader. The computer is an old laptop, a Thinkpad T41. The HDD is 160GB.
View 3 Replies View RelatedI've got a fresh install of Squeeze on a 32bit host and I have been unable to boot into XEN/dom0.The Xen Kernel is "linux-image-2.6.32-5-xen-686" (pvops) and Hypervisor is xen-hypervisor-4.0-i386.The system default installed with grub2.It boots quite happily in normal mode, using the above Kernel, but just reboots itself if I try run it as Xen/dom0. (reboots within a second of pressing <enter> ... there is no messages displayed on the screen that I have noticed)The relevant menu (generated by /etc/grub.d/20_linux_xen) entry for running Xen is as below;
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
[code]....