Question

Given the following situation, list any log files or commands that you would use when collecting information during the troubleshooting process

a. A CD_ROM device that worked previously with Linux does not respond to the mount command.

b. The system was unable to mount the /home filesystem (/dev/sdaa6)

c. A new database application fails to start successfully

d. The Modem Manager utility that you have installed cannot recognize any modems on the system

e. You have installed a new sound card in the Linux system, but it is not listed within any sound utility.

Answer 1

a)

Investigating the Installation Process

Cd ROM Reliability

Once in a while, particularly with more established CD-ROM drives, the installer may neglect to boot from a CD-ROM. The installer may likewise — even subsequent to booting effectively from CD-ROM — neglect to perceive the CD-ROM or return blunders while perusing from it amid the establishment.

There are various conceivable reasons for these issues. We can just show some basic issues and give general recommendations on the best way to manage them. The rest is dependent upon you.

There are two exceptionally straightforward things that you should attempt first.

In the event that the CD-ROM does not boot, watch that it was embedded effectively and that it isn't filthy.

On the off chance that the installer neglects to perceive a CD-ROM, attempt simply running the alternative Detect and mount CD-ROM a moment time. Some DMA related issues with extremely old CD-ROM drives are known to be settled along these lines.

In the event that this does not work, at that point attempt the proposals in the subsections underneath. Most, however not all, proposals talked about there are substantial for both CD-ROM and DVD, yet we'll utilize the money market investment ROM for effortlessness.

On the off chance that you can't get the establishment working from CD-ROM, attempt one of the other establishment techniques that are accessible.

Normal issues

Some more established CD-ROM drives don't bolster perusing from plates that were copied at high speeds utilizing an advanced CD author.

Some extremely old CD-ROM drives don't work effectively if "coordinate memory get to" (DMA) is empowered for them.

The most effective method to research and possibly tackle issues

On the off chance that the CD-ROM neglects to boot, attempt the proposals recorded underneath.

Watch that your BIOS really underpins booting from CD-ROM (just an issue for extremely old frameworks) and that CD booting is empowered in the BIOS.

In the event that you downloaded an iso picture, watch that the md5sum of that picture coordinates the one recorded for the picture in the MD5SUMS document that ought to be available in an indistinguishable area from where you downloaded the picture from.

$ md5sum debian-testing-i386-netinst.iso

a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst.iso

Next, watch that the md5sum of the copied CD-ROM coordinates too. The accompanying charge should work. It utilizes the measure of the picture to peruse the right number of bytes from the CD-ROM.

$ dd if=/dev/cdrom | \

> head - c `stat - format=%s debian-testing-i386-netinst.iso` | \

> md5sum

a20391b12f7ff22ef705cee4059c6b92 -

262668+0 records in

262668+0 records out

134486016 bytes (134 MB) duplicated, 97.474 seconds, 1.4 MB/s

In the event that, after the installer has been booted effectively, the CD-ROM isn't recognized, once in a while just attempting again may take care of the issue. On the off chance that you have in excess of one CD-ROM drive, have a go at changing the CD-ROM to the next drive. On the off chance that that does not work or if the CD-ROM is perceived however there are blunders when perusing from it, attempt the recommendations recorded underneath. Some fundamental learning of Linux is required for this. To execute any of the charges, you should first change to the second virtual comfort (VT2) and initiate the shell there.

Change to VT4 or view the substance of/var/log/syslog (utilize nano as editorial manager) to check for a particular blunder messages. From that point forward, additionally check the yield of dmesg.

Check in the yield of dmesg if your CD-ROM drive was perceived. You should see something like (the lines don't really need to be back to back):

ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33

ata1.00: arranged for UDMA/33

scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 ANSI: 5

sr0: scsi3-mmc drive: 24x/24x author dvd-smash disc/rw xa/form2 cdda plate

cdrom: Uniform CD-ROM driver Revision: 3.20

On the off chance that you don't see something to that effect, odds are the controller your CD-ROM is associated with was not perceived or might be not bolstered by any stretch of the imagination. On the off chance that you recognize what driver is required for the controller, you can have a go at stacking it physically utilizing modprobe.

Watch that there is a gadget hub for your CD-ROM drive under/dev/. In the case over, this would be/dev/sr0. There ought to likewise be a/dev/cdrom.

Utilize the mount charge to check if the CD-ROM is as of now mounted; if not, take a stab at mounting it physically:

$ mount/dev/hdc/cdrom

Check if there are any mistake messages after that charge.

Check if DMA is presently empowered:

$ disc/proc/ide/hdc

$ grep using_dma settings

using_dma 1 0 1 rw

A "1" in the primary segment after using_dma implies it is empowered. In the event that it is, have a go at impairing it:

$ resound - n "using_dma:0" >settings

Ensure that you are in the catalog for the gadget that compares to your CD-ROM drive.

On the off chance that there are any issues amid the establishment, take a stab at checking the respectability of the CD-ROM utilizing the alternative close to the base of the installer's primary menu. This choice can likewise be utilized as a general test if the CD-ROM can be perused dependably.

Boot Configuration

On the off chance that you have issues and the piece hangs amid the boot procedure, doesn't perceive peripherals you really have, or drives are not perceived legitimately, the principal thing to check is the boot parameters, as talked about in Section 5.3, "Boot Parameters".

Sometimes, breakdowns can be caused by missing gadget firmware (see Section 2.2, "Gadgets Requiring Firmware" and Section 6.4, "Stacking Missing Firmware").

Deciphering the Kernel Startup Messages

Amid the boot grouping, you may see numerous messages in the frame can't discover something, or something not present, can't introduce something, or even this driver discharge relies upon something. The greater part of these messages are safe. You see them in light of the fact that the part for the establishment framework is worked to keep running on PCs with a wide range of fringe gadgets. Clearly, nobody PC will have each conceivable fringe gadget, so the working framework may radiate a couple of protests while it searches for peripherals you don't claim. You may likewise observe the framework stop for some time. This happens when it is sitting tight for a gadget to react, and that gadget is absent on your framework. On the off chance that you discover the time it takes to boot the framework inadmissibly long, you can make a custom piece later (see Section 8.6, "Incorporating a New Kernel").

Detailing Installation Problems

On the off chance that you get past the underlying boot stage however can't finish the introduce, the menu alternative Save investigate logs might be useful. It gives you a chance to store framework mistake logs and setup data from the installer to a floppy, or download them utilizing a web program. This data may give pieces of information with respect to what turned out badly and how to settle it. On the off chance that you are presenting a bug report, you might need to join this data to the bug report.

Other correlated establishment messages might be found in/var/log/amid the establishment, and/var/log/installer/after the PC has been booted into the introduced framework.

Submitting Installation Reports

On the off chance that regardless you have issues, please present an establishment report. We additionally urge establishment reports to be sent regardless of whether the establishment is effective, so we can get however much data as could be expected on the biggest number of equipment designs.

Note that your establishment report will be distributed in the Debian Bug Tracking System (BTS) and sent to an open mailing list. Ensure that you utilize an email address that you wouldn't fret being made open.

In the event that you have a working Debian framework, the least demanding approach to send an establishment report is to introduce the establishment report and reportbug bundles (well-suited introduce establishment report reportbug), arrange reportbug as clarified in Section 8.5.2, "Sending E-Mails Outside The System", and run the order reportbug establishment reports.

c)

Problem(Abstract)

Because of issues with inward circles, a Tivoli Storage Manager neglects to appropriately begin and is prematurely ended. In this way, once the plates issues are settled, the case neglects to begin with the beneath blunders.

Side effect

When beginning the server in the frontal area utilizing the "dsmserv" summon, the accompanying messages are accounted for:

ANR0151W Database chief neglects to begin. For more data about the disappointment, issue the db2start order.

ANR0172I rdbdb.c(1722): Error experienced performing activity InstanceStop. ANR0162W Supplemental database symptomatic data: - 1032:SQLSTATE 57019: The announcement was not fruitful, due to an issue with an asset.

:- 1032 (SQL1032N No begin database chief summon was issued. SQLSTATE=57019

Cause

Uncalled for shutdown of case created stranded IPC assets

Diagnosing the issue

In the db2diag.log of the example, the accompanying mistake is logged :

<timestamp> I779399E357 LEVEL: Severe

PID : 18375 TID : 140737134171936PROC : db2star2

Example: tsmserv NODE : 000

Capacity: DB2 UDB, base sys utilities, DB2StartMain, probe:580

MESSAGE : ECF=0x900003DE=-1879047202=ECF_TRCAPI_MUTEX_LOCK_ERROR

Follow office mutex sudden bolt mistake

Settling the issue

Finish the accompanying strides to determine the mistake:

1. Sign on with the Tivoli Storage Manager server occasion client ID on Linux.

2. Run the accompanying charge to stop the DB2 occasion :

db2stop

In the event that the charge fizzles or does not finish, run the accompanying summon :

db2_kill

3. Run the accompanying ipcs charge to confirm whether there are remarkable IPC assets that are related with the example :

ipcs - a

4. Run the ipclean summon to tidy up IPC assets that are related with the occurrence :

- bash-3.1$ ipclean

ipclean: Removing DB2 motor and customer's IPC assets for tsmserv.

5. Run the accompanying ipcs summon to confirm whether there are exceptional IPC assets that were not expelled by the ipclean charge. For instance :

ipcs - a

6. On the off chance that there are exceptional IPC assets related to the occurrence, utilize the accompanying orders to evacuate them :

To expel a common memory fragment asset, run the accompanying order :

ipcrm - m <shmid>

To evacuate a semaphore asset, run the accompanying summon :

ipcrm - s <semid>

To evacuate a message line asset, run the accompanying summon :

ipcrm - q <msgid>

7. When all extraordinary IPC assets have been expelled, restart the Tivoli Storage Manager server case.

Please post the remaining questions as another question