[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Cannot boot after sarge->etch upgrade



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Douglas,

Yes, by "combined" mode I mean BIOS parameters for SATA, but as far as I
understand in this mode sata drives should appear as sd* and pata as hd*
 (at least this was true for sarge).

Strangely enough I was able to boot using systemresquecd-x86-0.3.0 in
this mode, and all my hard disks were accessible.

Anyway, now I'm thinking about installing etch from the scratch on this
server because I've got problems with mysql (it wouldn't start as well
with strange messages:

glenfiddich:~# /etc/init.d/mysql start
Starting MySQL database server: mysqld...failed.
        Please take a look at the syslog.
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)'
Check that mysqld is running and that the socket:
'/var/run/mysqld/mysqld.sock' exists!

glenfiddich:~# tail /var/log/syslog
Jan  9 17:50:02 glenfiddich /etc/init.d/mysql[6237]: 0 processes alive
and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping'
resulted in
Jan  9 17:50:02 glenfiddich /etc/init.d/mysql[6237]:
^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Jan  9 17:50:02 glenfiddich /etc/init.d/mysql[6237]: error: 'Can't
connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)'
Jan  9 17:50:02 glenfiddich /etc/init.d/mysql[6237]: Check that mysqld
is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Jan  9 17:50:02 glenfiddich /etc/init.d/mysql[6237]:

and with gforge:

glenfiddich:/var/log# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
The following packages will be upgraded:
  gforge-common
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
508 not fully installed or removed.
Need to get 0B/1009kB of archives.
After unpacking 4002kB of additional disk space will be used.
Do you want to continue [Y/n]?
Preconfiguring packages ...
(Reading database ... 67787 files and directories currently installed.)
Preparing to replace gforge-common 3.1-31sarge1 (using
.../gforge-common_4.5.14-19_all.deb) ...
Unpacking replacement gforge-common ...
dpkg: error processing
/var/cache/apt/archives/gforge-common_4.5.14-19_all.deb (--unpack):
 trying to overwrite `/usr/share/man/man1/cvssh.1.gz', which is also in
package gforge-cvs
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/gforge-common_4.5.14-19_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

So, I think it would be better to reinstall etch...

Kind regards,

Vladimir.


Douglas Tutty wrote:
> 
> Hi Vladimir,
> 
> Please pardon my ignorance.  I don't understand "combined mode".  As I
> understand it, Sarge would only see some SATA drives and lable them hd*
> whereas Etch sees most SATA drives and lables them sd*
> 
> If by combined mode you mean that the BIOS is making the SATA drives
> appear as PATA drives, then perhaps this doesn't work with Etch.
> 
> What you probably want is the SATA drives to look like SATA drives and
> the PATA drives to look like PATA drives.  Then change your root= kernel
> parameter to point to the correct device and change /etc/fstab.
> 
> What you may need to do is capture the kernel messages as they scroll by
> to see what drives it finds and what it calls them.  If this scrolls by
> the screen too quickly, I would suggest either using a serial console to
> capture it or adding a console=lp (see the relavent HOWTOs) to output to
> a printer (note that the order of console parameters is important so
> that you can still input from your keyboard).
> 
> I hope this helps.
> 
> Doug.
> 
>  
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFo6zV2LrwehIvHEQRAqxTAJ45CP4TtVA00KYkinSCvGfBeko5rQCdHYNS
DEZHE8oga3y+EaZrXv8c808=
=/Rd/
-----END PGP SIGNATURE-----



Reply to: