Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
08-17-2014, 12:42 AM
|
#1
|
LQ Newbie
Registered: Mar 2013
Location: /bin/bash
Distribution: Slackware
Posts: 27
Rep:
|
Kernel Panic with generic kernel on Dell poweredge 2850 Slackware 14.1
After installing slackware 14.1 with LVM and making an initrd.gz for the generic kernel on my dell poweredge 2850 I had a kernel panic. Searched around for similar errors and checked LQ with no luck. Reinstalled without LVM and same error.
Huge boots fine with no issues, I don't know if maybe something is missing from the mkinitrd_command_generator.sh output or the generic kernel?
The system is installed on a raid 1 array with multiple partitions for boot, swap, / , tmp, var, and home.
This is the error I get
http://31.media.tumblr.com/3704ba874...l5eo1_1280.jpg
mkinitrd_command_generator.sh output edited to include ext2 for the boot partiton
Code:
mkinitrd -c -k 3.10.17 -f ext4 -r /dev/sda3 -m megaraid:usbhid:hid_generic:uhci-hcd:mbcache:jbd2:ext2:ext4 -u -o /boot/initrd.gz
lspci gives
Code:
00:00.0 Host bridge: Intel Corporation E7520 Memory Controller Hub (rev 09)
00:02.0 PCI bridge: Intel Corporation E7525/E7520/E7320 PCI Express Port A (rev 09)
00:04.0 PCI bridge: Intel Corporation E7525/E7520 PCI Express Port B (rev 09)
00:05.0 PCI bridge: Intel Corporation E7520 PCI Express Port B1 (rev 09)
00:06.0 PCI bridge: Intel Corporation E7520 PCI Express Port C (rev 09)
00:1d.0 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
01:00.0 PCI bridge: Intel Corporation 80332 [Dobson] I/O processor (A-Segment Bridge) (rev 06)
01:00.2 PCI bridge: Intel Corporation 80332 [Dobson] I/O processor (B-Segment Bridge) (rev 06)
02:0e.0 RAID bus controller: Dell PowerEdge Expandable RAID controller 4 (rev 06)
05:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A (rev 09)
05:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B (rev 09)
06:07.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
07:08.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
09:05.0 Unassigned class [ff00]: Dell Remote Access Card 4 Daughter Card
09:05.1 Unassigned class [ff00]: Dell Remote Access Card 4 Daughter Card Virtual UART
09:05.2 Unassigned class [ff00]: Dell Remote Access Card 4 Daughter Card SMIC interface
09:06.0 IDE interface: Silicon Image, Inc. PCI0680 Ultra ATA-133 Host Controller (rev 02)
09:0d.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] RV100 [Radeon 7000 / Radeon VE]
fstab
Code:
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 1 1
/dev/sda1 /boot ext2 defaults 1 2
/dev/sda5 /var ext4 defaults 1 2
/dev/sda6 /tmp ext4 defaults 1 2
/dev/sda7 /home ext4 defaults 1 2
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro,comment=x-gvfs-show 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
Please and Thank you for any help that you can give.
|
|
|
08-17-2014, 12:52 PM
|
#2
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,220
Rep:
|
Hi, welcome to LQ and this forum.
Here is what I understand.
You have a separate partition for /boot and the initrd is installed there. But /boot being not yet mounted at time of unpacking the initrd, that contains the ext4 module needed to mount /, you can't mount /, thus you don't have access to /mnt.
Long story short: don't make a separate /boot partition or don't put the initrd there.
Also IMHO there are very few use cases that actually need to have separate partitions for /boot, /var, /tmp and /home, but dedicated hard disks.
Last edited by Didier Spaier; 08-17-2014 at 01:07 PM.
|
|
|
08-17-2014, 03:20 PM
|
#3
|
Senior Member
Registered: Sep 2009
Location: Leinster, IE
Distribution: Slackware, NetBSD
Posts: 2,228
|
@ Didier: perhaps he needs a non-RAID /boot partition on each disk to ensure the system boots if one of the disks in the RAID-1 array fails?
@ Dieselchair: do you have support for your RAID card compiled into the kernel, or did you just compile it as a module?
|
|
|
08-17-2014, 04:09 PM
|
#4
|
LQ Newbie
Registered: Mar 2013
Location: /bin/bash
Distribution: Slackware
Posts: 27
Original Poster
Rep:
|
Hello and thank you for the welcome.
Didier that seems like a good cause of my troubles, I'm doing a fresh install right now. This time with only 2 partitions, root and swap.
gezley I'm just using whats on the slack dvd, haven't compiled anything yet
|
|
|
08-17-2014, 04:19 PM
|
#5
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
Quote:
Originally Posted by Didier Spaier
Here is what I understand.
You have a separate partition for /boot and the initrd is installed there. But /boot being not yet mounted at time of unpacking the initrd, that contains the ext4 module needed to mount /, you can't mount /, thus you don't have access to /mnt.
|
His /boot partition is ext2, not ext4, according to his fstab. I'm using a similar setup, without any problems.
|
|
|
08-17-2014, 04:34 PM
|
#6
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,220
Rep:
|
Quote:
Originally Posted by kikinovak
His /boot partition is ext2, not ext4, according to his fstab. I'm using a similar setup, without any problems.
|
I didn't mean that /boot couldn't be mounted without the initrd, but possibly was not mounted soon enough so that the initrd be available, that contains the ext4 module needed to mount /, thus making not possible to access /mnt.
But I certainly admit that this is pure speculation on my part.
As long as the OP's issue will be sorted out one way or another and that I'll have learned something in the process, I'll be happy. If I've to be proved wrong to get that result, so be it
Last edited by Didier Spaier; 08-17-2014 at 04:36 PM.
|
|
|
08-17-2014, 05:31 PM
|
#7
|
LQ Newbie
Registered: Mar 2013
Location: /bin/bash
Distribution: Slackware
Posts: 27
Original Poster
Rep:
|
Well, everything went ok with the reinstall. Until I tried to boot generic. It didn't work Didier it give the same error as in the picture.
|
|
|
08-17-2014, 05:45 PM
|
#8
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,220
Rep:
|
Which partitioning layout did you configure this time? (EDIT: sorry I didn't see your second post). Did you change anything else?
PS If not already done I'd suggest that you put two lilo stanzas in your /etc/lilo.conf: one with the -generic kernel and one with the -huge one. This way you'll be able to get into your system and attach to your next post the relevant part of /var/log messages, i.e. all messages from booting with the -generic kernel till the kernel panic.
Just to make sure: of course you included the line locating the initrd in /etc/lilo.conf?
Last edited by Didier Spaier; 08-17-2014 at 06:33 PM.
Reason: PS added.
|
|
|
08-17-2014, 07:06 PM
|
#9
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
Quote:
Originally Posted by Didier Spaier
Which partitioning layout did you configure this time? (EDIT: sorry I didn't see your second post). Did you change anything else?
PS If not already done I'd suggest that you put two lilo stanzas in your /etc/lilo.conf: one with the -generic kernel and one with the -huge one. This way you'll be able to get into your system and attach to your next post the relevant part of /var/log messages, i.e. all messages from booting with the -generic kernel till the kernel panic.
Just to make sure: of course you included the line locating the initrd in /etc/lilo.conf?
|
If the boot process under generic cannot mount "/", it won't be able to mount /var/log either. There won't be any messages there from the attempt to boot the generic kernel.
|
|
|
08-17-2014, 07:35 PM
|
#10
|
LQ Guru
Registered: Mar 2004
Distribution: Slackware
Posts: 6,571
|
Maybe problem is with megaraid module, not ext4, I see that the hid_generic and uhci-hcd seem to have been loaded with the initrd (if I refer to the picture) so logically the initrd has been loaded as well
With the system running with working kernel, what dmesg says about the raid?
Last edited by keefaz; 08-17-2014 at 07:41 PM.
|
|
|
08-17-2014, 07:52 PM
|
#11
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
I suggest that when the system tells you that it is in RESCUE mode, type the command cat /proc/partitions to find out what partitions it sees at the moment. If that doesn't provide enough information on the problem (or provides no output) then do the following: - Use the installation DVD to boot and mount/chroot into your installed system. Assuming that you create a new directory /mnt/rescue to mount your system from the installation DVD, run the following commands:
- the mount command that mounts your root partition to /mnt/rescue
- mount --bind /proc /mnt/rescue/proc
- mount --bind /sys /mnt/rescue/sys
- mount --bind /run /mnt/rescue/run
- chroot /mnt/rescue
- As root, re-run /usr/share/mkinitrd/mkinitrd_command_generator.sh with the same command line arguments as before.
- Run the command returned by /usr/share/mkinitrd/mkinitrd_command_generator.sh appending the additional arguments of -w 10 which will delay the boot 10 seconds after the modules are loaded. That should give you time to read the results of the module loading and/or take a picture of that output.
- Please tell us what the module loading tells you.
If that doesn't suggest a solution, I would use the installation DVD to re-mount the system using the above mount --bind commands and then edit the file /boot/init-tree/init to add
Code:
cat /proc/partitions
on line 159 and then run the command mkinitrd to re-generate initrd.gz. Reboot and see what partitions are available after the modules load.
|
|
1 members found this post helpful.
|
08-17-2014, 08:12 PM
|
#12
|
LQ Newbie
Registered: Mar 2013
Location: /bin/bash
Distribution: Slackware
Posts: 27
Original Poster
Rep:
|
Didier I didn't change anything else, and huge is included in lilo.conf.
New fstab
Code:
cat /etc/fstab
/dev/sda2 swap swap defaults 0 0
/dev/sda1 / ext4 defaults 1 1
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro,comment=x-gvfs-show 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
keefaz There is a second raid-5 array mostly media and music but it's not mounted yet. Was planing on mounting it after setting up slack.
Code:
dmesg -T | grep -C 7 -i "raid"
[Sun Aug 17 21:02:47 2014] ACPI: bus type PCI registered
[Sun Aug 17 21:02:47 2014] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[Sun Aug 17 21:02:47 2014] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[Sun Aug 17 21:02:47 2014] PCI: Intel Corporation E7520 Memory Controller Hub with MMCONFIG support
[Sun Aug 17 21:02:47 2014] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
[Sun Aug 17 21:02:47 2014] PCI: Using configuration type 1 for base access
[Sun Aug 17 21:02:47 2014] bio: create slab <bio-0> at 0
[Sun Aug 17 21:02:47 2014] raid6: sse2x1 2339 MB/s
[Sun Aug 17 21:02:47 2014] raid6: sse2x2 3476 MB/s
[Sun Aug 17 21:02:47 2014] raid6: sse2x4 3312 MB/s
[Sun Aug 17 21:02:47 2014] raid6: using algorithm sse2x2 (3476 MB/s)
[Sun Aug 17 21:02:47 2014] raid6: using intx1 recovery algorithm
[Sun Aug 17 21:02:47 2014] ACPI: Added _OSI(Module Device)
[Sun Aug 17 21:02:47 2014] ACPI: Added _OSI(Processor Device)
[Sun Aug 17 21:02:47 2014] ACPI: Added _OSI(3.0 _SCP Extensions)
[Sun Aug 17 21:02:47 2014] ACPI: Added _OSI(Processor Aggregator Device)
[Sun Aug 17 21:02:47 2014] ACPI: EC: Look up EC in DSDT
[Sun Aug 17 21:02:47 2014] ACPI: Interpreter enabled
[Sun Aug 17 21:02:47 2014] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130328/hwxface-568)
--
[Sun Aug 17 21:02:47 2014] 0000:09:05.1: ttyS1 at I/O 0xcc80 (irq = 21) is a 16550A
[Sun Aug 17 21:02:47 2014] Floppy drive(s): fd0 is 1.44M
[Sun Aug 17 21:02:47 2014] brd: module loaded
[Sun Aug 17 21:02:47 2014] Compaq SMART2 Driver (v 2.6.0)
[Sun Aug 17 21:02:47 2014] HP CISS Driver (v 3.6.26)
[Sun Aug 17 21:02:47 2014] fnic: Cisco FCoE HBA Driver, ver 1.5.0.22
[Sun Aug 17 21:02:47 2014] fnic: Successfully Initialized Trace Buffer
[Sun Aug 17 21:02:47 2014] Adaptec aacraid driver 1.2-0[30200]-ms
[Sun Aug 17 21:02:47 2014] aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
[Sun Aug 17 21:02:47 2014] scsi: <fdomain> Detection failed (no card)
[Sun Aug 17 21:02:47 2014] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.05.00.03-k.
[Sun Aug 17 21:02:47 2014] Emulex LightPulse Fibre Channel SCSI driver 8.3.39
[Sun Aug 17 21:02:47 2014] Copyright(c) 2004-2009 Emulex. All rights reserved.
[Sun Aug 17 21:02:47 2014] Brocade BFA FC/FCOE SCSI driver - version: 3.1.2.1
[Sun Aug 17 21:02:47 2014] DC390: clustering now enabled by default. If you get problems load
[Sun Aug 17 21:02:47 2014] with "disable_clustering=1" and report to maintainers
[Sun Aug 17 21:02:47 2014] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
[Sun Aug 17 21:02:47 2014] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
[Sun Aug 17 21:02:47 2014] megaraid: probe new device 0x1028:0x0013:0x1028:0x016d: bus 2:slot 14:func 0
[Sun Aug 17 21:02:47 2014] megaraid 0000:02:0e.0: PCI IRQ 46 -> rerouted to legacy IRQ 18
[Sun Aug 17 21:02:47 2014] FDC 0 is a National Semiconductor PC87306
[Sun Aug 17 21:02:47 2014] megaraid: fw version:[522D] bios version:[H430]
[Sun Aug 17 21:02:47 2014] scsi0 : LSI Logic MegaRAID driver
[Sun Aug 17 21:02:47 2014] scsi[0]: scanning scsi channel 0 [Phy 0] for non-raid devices
[Sun Aug 17 21:02:47 2014] scsi 0:0:6:0: Processor PE/PV 1x6 SCSI BP 1.0 PQ: 0 ANSI: 2
[Sun Aug 17 21:02:48 2014] tsc: Refined TSC clocksource calibration: 3192.207 MHz
[Sun Aug 17 21:02:48 2014] Switching to clocksource tsc
[Sun Aug 17 21:02:49 2014] scsi[0]: scanning scsi channel 1 [Phy 1] for non-raid devices
[Sun Aug 17 21:02:53 2014] scsi[0]: scanning scsi channel 2 [virtual] for logical drives
[Sun Aug 17 21:02:53 2014] scsi 0:2:0:0: Direct-Access MegaRAID LD 0 RAID1 69G 522D PQ: 0 ANSI: 2
[Sun Aug 17 21:02:53 2014] scsi 0:2:1:0: Direct-Access MegaRAID LD 1 RAID5 419G 522D PQ: 0 ANSI: 2
[Sun Aug 17 21:02:53 2014] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013
[Sun Aug 17 21:02:53 2014] mpt2sas version 14.100.00.00 loaded
[Sun Aug 17 21:02:53 2014] GDT-HA: Storage RAID Controller Driver. Version: 3.05
[Sun Aug 17 21:02:53 2014] 3ware Storage Controller device driver for Linux v1.26.02.003.
[Sun Aug 17 21:02:53 2014] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
[Sun Aug 17 21:02:53 2014] LSI 3ware SAS/SATA-RAID Controller device driver for Linux v3.26.02.000.
[Sun Aug 17 21:02:53 2014] ipr: IBM Power RAID SCSI Device Driver version: 2.6.0 (November 16, 2012)
[Sun Aug 17 21:02:53 2014] RocketRAID 3xxx/4xxx Controller driver v1.8
[Sun Aug 17 21:02:53 2014] stex: Promise SuperTrak EX Driver version: 4.6.0000.4
[Sun Aug 17 21:02:53 2014] st: Version 20101219, fixed bufsize 32768, s/g segs 256
[Sun Aug 17 21:02:53 2014] sd 0:2:0:0: [sda] 142069760 512-byte logical blocks: (72.7 GB/67.7 GiB)
[Sun Aug 17 21:02:53 2014] sd 0:2:1:0: [sdb] 859545600 512-byte logical blocks: (440 GB/409 GiB)
[Sun Aug 17 21:02:53 2014] sd 0:2:1:0: [sdb] Write Protect is off
[Sun Aug 17 21:02:53 2014] sd 0:2:1:0: [sdb] Mode Sense: 00 00 00 00
[Sun Aug 17 21:02:53 2014] sd 0:2:1:0: [sdb] Asking for cache data failed
--
[Sun Aug 17 21:02:53 2014] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[Sun Aug 17 21:02:53 2014] serio: i8042 KBD port at 0x60,0x64 irq 1
[Sun Aug 17 21:02:53 2014] mousedev: PS/2 mouse device common for all mice
[Sun Aug 17 21:02:53 2014] rtc_cmos 00:03: RTC can wake from S4
[Sun Aug 17 21:02:53 2014] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[Sun Aug 17 21:02:53 2014] rtc_cmos 00:03: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
[Sun Aug 17 21:02:53 2014] md: linear personality registered for level -1
[Sun Aug 17 21:02:53 2014] md: raid0 personality registered for level 0
[Sun Aug 17 21:02:53 2014] md: raid1 personality registered for level 1
[Sun Aug 17 21:02:53 2014] md: raid10 personality registered for level 10
[Sun Aug 17 21:02:53 2014] md: raid6 personality registered for level 6
[Sun Aug 17 21:02:53 2014] md: raid5 personality registered for level 5
[Sun Aug 17 21:02:53 2014] md: raid4 personality registered for level 4
[Sun Aug 17 21:02:53 2014] md: multipath personality registered for level -4
[Sun Aug 17 21:02:53 2014] device-mapper: uevent: version 1.0.3
[Sun Aug 17 21:02:53 2014] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com
[Sun Aug 17 21:02:53 2014] cpuidle: using governor ladder
[Sun Aug 17 21:02:53 2014] cpuidle: using governor menu
[Sun Aug 17 21:02:53 2014] input: Speakup as /devices/virtual/input/input0
[Sun Aug 17 21:02:53 2014] initialized device: /dev/synth, node (MAJOR 10, MINOR 25)
--
[Sun Aug 17 21:02:53 2014] scsi 3:0:0:0: Direct-Access DELL VSF 0123 PQ: 0 ANSI: 5
[Sun Aug 17 21:02:53 2014] scsi 3:0:1:0: CD-ROM DELL VCD 0133 PQ: 0 ANSI: 5
[Sun Aug 17 21:02:53 2014] sd 3:0:0:0: [sdc] Attached SCSI removable disk
[Sun Aug 17 21:02:53 2014] sr1: scsi-1 drive
[Sun Aug 17 21:02:53 2014] sr 3:0:1:0: Attached scsi CD-ROM sr1
[Sun Aug 17 21:02:53 2014] registered taskstats version 1
[Sun Aug 17 21:02:53 2014] md: Waiting for all devices to be available before autodetect
[Sun Aug 17 21:02:53 2014] md: If you don't use raid, use raid=noautodetect
[Sun Aug 17 21:02:53 2014] md: Autodetecting RAID arrays.
[Sun Aug 17 21:02:53 2014] md: Scanned 0 and added 0 devices.
[Sun Aug 17 21:02:53 2014] md: autorun ...
[Sun Aug 17 21:02:53 2014] md: ... autorun DONE.
[Sun Aug 17 21:02:53 2014] EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
[Sun Aug 17 21:02:53 2014] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240)
[Sun Aug 17 21:02:53 2014] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[Sun Aug 17 21:02:53 2014] VFS: Mounted root (ext4 filesystem) readonly on device 8:1.
Richard: I'm trying that right now.
|
|
|
08-17-2014, 08:46 PM
|
#14
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
OK, so the problem is that loading the module is not sufficient to have the drive show up.
When you are in rescue mode, please type dmesg to see what the kernel may have complained about while starting. If you can't read it all, try dmesg | more.
|
|
1 members found this post helpful.
|
08-17-2014, 08:55 PM
|
#15
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
BTW, if you ever re-boot using the installation DVD, what do you find by running the command ls /proc/scsi ?
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 08:17 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|