Server :: ISCSI Failing At Reboot To Detect Mapped Volume
Sep 28, 2010
I am trying to connect the one of server RHEL5.4 to the IBM iSCSI storage. Server is equipped with 2 single port Qlogic iSCSI HBA(TOE). RHEL detected the HBA and installed driver itself (qla3XXX). I have configured the HBA ip address in the range of iSCSI host port of storage. Both of the HBA is connecting to the two different controller of storage. I have discovered the storage using command iscsiadm -m discovery command for both of the controller and it went through fine. But problem is whenever server is restarting if both of the hba is connected to the storage then server will not detect the volumes which is mapped to the server and then to detect the volume I need to run "mppBusRescan" and "vgscan" command each time. If only one path is connected it is fine.
We have a Centos 5.6 server mounting two iSCSI volumes from an HP P2000 storage array. Multipathd is also running, and this has been working well for the few months we have been using it. The two volumes presented to the server were created in LVM, and worked without problem.We had a requirement to reboot the server, and now the iSCSI volumes will no longer mount. From what I can tell, the iSCSI connection is working ok, as I can see the correct sessions, and if I run 'fdisk -l' I can see the iSCSI block devices, but the O/S isn't seeing the filesystems. Any LVM command does not show the volumes at all, and 'vgchange -a y' only lists the local boot volume, not the iSCSI volumes. My concern is that, the output of 'fdisk -l' says 'Disk /dev/xxx doesn't contain a valid partition table' for all the iSCSI devices. Research shows that performing the vgchange -a y command should automatically mount any VG's that aren't showing, but it doesn't work.
There's a lot of data on these iSCSI volumes, and I'm no LVM expert. I've read that some have had problems where LVM starts before iSCSI and things get a bit messed up, but I don't know if this is the case here (I can't tell), but if there's a way of switching this round that might help, I'm prepared to give it a go.There was absolutely no indication there were any problems with these volumes, so corruption is highly unlikely.
I've installed Squeeze 2.6.32-5-amd64 on my laptop (Alienware M17X R3, Intel i7 Sandybridge, ATI Technologies Inc Broadway [ATI Mobility Radeon HD 6800 Series])The screen is 17", with maximum resolution of 1920 x 1080. After a default install of the operating system, the maximum resolution I can select is 1280 x 1024.My research so far has suggested that I need to edit the /etc/X11/xorg.conf file and provide xorg with the necessary resolution.
Again, by default, the xorg.conf file is not created. This leads me to believe that xorg is scanning my hardware at startup and providing me with whatever it thinks is appropriate. I tried following these instructions to generate an xorg.conf file. This process created an xorg.conf file under /root/.
When I copy this xorg.conf file to /etc/X11, I get a blank (i.e. black) screen. Deleting this file restores the default resolution 1280 x 1024.This system is dual booting with Windows 7. Under windows I am able to get a 1920 x 1080 resolution, so I know my hardware is up to it.At this stage I have yet to install the drivers for the Radeon graphics card.What are my options regarding configuring xorg to give me a higher screen resolution?
I'm a light linux user over the last couple of years and I decided to built a HTPC/NAS device.
Setup: 40gb ide -> usb boot drive 3x2tb sata (4k Sector) drives
I've got another 2tb identical drive but it's holding data that is going to be copied to the raid after it's up and running and then be 'grown' into the raid array to yield a final 5+tb array. I tried doing a disk util raid array and it ended up failing after reboot due to it using the /dev/sd* designations and they swapped. I have no idea how to do the UUID version, my googlefu and practical guide to ubuntu. So I decided to do it manually in order to also fix the sector issue as disk util wasn't formatting them correctly and once formatted wouldn't let me create a raid array from the discs.
I have an iSCSI device that is large, ~17TB usable, and I've created an XFS file system at the device level. I mount the device no problem and am able to touch and remove files without issue. I start my application and within about 5-10 minutes I start seeing the following entries appear in /var/log/messages
I have an iSCSI target on my Ubuntu 10.04 LTS server that is giving me access to 3 x 2TB volumes. I am using LVM to create 1 big volume and using it as a place for my backup software to write to. Upon initial setup I tested to see if the connection would still be there after a reboot, and it was. After going through the trouble of configuring my backup software (ZManda) and doing a few very large backups I had to reboot my SAN (OpenFiler) for hardware reasons. I took my server down while performing the maintenance and brought it back up only after the SAN work was done. Now, the LVM volume is listed as "not found" when booting.
Using iscsiadm I can see the target but LVM doesn't know of any volumes that exist using those targets. I need to get it back up and running and then troubleshoot the reboot issue.
I am currently wanting to connect to an NAS unit that I have. I have installed open-iSCSI and have made the following changes to the iscsi_conf file:
Quote:
# To set a CHAP username and password for initiator # authentication by the target(s), uncomment the following lines: node.session.auth.username = "user" node.session.auth.password = "12 digit pass"
[Code].....
My goal is to get the iSCSI initiator to connect after a reboot. Mounting after connecting I am sure this will be another challenge.
Does anyone have any good articles on mounting a Ubuntu volume as an iSCSI share on a windows box? Originally I was just going to use a SAMBA share but it turns out samba has issues with my lan security. So I thought since all I really want to do is create the share on my backup server that an iSCSI device would do. Been using the following article with limited success... [URL]
The first time I started ubuntu, it auto-conected to my personal wireless network. Now, when I try to connect to another wireless network, it doesn't auto-detect. Does anyone know why this happens?
I have never done this before but stood up a new Debian (testing) x64 system. It only has 146GB available for RAID1 so I created a 500GB iSCSI LUN on my NAS device on the network and am really confused how I can attach my Debian to the iSCSI LUN I created. Right now the OS is installed all locally on the machine but I would like the iSCSI LUN to be the /home directory for mail storage. Is this possible or do I need to mount the LUN to a newly created folder / mount point that is locally attached?
Well, this new issue when installing the new lucid relase iso seems to be closly related to my previous bug report refering to suspend and hybernate failing to power off, freezing at and of suspend/hybernate preperation. now what happens... installing ubuntu lucid 64bit, all gos perfect. finally i get the window begging me to reboot. i click reboot. window finsihes its work and disapears. that's it. screen is frozen with its purple background. no ctrl+alt+del, nor anything else works. only reset button. so it failed ro reboot like it fails to pwoer off for hybernate or suspend. on same machine this does not happen with karmic. it is a soley ubuntu lucid problem. any suggestion how to track that down? p.s. in my original thread and bug report i provided a pm-suspend.log that went all good till the last statement "powering off".
I have a peer-to-peer network with 25 WinXP Pro computers. I have built a Linux (SuSE) server for the purpose of backing up My Documents, PST files and favourites. Each user has their own folder containing the sync'd files. Each folder is password protected. I have configured each users machine with a mapped 'S' drive, which is the sync'd data folder on the Linux computer. All of the computers seem to end up with a "disconnected network drive" status after either logging out for the day or after some time has elapsed. Some will connect with a double click but others prompt for a password. I have tried mapping the drive using the option "Connect using a different user name", which is fine until the user logs out and back in again. I use SyncToy as a scheduled task, but can't connect to these mapped drives automatically, so the sync process will not work unattended.
I'm running SUSE 11.3 with gnome (and pulseaudio, which I tried to get rid of, but for me it's just too much hassle to get audio working w/o pulse). The Master volume of my USB headset (2nd soundcard) is reset to 0 after each boot. In order to get it properly working, I have to run the YaST sound module and re-set the Master volume (which always is down to 0). Using alsamixer to do the same doesn't work (alsamixer shows no controls), probably because pulse grabs the device or does something else with it?
Pulseaudio version: 0.9.21-10.1.1.i586 Alsa version: 1.0.23-2.12.i586 Any input on what I can do to make the volume level stick?
I know if I do a shutdown -rF now, it will perform an e2fsck on all my volumes with the -y switch. But if I just want to check one of the volumes rather than all of them, and have it use the -y switch so it will automatically answer yes to everything, how can I do that?I'm using RHEL, and have a huge volume I need to run a check on, and I dont want to sit there for the next 24 hours hitting the Y key every time it finds a problem ;-)
I'm trying to increase the size of an iSCSI device. On the LUN side, the provision size has been expanded already. I expanded the size of this device from 15GB to 30GB.
It's been days that I've been with this and I'm getting to the end of my wits.
I tried to create a RAID-5 volume with three identical 1tb drives. I did so, but I couldn't mount the new volume after a reboot. Mdadm --detail told me that of the three drives, two were in use with one as a hot spare. This isn't what I wanted.
So I deleted the volume with the following commands:
Then I rebooted the machine, and used fdisk to delete the linux raid partitions and re-write an empty partition table on each of the drives. I rebooted again.
Now I'm trying to start over. I purged mdadm, removed the /etc/mdadm/mdadm.conf file, and now I'm back at square one.
Now for whatever reason I can't change the partition tables on the drives (/dev/sdb /dev/sdc /dev/sdd). When I try to make a new ext3 filesystem on one of the drives, I get this error:
"/dev/sdb1 is apparently in use by the sytem; will not make a filesystem here!"
I think that the system still thinks that mdadm still has some weird control of my drives and won't release them. Never mind that all I want to do even now is just make a RAID-5 volume. I've never had such difficulty before.
I am trying to create a link to my windows xp workgroup where all my data is stored (I was surprised that linux could even see it!) I mounted a volume on the desktop apparently... that worked fine until I rebooted and it had disappeared. it was fairly annoying that I had to go back into the network and re-mount the volume. How can I get it to stay put, even after rebooting?
I'm looking for insite on how it might be possible to grow an existingvolume/partition/filesystem while it's in active use, and without having to add additional luns/partitions to do it.For example the best way I can find to do itcurrently, and am using this in production, is you have a system using LVM managing a connected LUN (iSCSI/FC/etc), with a single partition/filesystem residing on it.To grow this filesystem (while it's active) you have to add a new LUN to the existing volume group, and then expand the filesystem. To date I have not found a way to expand a filesystem that is hosted by a single LUN.
For system context, I'm running a 150 TB SAN that has over 300 spindles, to which about 50 servers are connected. It is an equal mix of Linux, Windows, and VMware hosts connected via both FC & iSCSI... With both Windows & VMware, the aforementioned task of expanding a single LUN and having the filesystem expanded is barely a 1 minute operation that "Just Works".If you can find me a sweet way to seamlessly expand a LUN and have a Linuxfilesystem expanded (without reboot/unmount/etc)I have cycles to test out any suggested methods/techniques, and am more than happy to report the results for anyone else interested. I think this is a subject that many people would like to find that magic method to make all our lives much easier
The volume keyboard shortcuts on my Asus Eee 1008p resets on reboot.(going back to no shortcut at all). It works for the session, if i set it, but after reboot i have to set it again.
I added another disk in server and create mount point in fstab: /dev/VolGroup00/LogVol00 /opt ext3 defaults 1 2 Everything is working perfect... halt, boot, system... but when I wanna to reboot with a command sudo reboot, it hangs at the end of all initialization when it's rebooting and some number. If I remove disk in fstab, than reboot working.
I encountered problem on my NEW PROD box. I have remaining space of 300GB and i decided the create a /dev/mapper/VolGroup00 using Redhat Gui. It is successful. Then, i decided to create logical volumes out of it..
I am interested in turning my home server into something that I can store backups on. I do photography and therefore have a lot of photos. I use Mac OS X for my photo editing, so it must be accessible from my Macbook. I am new when it comes network storage servers, so what would be the best solution for me to be able to backup my photos seamlessly? I would like it easy enough so others can backup files without any terminal commands and such. What would you suggest? CIFS? RAID? iSCSI?
I am running RHEL5.5 its a fresh install and we are testing Xen Virtualization. We are wanting to use our iSCSI SAN for the VMs. I have created the initiator iqn, and discovered the target address. We are connected to the target, but there is no new block device in /dev.
I built a CentOS 5 Linux cluster with GFS storage using local RAID volume and share it with gnbd_export/import on two web-servers. Now I need to expand that storage to another servers local volume. I saw the picture in the manual, but I don`t know, how can I create that scheme.
I can use gnbd_export on the second server and gnbd_import on the first. In that case I will have two volumes on the first storage and I can expand volume group, logical volume, etc on it.
I've got a file server with two RAID volumes. The one in question is 6 1TB SATA drives in a RAID6 configuration. I recently thought one drive was becoming faulty, so I removed it from the set. After running some stress tests, I determined my underlying problem hadn't cleared up. I added the disk back, which started the resync. Later on, the underlying problem caused another lock up. After a hard-reboot, the array will not start. I'm out of ideas on how to kick this over.
I'm trying to make a fresh install of Ubuntu 10.10 Server 64bit but is stuck with the Partitioning Disk part and Ubuntu 10.04 LTS provides the same error. The installation wizard gives me a menu:
!! Partitioning disks This menu allows you to configure iSCSI volumes iSCSI configuration actions
I have a fairly simple iSCSI setup using two devices, but they have swapped names on different machines. running CentOs 5.3 ia64, and using iscsi-initiator-utils-6.2.0.868-0.18.el5
vm1: [root@vm1 ~]# fdisk -l Disk /dev/xvda: 4194 MB, 4194304000 bytes 255 heads, 63 sectors/track, 509 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
[Code].....
Any way to get iSCSI to mount the devices as consistent device names ?
