I have installed Ubuntu server 10.10 today and I am trying to mount the scsi cdrom drive in a Dell Poweredge 2850. I can see the device in dev listed as scd0, but when i try to mount it to /media/cdrom or /mnt/cdrom I get a long list of I/O errors: Buffer I/O error on device sr0.
I have successfully setup a FOG server to image my Windows clients, so I have tftp, pxe and anything else related to booting to a pxe server setup and rocking. What I'm trying to do now, is use the CentOS net install files to setup CentOS on an old server with no USB boot option, and a broken scsi cdrom drive (it's a Dell PowerEdge 2400, with a single PIII 733 and 1.25GB ram).
Using the FOG Projects gparted wiki entry (adding gparted to the pxe boot menu) I was actually successfully able to pull the net install files over to the PE, and install CentOS 5.5 via local ftp server. At first it kept erroring out (I kept picking and choosing individual packages from the package groups), so I thought it may be an issue with the GUI install (the python script kept spitting back errors forcing a reboot). In any case, I finally got through the GUI install, but now I need / want to know how to force a text mode install.
[Code]....
the bolded "append" line is where I thought I could force the text mode install script, but that didn't work. The vmlinuz and initrd.img files were both pulled form the net install iso, NOT the livecd. Would that have made a difference? If not, what / where / how should I force the text mode install script?
My cdrom drive was working until yesterday it didn't mount at all. It said 'special device /dev/scd0 does not exist'. I went and checked in BIOS and the CD rom was not identified there as well I would like to know if there is a workaround for this problem. I am using an ACER aspire 4520 laptop with only ubuntu 9.10 on i
I went through some conf files under /etc. But cannot find out why cdrom always mounted under /media? Also there is one line in /etc/auto.misc: cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
Does that mean the cdrom should be mounted under /misc/cd?
I'm trying to install Lucid on a computer with windows already present. When I ran trough the install procedure no drives show up at the partitioning stage. So I check some things out and it turns out that /dev/sda1 is mounted to /cdrom and I can't umount it because it says the disk is in use. I'm booting with the live-cd downloaded from ubuntu. Why is this happening? Previously with older live-cd's I always have to mount the HD manually if I wanted to access it for any reason?
Some of our workstations have LTO's attached and they seem to drop off every now and again, the only thing which picks them up again (besides a reboot) is the famous rescan-scsi-bus script from here
The thing is that I'd like non-root users to be able to run this script, which in turn needs root to /proc/scsi/scsi
i m facing same error in most of the HCL servers. the problem is that it throws error while booting and sometimes not throws error. the error is :-
Feb 13 13:17:25 fe13s kernel: Adapter 0: Bus A: The SCSI controller was reset due to SCSI BUS noise or an invalid signal. Check cables, termination, termpower, LVDS operation, etc.
Feb 13 13:17:30 fe13s kernel: Adapter 0: Bus B: The SCSI controller successfully recovered from a SCSI BUS issue. The issue may still be present on the BUS. Check cables, termination, termpower, LVDS operation, etc
Feb 13 13:29:15 fe13s kernel: Adapter 0: Bus B: The SCSI controller successfully recovered from a SCSI BUS issue. The issue may still be present on the BUS. Check cables, termination, termpower, LVDS operation, etc code....
In my understanding, the way /proc/scsi/scsi gets populated, /proc/paritions also gets populated in the same fashion. i.e. the description for first entry of /proc/scsi/scsi can be seen in the first entry of /proc/partitions and same for rest.
So, With this assumption, in my project, I used to relate first entry of /proc/scsi/scsi with first entry of /proc/partitions to get its total size and same for all entries.
But, I observed some differences in following scenario, where
1) The first 4 entries in /proc/scsi/scsi are SAN luns attached to my system and for which the actual device names in /dev/ are sda,sdb,sdc and sdd.
2) The last 4 entries are the internal HDDs on same system. In /dev/, their respective device names are sde,sdf,sdg & sdh.
(Output attached at end of the thread)
But in /proc/partitions, the device order is different.
You can see their respective sizes in /proc/partition output as well.
So, my question is, in this particular scenario, I can't relate the first entry of /proc/scsi/scsi with first entry of /proc/partition. i.e. scsi0:00:00:00 is not /dev/sde, because it is actually /dev/sda.
It seems that my assumption is wrong in this scenario.
Is there any way or mechanism to figure out actual device name for an entry in /proc/scsi/scsi in /dev/ directory?
How can my application should relate /proc/scsi/scsi entries with their respective device names and sizes?
When I enter "cat /proc/scsi/scsi" I'm returned with "cat: /proc/scsi/scsi: No such file or directory". I've tried this on two different installs on two different machines.
I think I should warn you about this: I am a total n00b, just came here from. well, win7, at the end.I've installed Ubuntu 10.04 LTS (Lucid Lynx), updating from 9.04 (Jaunty Jackalope) pretty much straight away.
What seems to be the problem now, after I've installed all the programs that interest me and, well, doing an 'aptitude update' and then an 'aptitude upgrade' that I was told to do, is that I don't seem to have my printer drivers and my sound card drivers installed. For one, it won't print when I tell it to from wherever I write something that I want to print, and the sound seems to work whenever it wants to, and will only work if I reboot whenever it decides not to. My printer is a Canon PIXMA iP1800 - which seems to be the only Canon one not in the list when I was asked what drivers to install.
My sound card is a Sound Blaster Audigy. The thing is, if I download the drivers from the relevant makers' websites, I have absolutely no idea what to do with them if I do. They just sit there, smile at me, and I smile back at them - and then delete them, as they don't seem to do anything of their own volition. You know, like in Windows, which my mom still runs.
I have been trying plop floppy to boot a bootable cdrom from a mobile USB cdrom reader, but the usb cdrom are not recognized.I was thinking that with grub or grub2 or syslinux that would be possible, no ?
I decided to give linux a try on an old laptop I had at my house. It's a Dell Inspiron (don't remember the model, will update as soon as I get home). Installation was flawless and extremely fast, but I cannot connect to my house's wireless network. I had exactly the same problem with Ubuntu, which is why I tried Fedora. I had installed Ubuntu over a year back and it had worked flawleslly, but I had to loan the pc to a friend so I reinstalled Windows.
Wireless drivers are Intel PRO/Wireless 2200 which should be included in the kernel. I am a complete Linux/Fedora n00b, just want to start learning.
I have a Linux system running on an older Sun V20z. The drives are mirrored in a software RAID1. The motherboard has interfaces for only IDE and SCSI. The system is old and is no longer able to handle the load we're putting on it. I also have a much newer Sun X4100. This system is presently unused and has a pair of SAS drives in it. The new server only has SAS and SATA connections on the motherboard, though. I'm trying to think of the best way to clone the V20z over the X4100. I don't mind breaking the mirror knowing I can re-establish it later. I prefer not to do a fresh OS install followed by a tape restore. I would much rather break the mirror and clone one of the SCSI drives the SAS drive. I do have a USB to SATA adaptor for migrating external drives. Anyone know if this will work with a SAS drive? Any pointers on the best way to migrate this? I'm thinking even if the cloning is successful, I'm going to have to much with GRUB to get it to boot from the SAS drive?
I have installed an old HP Scanner on my Fedora 11 system, and it works great. The scanner is connected through a SCSI, and it gets recognized at boot time if the scanner is ON. However, if the scanner is OFF, I need to turn ON the scanner and reboot the workstation for the SCSI devise to be recognized. Is there a way that I can rescan the SCSI devise without rebooting?
I am attaching a LTO-3 tape drivce into my RHEL5 linux machine. Every time i used to restart my machine to detect the tape drive is there any way to rescan the buses to detect the newly attached scsi devices. In solaris "devfsadm" and "iostat" is there. I need the same kind of thing in linux.
I have a virtual machine with Solaris 10. On this virtual machine I have to configure an iSCSI initiator.
The problem is that i have no physical SCSI devices to connect to my LAN
Therefore I have to create a Virtual SCSI device on my host laptop and configure it as an iSCSI server (iSCSI target) and share this virtual disk on the LAN.
I have one scsi storage array, JetStor SATA 416S,split into 2 halves. each is RAID5 12TB. Is it possible to dedicate each half to a different rhel5 server. I have "lsi22320-r" ultra230 dual channel scsi adapter in each server.
The first server sees the 2 halfs however the second server doesn't on the first server:
I am testing PCLinux 2009.1 prior to installing. My desktop currently runs on ME and has been out of use for some time. It still works however and I can still get online. I'm currently using a laptop running XP. I would like to make use of my old desktop and tried to test PCLinux 2009.1 today. I followed the instructions obtained online and booted from the Linux cd. The pc booted up ok and displayed the first screen allowing me to select the "Live CD" option. After enter my system hung up at "Probing SCSI Devices:Segmentation fault".
I created 2 virtual machines with VMware Workstation 7. They have identical hardwares. One guest is CentOS 5.6, another is Mandriva 2011. When I try to mount the cdrom in guest OS, in CentOS, I should execute
mount /dev/hdc /path/to/mount
in Mandriva, I should execute
mount /dev/sr0 /path/to/mount
I also remebered in some other Linux variant, I had to use
mount /dev/cdrom /path/to/mount
What's the difference between hdc, sr0 or cdrom? Is there a consistent way to mount cdrom in all Linux variants?
Suppose during a script execution I am attaching one or two new disk having different vendor id to host machine, how do I know which disk corresponds to which file in /dev/ directory? i just want to perform some operation on those device from some script, how will i know which file in /dev directory correspond to which disk(having same size but different vendor id).
I'm using a software that needs to read data from a cdrom. The instructions say to mount the cdrom (mount /mnt/cdrom). I understand that I need to mount the cdrom to /mnt/cdrom. I created a folder "cdrom" under "mnt". Then I tried to mount the cdrom by typing:
sudo mount /media/ /mnt/cdrom/ This didn't work. Under "media" I have another folder with the actual cd content so I tried to mount it too, but again with no success. I keep getting an error that "media is not a block device". What I am doing wrong?
i have vmware workstation with ubunutu server installed now i need to install samba , i use this command
apt-cdrom add after that i check the source.list and the cdrom uncomment then i use sudo apt-get install smbfs, instead of using the cdrom as the source he use internet .