LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-15-2012, 05:00 AM   #1
dogbird
Member
 
Registered: Nov 2004
Location: oklahoma
Distribution: slackware 9.0
Posts: 98

Rep: Reputation: 15
Angry I have 13.37 and it is broken in my system.


Infact I have a standalone system on an IDE drive but the installation says it is a scuzi drive. Now I have used scuzi drives before. but this is an IDE and a sata swap disk. I cannot boot my standalone system because the names are mangled. I cant find an /dev/hda1 anywhere during the setup. It thinks is have a sbda1 or sadb1 which are both IDE drives and not S anything. If I try to use a boot disk and say root=/dev/hda1 the setup crashes. other wise the boot sequence looks for Sbda1 and crashes. I have 13.0 and am considering reinstalling.

 
Old 05-15-2012, 05:08 AM   #2
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 875

Rep: Reputation: 282Reputation: 282Reputation: 282
ftp://ftp.slackware.com/pub/slackwar..._AND_HINTS.TXT

Quote:
*** LIBATA SWITCHOVER ***

The "old" ide subsystem in the the linux kernel is now deprecated in favor
of the newer libata subsystem, and this affects the naming of device nodes
for almost all types of disk drives -- hard drives in particular will now
have an "sd" named node. The following information should allow you to
handle that changeover gracefully.

1. Upgrade the kernel and kernel-modules packages normally.

2. Edit /etc/fstab to reflect the change from hd* to sd*.

If you have multiple SATA devices, and especially if you have some of
both hd* and sd* devices present already, then you're basically going
to be playing a guessing game right now, and you probably want to
consider using some of the persistent symlinks in the /dev/disk/by-*/
directories instead of raw device nodes -- for example, the links in
/dev/disk/by-id/ should always point to the same device, even if its
raw device node changes from e.g. sda1 to sdc1 or some such across
reboots.

* If you are using one of the generic kernels (requiring an initrd),
then use the sd* name for the root device when creating the image.

* You will almost surely want to remove the udev rules file for cdrom
devices (it will be regenerated on the next boot with correct
information reflecting the new libata stuff):
# rm -f /etc/udev/rules.d/70-persistent-cd.rules

* Speaking of optical devices, if you have multiple disk drives and an
optical drive using the old ide subsystem, then be aware that the
optical drive will get a /dev/sr* name instead of /dev/sd* -- this is
relevant because you might see something like this (if your optical
drive is currently /dev/hdb):

Old Name --> New Name
/dev/hda /dev/sda
/dev/hdb /dev/sr0
/dev/hdc /dev/sdb

3. Run lilo. Note that you have made no edits at all to it yet, unless
you needed to edit it for the new kernel. Specifically, do not make
any changes with respect to hd* --> sd*.

4. Reboot. At the lilo prompt, press <TAB> and add an append for the
real root device (which will no longer be /dev/hd*). For example, if
the old root device was /dev/hda1, and it will now be /dev/sda1, and
the name of your kernel image is "Linux" then you would do this:

Linux root=/dev/sda1

5. Once the system comes back up, then fix /etc/lilo.conf, run lilo, and
reboot again to be sure everything is correct.
 
Old 05-15-2012, 05:10 AM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
Starting with Slackware 13.1 the old ATA subsystem in the kernel was deprecated. All drives (even IDE and SATA) are now handled by the SCSI subsystem.
Read the CHANGES_AND_HINTS file from Slackware 13.1, for example this online version: http://slackware.osuosl.org/slackwar..._AND_HINTS.TXT and search for the "libata switchover" section:
Code:
*** LIBATA SWITCHOVER ***

The "old" ide subsystem in the the linux kernel is now deprecated in favor
  of the newer libata subsystem, and this affects the naming of device nodes
  for almost all types of disk drives -- hard drives in particular will now
  have an "sd" named node.  The following information should allow you to
  handle that changeover gracefully.

  1. Upgrade the kernel and kernel-modules packages normally.
     
  2. Edit /etc/fstab to reflect the change from hd* to sd*.
    
     If you have multiple SATA devices, and especially if you have some of
     both hd* and sd* devices present already, then you're basically going
     to be playing a guessing game right now, and you probably want to
     consider using some of the persistent symlinks in the /dev/disk/by-*/
     directories instead of raw device nodes -- for example, the links in
     /dev/disk/by-id/ should always point to the same device, even if its
     raw device node changes from e.g. sda1 to sdc1 or some such across
     reboots.
 
     * If you are using one of the generic kernels (requiring an initrd),
       then use the sd* name for the root device when creating the image.
     
     * You will almost surely want to remove the udev rules file for cdrom
       devices (it will be regenerated on the next boot with correct
       information reflecting the new libata stuff):  
         # rm -f /etc/udev/rules.d/70-persistent-cd.rules 

     * Speaking of optical devices, if you have multiple disk drives and an
       optical drive using the old ide subsystem, then be aware that the
       optical drive will get a /dev/sr* name instead of /dev/sd* -- this is
       relevant because you might see something like this (if your optical
       drive is currently /dev/hdb):
 
         Old Name --> New Name 
         /dev/hda     /dev/sda
         /dev/hdb     /dev/sr0
         /dev/hdc     /dev/sdb
 
  3. Run lilo.  Note that you have made no edits at all to it yet, unless
     you needed to edit it for the new kernel.  Specifically, do not make
     any changes with respect to hd* --> sd*.
 
  4. Reboot.  At the lilo prompt, press <TAB> and add an append for the
     real root device (which will no longer be /dev/hd*).  For example, if
     the old root device was /dev/hda1, and it will now be /dev/sda1, and
     the name of your kernel image is "Linux" then you would do this:

       Linux root=/dev/sda1

  5. Once the system comes back up, then fix /etc/lilo.conf, run lilo, and 
     reboot again to be sure everything is correct.
Eric

Edit: wildwizard was faster!
 
Old 05-15-2012, 05:11 AM   #4
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,097

Rep: Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174
there's no more /dev/hdX since kernel 2.6.33, now you got only /dev/sdX, for ide, sata and scsi drives.

EDIT: sorry, I was phone.

Last edited by ponce; 05-15-2012 at 11:01 AM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with libgio-2.0.so.0 (I've broken my system) Sanva Linux - Software 3 04-07-2011 06:30 AM
fix a debian broken system el_pajaro! Debian 6 06-03-2009 01:23 AM
Broken build system squaregoldfish Linux - Software 2 10-16-2008 04:02 PM
I seem to have broken my system (compiler perhaps) kummiliim Linux - Software 5 02-19-2008 12:13 PM
System Broken after update potsilui Linux - Newbie 6 04-17-2005 06:35 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:44 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration