Debian Installation :: Bad Burn On Squeeze Rescue CD?
Feb 12, 2011
Looking at the versions of Squeeze available on Live CD's from live.Debian.net I noticed a Rescue CD. I decided to download and burn the 386 version in order to get a look at it. I did so and checked the MD5Sum. It indicated a good download. I then used k3b (which I prefer because it has proven to be somewhat more reliable than Brasero) to burn the iso file. I did it at the lowest speed k3b allows (10X for CDs) and asked for verification of the burn. The disk was verified.I then booted the disk and the disk failed to load citing a read error at block 144640, sector 1157120.
I downloaded another version of the same iso file and again checked the MD5Sum, which was good. I again burned with k3b in the same manner as above and got the exactly the same error.I have had no indication of any problem with my TSST CD/DVD drive and I doubt very much that two consecutive Memorex CDs would be bad. What am I missing here?One other question: Is there a way to check the MD5sum on a disk that has been burned? Should it be the same as the MD5Sum shown for the iso file? I see that I can check the MD5Sum for individual files on the burned CD. Given the very large number of files, which one might it make sense to check?
I have not been able to write to DVDs since the install except for once when luck seemed to play more a part than anything else. Does anyone have a fix for this?Well, after letting it sit and sit and sit, it looks like it does write the data. But, it's writing about 1/2 of a DVD for just 2 500K files.
I have been facing lot of problems installing debian with missing firmware until I found this file: URL....which I suppose it will include the missing firmware (bnx2-mips-09-6.2.1a.fw).I would like to ask what's the best way to burn the file on a DVD and make it bootable? any recommended free tool on Microsoft Windows?
I downloaded this squeeze live rescue iso and burned to CD.[URL].. When it boots, I get a text login screen prompting for username... Problem is, I cannot find anything on google that gives me a working u/p combo... I have tried a variety of these for username/passwords: live, rescue, user, linux, password.
Do I need to burn all 8 DVDs to install Debian? Is there a simple way that I can just burn a small bootable CD/DVD/USB Flash Drive, and add upon everything else I need afterwards by Internet?
I'm inexperienced in Debian. I have a dual-boot machine (64-bit, Debian 7.3, Windows 7, legacy boot) and encouter a problem at boot ever since I completed the installation of Debian 7.3 alongside the exising Windows 7. This machine has six hard drives: two are intended for ntfs storage of general data (raided together by RAID1); two more are intended for ext4 storage of general data (also raided together by RAID1); the fifth contains the Windows OS files and the sixth contains the Debian OS files. The problem is that I arrive to the grub_rescue each time at boot, seeing the message:
GRUB loading. Welcome to GRUB!
error: no such device: e081517b-3399-4067-9294-8f0686f753ca. Entering rescue mode... grub_rescue>
Today it happened again: After an apparently trivial update Grub (Grub2) enters rescue mode the next time booting, not displaying any useful help whatsoever at that point. (Remember that at boot time no manual or help pages are available.) I don't know what went wrong, but ... The harddisk or partition in question is now no longer a bootable partition.
I don't want to use much time trying to sort out things, so unless someone may direct me to at better procedure, I am going to save whatever can be saved from the hd and then reinstall debian (in this case: Sqeeze) from scratch. Nothing else has in my experience ever worked before.
I am running a 14 disk RAID 6 on mdadm behind 2 LSI SAS2008's in JBOD mode (no HW raid) on Debian 7 in BIOS legacy mode.
Grub2 is dropping to a rescue shell complaining that "no such device" exists for "mduuid/b1c40379914e5d18dddb893b4dc5a28f".
Output from mdadm: Code: Select all # mdadm -D /dev/md0 /dev/md0: Version : 1.2 Creation Time : Wed Nov 7 17:06:02 2012 Raid Level : raid6 Array Size : 35160446976 (33531.62 GiB 36004.30 GB) Used Dev Size : 2930037248 (2794.30 GiB 3000.36 GB) Raid Devices : 14
[Code] ....
Output from blkid: Code: Select all # blkid /dev/md0: UUID="2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb" TYPE="xfs" /dev/md/0: UUID="2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb" TYPE="xfs" /dev/sdd2: UUID="b1c40379-914e-5d18-dddb-893b4dc5a28f" UUID_SUB="09a00673-c9c1-dc15-b792-f0226016a8a6" LABEL="media:0" TYPE="linux_raid_member"
[Code] ....
The UUID for md0 is `2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb` so I do not understand why grub insists on looking for `b1c40379914e5d18dddb893b4dc5a28f`.
**Here is the output from `bootinfoscript` 0.61. This contains alot of detailed information, and I couldn't find anything wrong with any of it: [URL] .....
During the grub rescue an `ls` shows the member disks and also shows `(md/0)` but if I try an `ls (md/0)` I get an unknown disk error. Trying an `ls` on any member device results in unknown filesystem. The filesystem on the md0 is XFS, and I assume the unknown filesystem is normal if its trying to read an individual disk instead of md0.
I have come close to losing my mind over this, I've tried uninstalling and reinstalling grub numerous times, `update-initramfs -u -k all` numerous times, `update-grub` numerous times, `grub-install` numerous times to all member disks without error, etc.
I even tried manually editing `grub.cfg` to replace all instances of `mduuid/b1c40379914e5d18dddb893b4dc5a28f` with `(md/0)` and then re-install grub, but the exact same error of no such device mduuid/b1c40379914e5d18dddb893b4dc5a28f still happened.
[URL] ....
One thing I noticed is it is only showing half the disks. I am not sure if this matters or is important or not, but one theory would be because there are two LSI cards physically in the machine.
This last screenshot was shown after I specifically altered grub.cfg to replace all instances of `mduuid/b1c40379914e5d18dddb893b4dc5a28f` with `mduuid/2c61b08d-cb1f-4c2c-8ce0-eaea15af32fb` and then re-ran grub-install on all member drives. Where it is getting this old b1c* address I have no clue.
I even tried installing a SATA drive on /dev/sda, outside of the array, and installing grub on it and booting from it. Still, same identical error.
I had Ubuntu installed, i installed Debian and there was no dual boot. So i formated all the hard disk to install only Debian. It installed but at boot i get error: no such device and the grub rescue> prompt. i googled for a solution and nothing worked:
- i tryed reinstalling grub, not worked - i did the windows cd fixmbr trick, not worked - reinstalled debian with fixmbr the first step and nothing - tryed deleting with dd the mbr, not worked - reinstalled grub from debian rescue, not worked
what should i do? i can't access my computer? please tell me how should i fix it? the google guys will kill me because i put their servers on fire
I have and old PC and for last years i had Debian Lenny on that and it was working great but after the Squeeze release, i downloaded the first CD image and did a fresh installation but after this it boots up with no problem (i must say since in Squeeze installation the option of creating a floppy diskette was not working properly i use SuperGrubDisk2 to boot the Debian), but few seconds after logging in, the system hangs (or maybe only the X11 since i use a historic nVidia TNT2 Riva graphic card!).
This topic began in the Debian Development forum here I have successfully completed both the install and the after installation configuration. I have a fully functional system on this little baby, inspite of the fact that wireless (Broadcom bcm4312), ethernet (Realtek) and sound were initially broken.
There is a lot of assistance out there on the web. In the previous thread, I was having trouble installing any debian on a usb stick. The issues that needed resolving were 1. Bad stick
2. Incompatible kernels between boot.img and .iso
3. The method of copying .iso to the stick that finally worked was wget My first successful usb install was Lenny. Even though I upgraded the stock system with lenny-backports, I could not get wireless, ethernet or sound working the only connection I could get to the internet was through my 3g stick and that was not performing up to it's capability. I manually configured wvdial to get that working.
I attempted an upgrade to squeeze several times and each time the upgrade trashed the system. I finally found squeeze boot.img and .iso files from an eee pc blog. This allowed a fresh install of Squeeze and I was making progress. The little atom processor would not handle the b43-fwcutter driver, so I compiled one from the Broadcom site written especially for the atom processor. Now I had cable broadband supplied wireless. I got my ethernet working with help from the Gnome site technical specs on Network Manager. Simply changing ifupdown=false to ifupdown=true in the network manager config file.
Sound was activated by help from a blog entitled "Debian on the Dell Mini 9" My head is spinning now or I would be more specific and instructive on all I did to get this baby up and running. If anyone asks, I may do a how-to.
PS: Posted from that Dell Mini 9 running Debian Squeeze.
Debian Lenny worked just great. That was my first experience of Debian. The installer recognised all my hardware and the system was soon up and running brilliantly with a few tweaks. Confident of Debian's reliability, I decided to move to Debian 6 and did a fresh install, with downloads of the new operating system rather than a distribution upgrade. The installation routines have not worked for the same computer system. I don't know if its hardware not being recognised by Debian 6 that were recognised without a problem by Debian 5??
At first, the boot-up flipped at "Waiting for /dev to be fully populated," there was a kernal panic then Debian disappeared. No signal was sent to the monitor and I had to switch off the computer manually I was able to look into the Debian 6 OS from Arch Linux, installed on different partitions of the same hard-drive. I am able to overwrite the Debian files as root from Arch. My i686 machine has PATA IDE drives.
Why are 2) dbus and the 3) avahi-demon failing? I need to get them started first so that I can get an internet connection and try and correct the problem with X and the wrong Nvidia driver. Is there some configuration I can do either from Arch, where I am now, or the bash prompt on Debian? Thanks in advance.
I haven't used Debian in 1 year or so and would like to know if there is any possible way to do a fresh installation of Debian Lenny or Squeeze (either or) and not install Exim? I get to the package selection section of the Debian Installer and I de-select "Desktop Environment" & "Standard System" so nothing is selected and it still be default installs Exim. Is there a way to omit this from the install?
My laptop is Toshiba Portege 2000. Every time after I installed new ubuntu release, I have to replace the xorg.conf to fix the resolution problem b/c I got 800 x 600 screen only. However, after the 10.04 installation. I only got 1/2 of the screen of resolution. I cannot even see most of my terminal screen.
I go to the image site for ia64 (given that my machine has an Intel Atom N450) and put the mini.iso and netboot.tar.gz files on the key, then plug it into the machine and attempt to boot. It doesn't get recognized.
On my squeeze OS I have texlive-latex3 installed and I wanted to install revtex package of the American Physical Society. While trying to install I was prompted to run #unzip revtex4-1-tds.zip -d /usr/local/texlive/texmf-local/ However my machine does not have /usr/local/texlive/texmf-local/ Instead it has /usr/local/share/texmf/ Will it be all right if I insert this location after -d ?
Can't understand what's going on... Running 'apt-get update' I see that diffs are downloading with a normal speed (11.3 Mbyte by 49 seconds = ~ 227 Kbyte/sec - it's OK, my 'up' limit is 384 Kbyte/sec). But - running 'apt-get dist-upgrade' I see that packages are downloading w/ around 4000 byte/sec. WTF? What's the difference between downloading packages' diffs and packages themselves?
I've changed 6 mirrors - from oficcial (ftp.us.debian.org) to local (ftp.mgts.by). I've tried netselect-apt - no result. Still normall speed on 'apt-get update' and terrifying speed on 'apt-get dist-upgrade'.
Are there any special steps I'd need to take to install Squeeze AMD64 on a server with two quad-core Xeons? I had no issues installing Server 2003 x64 and XP Pro x64 on the box, but I seem to remember seeing something somewhere about XenServer in the kernel images.
I installed sqeeze on a netbook. Having no optical drive, I created a usb install disk with unetbootin on a laptop running Squeeze stable and the "Debian 6.0.1a DVD 1" iso. Much to my suprise it installed KDE. I expected, and wanted, Gnome. At the tasksel section I checked off "Graphical Desktop Env", "Laptop", and "Standard Sysytem Utilities". I found a similar post regarding this: viewtopic.php?f=17&t=60040 But in this case the OP installed with a netinstall iso and concluded a faulty mirror was the cause. This doesn't make sense in my case as I was using a DVD image which contains, afaik, Gnome, XFCE, and KDE
There surely must be a way to explicitly choose which desktop env. one wants installed. I realize this can be done by doing a base install and using apt-get; but I'm thinking there must be a simpler way using the installer. I tried the "Expert" install and only saw the generic "Graphical Desktop" option again. I figure I must be missing something somewhere. Also, can I get apt-get to recognize my unetbootin stick as a source to fetch from? I tried apt-cdrom and different entries in sources.list but I can't figure it out. It seems wasteful to me to download hundreds of MBs of packages from a mirror when I have them locally.
I'm new to the Debian, but not to Linux. I've previously used Ubuntu for a few years, so I know something about how a successful installation should look like. I'm currently using Windows 7.
I downloaded the debian-6.0.3-amd64-gnome-netinst.iso from [URL] ...., and then made a USB pendrive using the Windows version of Unetbootin. The MD5 sum for the .iso-file was the correct one, b663727d7f5b572c329cea8e2ff5e29c.
I used the usual non-graphical setup, without any special options. The installation process went without hiccups until the "Starting up the partitioner" -screen freezes at "Scanning disks...". The bar stops at 50%. It never progresses any farther, even after an hour. It doesn't give any errors either. After I pressed Alt+F4, the last lines were:
Code: Select allpartman: No matching physical volumes found partman: No volume groups found partman: Reading all physical volumes. This may take a while... partman-lvm: No volumegroups found
Exactly the same happens with firmware-6.0.3-amd64-netinst.iso too, or any of the live versions I tried. The result of graphical installation was also nothing. The USB pendrive created by LinuxLive USB Creator was nonoperative in exactly the same way.
The computer is brand new, without any previous OS installations. My desktop computer has the following parts:
I've just setup a fresh installation of Debian Squeeze and am trying to configure the firewall. I ran a search for iptables and got the following results:
When I run an iptables command to add a rule and reboot the new configuration is lost even after I have run the iptables-save command. I can't work out where the iptables config file is/should be stored so I could try editing the file with vi.
When installing squeeze from either a dvd or cd (i've burned loads to see if it was the problem) my computer goes through the installation, until the dreaded step of "selecting and installing software" where the installation stops, and my computer turns itself off because of a kill signal sent to everything. I've tried booting with fb=false, and for some reason acpi=off, and neither of them solved the problem (acpi=off caused my laptop to turn off unexpectedly earlier) (HP 6735s, AMD64 using Turion X2, 4GB Ram)
A Linux user for about 10 years, distro hopping for half of them. Finally found peace with PCLinuxOS (great distro), and MintLinux. When Mint went over to Debian, I thought why not try the original, so here I am.Booted the dvd, checked everything was working well (excellently, actually), and started the install over an existing PCLinuxOS system (dual booting with XP). First time installed while inside the gnome system, from the desktop icon, second and subsequent times from the welcome screen after boot (only text modes were available).In all cases, everything goes fine until I partition and install the packages. Partitioning is no secret to me, unless there is a "Debian way" of doing it: went through "guided partitioning," and chose the existing PCLinuxOS partitions, 37 Gb for /, ext3 (tried ext4 later with same results), and 2 Gb for swap, both on sda (sda1 and sda5). This is a full hard-disk, just for Linux. The other disk is for XP (sdb).
Tried formatting existing partitions, erasing contents of disk, and keeping as is. In all cases, when partitioning is done, the system installation fires up and I see all packages being transferred (up to 100%). Then I have a pop-up window telling me to continue to package manager, which I do, but then I get a message saying that I am trying to install on an "unclean target," over an existing installation (even after fully erasing the disks). It asks whether to continue or not and, whatever I do, I'm taken back to system install again, and see the progress go up to 100% and the same question again.
If I go back to the install menu and ignore the message, jumping to installing grub, I get an error message saying that grub install has failed, and that's it. I can't progress further because of these error messages.If I ignore all and boot without the live dvd, I get a prompt and nothing else, and I can't even use XP. Basically, I'm stuck unless I install another distro again to have a working system.First searched this forum and Google to get answers to this problem, but couldn't find anything applicable to my case.
I am trying to install Squeeze on a HP mini netbook. I have been trying to make a USB to netinstall Squeeze and cannot get it right. I cannot get past the message SYSLINUX 4.02 debian-2010.............. on booting.
I have tried to make the netinstall usb from this [URL] dInstaller I am also trying to understand this [URL] I have also tried using Unetbootin. Nothing works so far. Some simple steps to make a workable USB.
I am currently running 32 bit ubuntu in my PC with 2.5 GB RAM, Intel Pentium Dual Core inside. I am coming to debian soon. I will be installing 64 bit squeeze. Now I have 3 GB of swap space. I do satellite image processing. Therefore what is the recommended swap space for me with the kind of work I do. RAM is in very small amount but as of now I have to stay with it.
Also I am interested to know would KDE be an overkill for my machine. Will I run short of memory when I start image processing?
