[solved] Newly installed Squeeze cannot boot

Help with issues regarding installation of Debian

[solved] Newly installed Squeeze cannot boot

Postby oldboy » 2011-01-08 21:33

[This thread is a continuation from topic "Lenny to Squeeze Upgrade". This thread is started because the nature of the problem is now different, it is not an upgrade anymore. I started a new install of squeeze, and it would not boot]

cynwulf wrote:What did you download in order to installed?
I used netinst businesscard. md5sum ckecked out
Checked the md5sum of the downloaded .iso image?

Regardless try downloading CD1, check the md5sum and then burn at the slowest speed. http://cdimage.debian.org/cdimage/weekl ... 64/iso-cd/

Try again and see if it makes any difference.

I followed your link and downloaded and check md5sum. Installed it. It boots into the error and trace pages again. I restarted my pc and it booted ok and functions properly. Then I rebooted into my old lenny, and it functions as usual. I booted into squeeze again, and it would not boot, giving the same error trace.

Actually I have re-installed 2 times. First time was using these partitions:
ext3 /boot
ext4 /
ext4 /home
swap (from the lenny installation)
grub was installed in MBR

After trying many times to boot with no sucess, I reinstalled again, except this time I am using all ext3.

Could the problem be the swap which I used for lenny? Squeeze does not boot after I booted lenny.
Last edited by oldboy on 2011-01-17 23:12, edited 1 time in total.
This oldboy has a lot of time in his hands
Linux slows down my Alzheimer and dementia
oldboy
 
Posts: 654
Joined: 2007-08-09 12:45

Re: Newly installed Squeeze cannot boot

Postby oldboy » 2011-01-09 02:02

Here is any update:
I re-installed again, using
ext3 /boot
ext4 /
ext4 /home
swap (new, not the one used by lenny)

After install, and reboot, goes into errors and tracing. After many tries, finally booted into terminal mode (no gdm)
There are 2 error:
Code: Select all
Starting Avahi mDNS/DNS-SD Deamon: avahi-daemon failed
Starting Samba daemon: nmbd smbd.
saned disabled; edit /etc/default/saned
Startpar: service(s) returned failture: dbus...failed

I can login and look at dmesg and found these suspicious items
Code: Select all
PM: Checking hibernation image
PM: Error -22 checking image file
PM: resue from disk failure
input: HDA Digital PCBeep as /devices/pci0000:00/..../input/input8
r600_cp: Failed to load firmware "radeo/RV770_pfp.bin
[drm:rv770_startup] *ERROR* Failed to load firmware!

Looked into /etc/fstab, seems an error in mounting sda9 which is the / partition:
Code: Select all
/ was on /dev/sda9 during installation
UUID=d8........../ ext4 errors=remount-ro 0 1

/boot and /home and swap seems to be ok.
Since lenny was not on the grub menu, I typed os-prober:
Code: Select all
#os-prober
/dev/sda1:windows7 (loader):windows:chain
[2723.931695] EXT3-fs:write access unavailable, cannot procees.

I am going to take a look at the partitions with PartMagic, and see if anything show sup there.
This oldboy has a lot of time in his hands
Linux slows down my Alzheimer and dementia
oldboy
 
Posts: 654
Joined: 2007-08-09 12:45

Re: Newly installed Squeeze cannot boot

Postby llivv » 2011-01-09 09:30

After cynwulf fixed your install in our first threeway hand holding session, did you ever read or try his followup instructions, to stabilize your machine?http://forums.debian.net/viewtopic.php?f=17&t=58921&start=30#p341864
if not please do soon, OK
If you still think there is something wrong with your system after doing that, post um....
in the kitchen with Julia ....
[...]
Get on the D bus to B Can ....
[...]
User avatar
llivv
 
Posts: 5508
Joined: 2007-02-14 18:10
Location: morrison hotel

Re: Newly installed Squeeze cannot boot

Postby cynwulf » 2011-01-09 11:51

Your partitions are messed up and judging by the last error mounted read only. The upgrade would have been much easier...
cynwulf
 
Posts: 2397
Joined: 2008-09-25 08:49

Re: Newly installed Squeeze cannot boot

Postby oldboy » 2011-01-09 15:19

llivv wrote:After cynwulf fixed your install in our first threeway hand holding session, did you ever read or try his followup instructions, to stabilize your machine?http://forums.debian.net/viewtopic.php?f=17&t=58921&start=30#p341864
if not please do soon, OK
If you still think there is something wrong with your system after doing that, post um....

The same type of error I see there in the upgrade following cynwulf instructions. That is when I gave up on upgrade and did the new install.

@cynwulf
Yes, the partitions are suspects. So, I used pmagic to format those patitions again and ckecked the health of HDD, and re-install. It works perfect, booted right after the install. But, after I restart and boot into lenny, and then restart and boot into squeeze, it stalls again like it always did. This morning, I tried it again the first thing to boot, it stalled at
Code: Select all
setting preliminary keymap


One question about partitions. I have this
partition 1: primary ntfs (reserved for bios recovery)
partition 2: primary ntfs (windows7)
partition 3: primary ext3 /boot for lenny
partition 4: extended
partition 5: ext3 /root for lenny
partition 6 ext4 /home for lenny
partition 7 swap
partition 8 ext3 /boot for squeeze
partition 9 ext4 / for squeeze
partition 10 ext4 /home for squeeze

I cannot find info on how many extended partitions are allowed. After the latest install, it re-started and booted with no problem. Only after I have gone to lenny and back that it does not boot. So, something there is confusing it.
This oldboy has a lot of time in his hands
Linux slows down my Alzheimer and dementia
oldboy
 
Posts: 654
Joined: 2007-08-09 12:45

Re: Newly installed Squeeze cannot boot

Postby nadir » 2011-01-09 18:58

PM: Checking hibernation image
PM: Error -22 checking image file
PM: resue from disk failure

Have a look here:
http://blog.dvl.pl/article/2009/10/02/r ... vice-file/
(i have not had the error-messages you have got, but exaclty the one from the link. A short look won't hurt)

Post /etc/fstab.
When changing from ext3 to ext4 i often forget to change that.
Post "blkid" and "fdisk -l"


giving the same error trace.

I reread the other thread, and still am not sure what exactly the errors are.
What are they, exactly?

To each his own, but i think three OS on one PC is ...mmhhhh... a waste. In the long run 2 is more than enough. And less trouble.
"I am not fine with it, so there is nothing for me to do but stand aside." M.D.
User avatar
nadir
 
Posts: 5965
Joined: 2009-10-05 22:06
Location: away

Re: Newly installed Squeeze cannot boot

Postby llivv » 2011-01-09 19:54

If you don't understand this just ignore it..
imo you will reduce your system complexity by a thousand percent if you don't use separate /boot and /home partitions for squeeze....
Yeah, I'm gonna have to go back and reread the first thread too...
in the kitchen with Julia ....
[...]
Get on the D bus to B Can ....
[...]
User avatar
llivv
 
Posts: 5508
Joined: 2007-02-14 18:10
Location: morrison hotel

Re: Newly installed Squeeze cannot boot

Postby oldboy » 2011-01-09 21:56

nadir wrote:
PM: Checking hibernation image
PM: Error -22 checking image file
PM: resue from disk failure

Have a look here:
http://blog.dvl.pl/article/2009/10/02/r ... vice-file/
(i have not had the error-messages you have got, but exaclty the one from the link. A short look won't hurt)
The is no /etc/uswssusp.conf
Post /etc/fstab.
When changing from ext3 to ext4 i often forget to change that.

# / was on /dev/sda9 during installation
UUID=..../ ext4 errors=remount-ro 0 1
/boot was on /dev/sda8 during installation
UUID=..../boot ext3 default 0 2
/home was on /dev/sda10 during installation
UUID=... /home ext4 defaults 0 2
swap was on /dev/sda7 during installation
UUID=... none swap sw 0 2

Post "blkid" and "fdisk -l"
Blkid ouput:
/dev/sda1 label="system reserve" UUID...Type="ntfs"
/dev/sda2 UUID...type="ntfs"
/dev/sda3 UUID...SEC_TYPE="ext2" TYPE="ext3
/dev/sda5 UUID...same as above line
/dev/sda6 UUID...same as above line
/dev/sda7 UUID...TYPE="swap"
/dev/sda8 UUDI...TYPE="ext3"
/dev/sda9 UUID... TYPE="ext4"
/dev/sda10 UUID...Type="ext4"

fdisk -l gives ouput like blkid, except giving start and end cylinders, e.g.

/dev/sda8 * 12749 12779 242688 83 Linux {* indicates boot}


giving the same error trace.

I reread the other thread, and still am not sure what exactly the errors are.
What are they, exactly?
As far as I can tell, after reboot into recovery mode, it stalled, I hit Control C, and entered password, it gave me the terminal mode, and I managed to do dmesg | less and listed the suspicious lines I thought were errors
To each his own, but i think three OS on one PC is ...mmhhhh... a waste. In the long run 2 is more than enough. And less trouble.


@llivv
I will try re-install tonite, without /boot and /home and see what happens. Does it mean installing in one single partition?
Last edited by oldboy on 2011-01-09 22:18, edited 1 time in total.
This oldboy has a lot of time in his hands
Linux slows down my Alzheimer and dementia
oldboy
 
Posts: 654
Joined: 2007-08-09 12:45

Re: Newly installed Squeeze cannot boot

Postby oldboy » 2011-01-09 22:16

Here is some more info. I booted into recovery mode. It seems to boot ok, and ask for root password, but before I can type it, it goes on to trace:

Code: Select all
[code]general protection fault: 0000 [#2] SMP
last sysfs file: /sys/devices/i2c-3/name
cpu 1
module linked in: fuse ext3 jbd firwire....
Pid: 749, comm:usb-storage Tainted: G  D C 2.6.32-5-amd64 #1 EX58-UD3R {this is code name for my motherboard}
[/code]

The it gives a series of traces. I hit control-c to return to "Give password for maintenance"
But, I do not have any usb storage. I do have any usb storage attached.
This oldboy has a lot of time in his hands
Linux slows down my Alzheimer and dementia
oldboy
 
Posts: 654
Joined: 2007-08-09 12:45

Re: Newly installed Squeeze cannot boot

Postby oldboy » 2011-01-10 01:02

Update: I have changed the /etc/fstab table to replace the error... by defaults. Reboot. Same thing, stalled.
After many tries, I am now in squeeze :oops: . Do not know what happened. While I am in, what can I do to check out this installation. What can I do to see and change the resume image?
In the mean time, I am not going to reboot until I have some clue as to what can go wrong.
This oldboy has a lot of time in his hands
Linux slows down my Alzheimer and dementia
oldboy
 
Posts: 654
Joined: 2007-08-09 12:45

Re: Newly installed Squeeze cannot boot

Postby nadir » 2011-01-10 09:50

Things like:
Code: Select all
UUID=..../ ext4 errors=remount-ro 0 1

and
Code: Select all
/dev/sda2 UUID...type="ntfs"

are not exact, but the contrary of being exact. You have removed the interesting part.
Do copy and paste (not now, whenever you use commands/commandline).
Also use code tags, it is much easier to read.
I assume all of that is correct. But it never hurts to let other people have a short glance.


Example:
Code: Select all
# blkid
/dev/sda7: UUID="54d28392-46af-4831-8908-e7c959dbd283" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda5: UUID="98c46bb6-3778-4b1f-9da7-e80481c4a5a9" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: UUID="093f028f-9fb2-4f86-b265-3abd4a76bb09" TYPE="swap"
/dev/sda1: UUID="ea285dba-0bce-455f-b0a5-e51ac4265bbe" TYPE="ext4"
/dev/sda6: UUID="3cbc1510-070f-4c0e-80a4-a64ebb907717" TYPE="ext4"
/dev/sda8: UUID="0c86e42f-1eca-480b-a66d-8ec15a539ce4" TYPE="ext4"
/dev/sdb1: UUID="3cdbe83c-cd13-471b-be6e-dc2ec1333c90" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: UUID="91d0ce84-697d-4cb9-8502-16e57308a72f" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdd1: UUID="1b2793e9-4870-48e1-b677-4410bcfe6af3" SEC_TYPE="ext2" TYPE="ext3"


Code: Select all
# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda1       /               ext4   noatime,errors=remount-ro 0       1
 UUID=ea285dba-0bce-455f-b0a5-e51ac4265bbe      /               ext4   noatime,errors=remount-ro 0       1
# /dev/sda5       /home           ext3   noatime,defaults        0     0
UUID=98c46bb6-3778-4b1f-9da7-e80481c4a5a9 /home ext3 noatime,defaults,user_xattr 0 0
# /dev/sda6      /home/m1arkust/Music ext4 noatime,defaults    0   0   
UUID=3cbc1510-070f-4c0e-80a4-a64ebb907717      /home/m1arkust/Music ext4 noatime,defaults    0   0   
# /dev/sda2      none              swap    sw              0       0
UUID=093f028f-9fb2-4f86-b265-3abd4a76bb09     none              swap    sw              0       0
"I am not fine with it, so there is nothing for me to do but stand aside." M.D.
User avatar
nadir
 
Posts: 5965
Joined: 2009-10-05 22:06
Location: away

Re: Newly installed Squeeze cannot boot

Postby oldboy » 2011-01-10 14:56

Thanks nadir. I was in terminal mode with no access to iceweasel, so had to take the shortcut of typing the blkid, fstab. Here they are:
Code: Select all
 blkid
/dev/sda1: LABEL="System Reserved" UUID="00C0FAFDC0FAF7AC" TYPE="ntfs"
/dev/sda2: UUID="781E1F201E1ED74A" TYPE="ntfs"
/dev/sda3: UUID="b4c78567-d138-48e2-be49-0e56535775d4" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda5: UUID="80c40b11-a503-411f-9198-a0afa1b82131" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda6: UUID="16c6104b-79ea-4869-8ada-142be2f4e537" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: UUID="488d32d5-49d1-4ce5-84d0-337232a9b7a5" TYPE="swap"
/dev/sda8: UUID="b22b5916-de5e-4cc4-a9d0-c560ec0e7083" TYPE="ext3"
/dev/sda9: UUID="c7fd3ee4-96f7-4df2-a6e2-b717c136af3e" TYPE="ext4"
/dev/sda10: UUID="5a7d759c-7255-4458-a681-54c1ad36c210" TYPE="ext4"


Code: Select all
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda9 during installation
UUID=c7fd3ee4-96f7-4df2-a6e2-b717c136af3e /               ext4     errors=remount-ro     0       1
# /boot was on /dev/sda8 during installation
UUID=b22b5916-de5e-4cc4-a9d0-c560ec0e7083 /boot           ext3    defaults        0       2
# /home was on /dev/sda10 during installation
UUID=5a7d759c-7255-4458-a681-54c1ad36c210 /home           ext4    defaults        0       2
# swap was on /dev/sda7 during installation
UUID=488d32d5-49d1-4ce5-84d0-337232a9b7a5 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0


I have changed /dev/sda9 back to ext4 "errors=remount-ro" as it was.
This oldboy has a lot of time in his hands
Linux slows down my Alzheimer and dementia
oldboy
 
Posts: 654
Joined: 2007-08-09 12:45

Re: Newly installed Squeeze cannot boot

Postby llivv » 2011-01-10 17:02

oldboy wrote: Do not know what happened. What can I do to see and change the resume image?
The resume image is in the swap partition... the resume image is probably getting erased when you boot to lenny..

When you are ready - instead of booting to lenny try rebooting back into squeeze , so the resume image is not erased by booting into lenny or XP...

df -hlT
is useful and asked for by an installation report if you do one
apt-get install installation-report
some people like to use
glx-info
glx-gears
and if you have an
/etc/X11/xorg.conf
you want to know what is in that as well as checking
/var/log/Xorg.0.log

To see what is happening with KMS at boot I use
dmesg | egrep "onsole|fb|agp|drm"
or
dmesg | grep onsole # gets booth console and Console entries
dmesg | grep fb
dmesg | grep agp
dmesg | grep drm

this is what mine looks like on an old pentium 4 with intel graphics
radeon and nouveau output a lot more than this...
root@sb7:/home/len#dmesg | egrep "onsole|fb|agp|drm"
[ 0.000000] kernel direct mapping tables up to 377fe000 @ 17fb000-1800000
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.175526] pnp 00:08: [mem 0xffb80000-0xffbfffff]
[ 0.554380] efifb: probing for efifb
[ 0.554640] efifb: framebuffer at 0xf0000000, mapped to 0xf8080000, using 1216k, total 1216k
[ 0.554649] efifb: mode is 640x480x32, linelength=2560, pages=1
[ 0.554654] efifb: scrolling: redraw
[ 0.554660] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.567367] Console: switching to colour frame buffer device 80x30
[ 0.580312] fb0: EFI VGA frame buffer device
[ 0.935308] Linux agpgart interface v0.103
[ 0.943132] agpgart-intel 0000:00:00.0: Intel 865 Chipset
[ 0.950885] agpgart-intel 0000:00:00.0: detected gtt size: 131072K total, 131072K mappable
[ 0.966313] agpgart-intel 0000:00:00.0: detected 16384K stolen memory
[ 0.976317] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xf0000000
[ 1.841771] [drm] Initialized drm 1.1.0 20060810
[ 1.954831] [drm] initialized overlay support
[ 2.039243] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver
[ 2.041209] Console: switching to colour dummy device 80x25
[ 2.052096] Console: switching to colour frame buffer device 160x64
[ 2.057361] fb0: inteldrmfb frame buffer device
[ 2.057392] drm: registered panic notifier
[ 2.057559] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 48.639013] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking



it's a lot to try to digest so bite off what you think you can chew and enjoy it.....
spit what you can't swallow or tastes weird.... :wink:
in the kitchen with Julia ....
[...]
Get on the D bus to B Can ....
[...]
User avatar
llivv
 
Posts: 5508
Joined: 2007-02-14 18:10
Location: morrison hotel

Re: Newly installed Squeeze cannot boot

Postby nadir » 2011-01-10 18:49

What i see from your output looks ok, not sure though.

About the "resume-from" problem: i simply removed the package: uswsusp
and my problem was gone. But i wouldn't know if that is your problem at all (the link above contains some further details, btw).
"I am not fine with it, so there is nothing for me to do but stand aside." M.D.
User avatar
nadir
 
Posts: 5965
Joined: 2009-10-05 22:06
Location: away

Re: Newly installed Squeeze cannot boot

Postby oldboy » 2011-01-10 19:15

nadir wrote:What i see from your output looks ok, not sure though.

About the "resume-from" problem: i simply removed the package: uswsusp
and my problem was gone. But i wouldn't know if that is your problem at all (the link above contains some further details, btw).


Thanks. I checked, there is no uswsusp package installed.

@llivv:
Thanks. I did dmesg | grep onsole.
It returned with
Code: Select all
 dmesg | grep onsole
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    4.414753] Console: switching to colour frame buffer device 240x75

Not sure what all these mean.

I'll restart now and see what happens.
edit: It booted back to squeeze ok. My Ralink wireless is working also.
I'll restart and boot to lenny and see what happens.
This oldboy has a lot of time in his hands
Linux slows down my Alzheimer and dementia
oldboy
 
Posts: 654
Joined: 2007-08-09 12:45

Next

Return to Installation

Who is online

Users browsing this forum: No registered users and 39 guests

fashionable