HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- I20A0 boot disk devicename change on GS80
Operating System - Tru64 Unix
        1839906
        Members
    
    
        3137
        Online
    
    
        110157
        Solutions
    
Forums
        Categories
Company
Local Language
                
                  
                  back
                
        
                
        
                
        
                
        
        
        
                
        
                
        
        
        
                
        
              
              Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
                
                  
                  back
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
            
                
            
                
            
                
            
                
            
            
                
            
                
            
            
                
            
                
              
            Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
        Information
        Community
Resources
Community Language
        Language
        Forums
Blogs
Topic Options
			
				
					
	
			
		
	- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2006 12:52 AM
11-18-2006 12:52 AM
			
				
					
						
							I20A0 boot disk devicename change on GS80
						
					
					
				
			
		
	
			
	
	
	
	
	
			
				
					
					
						hi,
on GS80, there is I20 scsi adapter to which the external disk system is connected to. i have created a RAID5 with the last 4 disks in the array (bay 6, 7, 8, and 9) and i have installed the OS on it and it's the booddef_dev. the device filename for it is dza520.0.0.2004.1
Today, we have just slotted some new disks in the array to create another RAID with. After rebooting the system, the devicename which was dza520.0.0.2004.1 of the bootdef has changed to something else.
now, the OS cant boot anymore bcoz giving the error: sysconfigtab: invalid line - lsm_rootdev_is_volume=
and nothing will mount again.
please assist me to resolve the problem. could i change the filename back manually? if yes how? if not, how can i change sysconfigtab to boot?
thanks and waiting.
racio
		
		
	
	
	
on GS80, there is I20 scsi adapter to which the external disk system is connected to. i have created a RAID5 with the last 4 disks in the array (bay 6, 7, 8, and 9) and i have installed the OS on it and it's the booddef_dev. the device filename for it is dza520.0.0.2004.1
Today, we have just slotted some new disks in the array to create another RAID with. After rebooting the system, the devicename which was dza520.0.0.2004.1 of the bootdef has changed to something else.
now, the OS cant boot anymore bcoz giving the error: sysconfigtab: invalid line - lsm_rootdev_is_volume=
and nothing will mount again.
please assist me to resolve the problem. could i change the filename back manually? if yes how? if not, how can i change sysconfigtab to boot?
thanks and waiting.
racio
		2 REPLIES 2
	
	            
            
		
		
			
            
                - Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2006 02:19 AM
11-18-2006 02:19 AM
			
				
					
						
							Re: I20A0 boot disk devicename change on GS80
						
					
					
				
			
		
	
			
	
	
	
	
	
			
				
					
					
						hello, 
in my sysconfigtab file, the option lsm_rootdev_is_volume= has no value.
in which circonstance shld i use 0 or 1 as the value. and how do i do that in single user mode.
racio
		
		
	
	
	
in my sysconfigtab file, the option lsm_rootdev_is_volume= has no value.
in which circonstance shld i use 0 or 1 as the value. and how do i do that in single user mode.
racio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2006 09:24 AM
11-20-2006 09:24 AM
			
				
					
						
							Re: I20A0 boot disk devicename change on GS80
						
					
					
				
			
		
	
			
	
	
	
	
	
			
				
					
					
						Use lsm_rootdev_is_volume=1 if your boot volume is an LSM (Logical Storage Manager) volume. Use lsm_rootdev_is_volume=0 if it is not. 
If you're not using LSM, you can change the systconfigtab of a non-booting root volume by booting off the installation CD, mounting the corrupt root volume and making the necessary changes. You might be able to do something similar with LSM, but I'm not sure about that, and certainly couldn't tell you how to go about it.
		
		
	
	
	
If you're not using LSM, you can change the systconfigtab of a non-booting root volume by booting off the installation CD, mounting the corrupt root volume and making the necessary changes. You might be able to do something similar with LSM, but I'm not sure about that, and certainly couldn't tell you how to go about it.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
		
	
	
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP
