Bakunin, in this array i have not anymore important information. I recreated databases in other fs and i don't need it anymore btw is a raid 5 of 400Gb and i want to recover that space.
Yesterday i was "playing" and now i have destroyed all and i need to create again.
But i can't see the device
Yesterday
Now:
I don't have a idea how to create hdisk3 again (at storage lvl is everything ok)
OK, but in this case the discussion about reviving superblocks is moot: you can't revive a superblock on a FS located on some disk cannot see. The question is not: "how can i repair the superblock", but "how do i get back my disk". Only when this is done we can find out if the superblock needs to be repaired and - if so - how this can be done.
Quote:
Originally Posted by thorin666
I don't have a idea how to create hdisk3 again (at storage lvl is everything ok)
You cannot "create hdisk3" because hdisk3 is a device file created by a driver as an interface to a device it uses. As far as i can see you probably have storage box (DS4k, DS3k) connected via some FC-switch and you probably have some FC-cards either in your system or in a VIOS which serves the LPAR some virtual adapter.
"hdisk3" now is: the DS3k serves a LUN (a virtual "disk" construct), which is propagated via some FC-connection to your system. At your system you probably have some fcsX Adapters (X representing some number, "fcs0", "fcs1", ...) like this:
The driver (we use EMC storage so our drivers are different from yours, but the big picture is the same) picks up what comes over the FC link and tells the system: "i serve you something which you can think of to be a disk. For this i give you a device file and call it /dev/hdisk3 - behind which i will wait and will take whatever disk request you put there and translate that to commands the real storage can understand. Don't bother to look for real existing iron, it just isn't there."
When the cfgmgr runs instead of searching for hardware it will tell the driver to scan the FC-line for anything only the driver understands and - if it finds something worthwhile - tell that the cfgmgr so that a device file will be created.
This means for you: if you cannot get hdisk3 when running "cfgmgr" this means that the driver cannot find anything worthwile and this means that your disk is not visible to the system at all. There are several possible reasons for this, but you will have to investigate these at your own:
- driver incompatibility
Maybe you need a new driver because the old one cannot find anthing because of a version problem. Update (or - rarely - downdate) the driver and proceed
- zoning problems
You do not want every host connected to the storage to see every disk the storage serves. For this you create something similar to VLANs in network - zones. A zone is basically a bunch of "initiators" - LUNs and adapter ports, identified by a WWN, which is analogous to a MAC address - grouped together and allowed to see each other.
- storage problems
Storage is usually not only a long list of LUNs but has some layers to help virtualizing storage as much as possible. Maybe in one of these layers something changed and your LUN is not propagated to the zone where you expect it to be any more.
- hardware problems
Last but not least: there is a complex machinery at work, which sometimes can (and, over time, is guaranteed to) fail. Check cables, ports, adapters, FC-switches, maybe virtualization layers (SVC, ...) and similar things. Look at your machines error report (issue "errpt" and see what comes up).
OK, but in this case the discussion about reviving superblocks is moot: you can't revive a superblock on a FS located on some disk cannot see. The question is not: "how can i repair the superblock", but "how do i get back my disk". Only when this is done we can find out if the superblock needs to be repaired and - if so - how this can be done.
You cannot "create hdisk3" because hdisk3 is a device file created by a driver as an interface to a device it uses. As far as i can see you probably have storage box (DS4k, DS3k) connected via some FC-switch and you probably have some FC-cards either in your system or in a VIOS which serves the LPAR some virtual adapter.
"hdisk3" now is: the DS3k serves a LUN (a virtual "disk" construct), which is propagated via some FC-connection to your system. At your system you probably have some fcsX Adapters (X representing some number, "fcs0", "fcs1", ...) like this:
The driver (we use EMC storage so our drivers are different from yours, but the big picture is the same) picks up what comes over the FC link and tells the system: "i serve you something which you can think of to be a disk. For this i give you a device file and call it /dev/hdisk3 - behind which i will wait and will take whatever disk request you put there and translate that to commands the real storage can understand. Don't bother to look for real existing iron, it just isn't there."
When the cfgmgr runs instead of searching for hardware it will tell the driver to scan the FC-line for anything only the driver understands and - if it finds something worthwhile - tell that the cfgmgr so that a device file will be created.
This means for you: if you cannot get hdisk3 when running "cfgmgr" this means that the driver cannot find anything worthwile and this means that your disk is not visible to the system at all. There are several possible reasons for this, but you will have to investigate these at your own:
- driver incompatibility
Maybe you need a new driver because the old one cannot find anthing because of a version problem. Update (or - rarely - downdate) the driver and proceed
- zoning problems
You do not want every host connected to the storage to see every disk the storage serves. For this you create something similar to VLANs in network - zones. A zone is basically a bunch of "initiators" - LUNs and adapter ports, identified by a WWN, which is analogous to a MAC address - grouped together and allowed to see each other.
- storage problems
Storage is usually not only a long list of LUNs but has some layers to help virtualizing storage as much as possible. Maybe in one of these layers something changed and your LUN is not propagated to the zone where you expect it to be any more.
- hardware problems
Last but not least: there is a complex machinery at work, which sometimes can (and, over time, is guaranteed to) fail. Check cables, ports, adapters, FC-switches, maybe virtualization layers (SVC, ...) and similar things. Look at your machines error report (issue "errpt" and see what comes up).
I hope this helps.
bakunin
Bakunin now i understand that maybe the problem is in the storage (i had before problems with that storage)
y destroyed the array and recreated it (now is running the creation process that maybe will spend more than 1 hour). I linked with my server and when it finish i will rerun cfgmgr to see if it is something new.
ill post when i have news (today of course)
Regards!
Hi,
In Linux, I had modified fstab file which used to mount ~/Music, ~/Pictures, etc with disk partitions containing corresponding content or binding directory located at other partition. But I am wondering can I do same in El-Capitan as well? No linking!
/media/L-Store/Desktop/Documents ... (0 Replies)
I want to gain read/write access to a Windows 8 partition from a linux live cd. Prior to Windows 8, I used ntfs-3g to mount the partition from the command line.
The "Fdisk -l" command does not seem to be able to read efi partitions. There must be some new strategy for linux users. This is... (6 Replies)
Hello,
Im new here, and may be my question is stupid, but...
Today I run PGP Desktop decript on my 2nd partition ( D:\ ) and when decript finish, I restart my PC.Now when I try to open D:\ its give me: D:\ is not accessable and I lose my files :(
So I load Linux live CD ( knoppix ) and try to... (1 Reply)
I dualboot Ubuntu and Fedora in one hard drive. Below are the scenario.
First, installed Ubuntu 10.4 on the entire disk (40GiB of size).
Then, shrink the Ubuntu installation to equal size to free up space for fedora.
Second, installed Fedora 13 using the option "Use free space on selected... (2 Replies)
Dear Brothers
First i installed suse linux with the following partition. my hd0 size is 75gb
hdc1 swap 1 gb
hdc2 native linux 39gb
For the rest of the 35 gb i did not create any partition. so i planned to install solaris 10x86 on that free space.
When i installed the solaris i... (1 Reply)
I've created a partition with GNU Parted, how do I mount the partition?
The manual information at http://www.gnu.org/software/parted/manual/parted.html is good, but I am sure about how I mount the partition afterwards.
Thanks,
--Todd (1 Reply)
Hello ,
I 've got a problem with the root partition on my SCO 5.0.5 .
When I check the disk with df or mount , I can 't see the root filesystem .
# mount
/stand on /dev/boot read only on Tue Sep 05 16:13:51 2006
/home on /dev/home read/write on Tue Sep 05 16:14:41 2006
But , if I try... (3 Replies)
dear all,
that is my problem :
c0d0p1 is nt,
c0d0p2 is solaris
and other on extended partition is pcfs,
so how can i mount it somewhere?
because i dont know which one connect from raw to block dev.
/dev/rdsk/c0d0p?
any help would be great... :) (6 Replies)
Hello,
I have a problem on my sun station, that run solaris7.
To free temporarly a little space on /, I moved a few empty folders (mnt, net, awk, tftpboot) to the /home partition.
Unfortunately the system froze just after this...maybe I should not have move this files, I don't know, I am a... (3 Replies)
Hello,
I am trying to mount a FAT16 and FAT32 partition on an already installed Redhat system.
I have tried to edit the fstab and mtab, and to put in the data I got from fdisk, but it just says cannot find it.
The information given by fdisk on /dev/hda is:
Device Boot Start ... (4 Replies)