You might be able to use nmap to find out. You can use the -Pn option to tell nmap to skip the ping scan to determine if the host is up. Be aware that nmap will try to connect to a wide range of known ports, which might trigger watchdogs on the target network. In general, using nmap on networks that you are not a valid user of is considered bad manners, so discuss with the network owner before using.
Your success will depend on how the firewall is configured. If it is set up to block all access from WAN for that host (e.g. drop all inbound/outbound packets to/from the host you are interested in), you will never get any response from the host. Your only hope may be that you can access a different host on the target network and be able to try to ping or connect to the host from there.
My current OS gparted obviously does not see md device associated with the array, but it sees the USB /dev/sdx (and all the partitions) , and it does not exist in mdadm.conf file. Also mdadm --detail --scan --verbose cannot see it either - no surprise here.
Is there a SAFE way to recreate RAID5 md device in my current OS?
Can I use mdadm --create ..... to keep current data intact?
A search for "<your distro> RAID" should lead you to some useful documents.
There is one I can't quickly find that discusses rearranging RAID partitions, changing RAID levels and so on.
That would give you a starting point.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
So far I have found tools to recover Linux.
I am after restoring specific , already data containing RAID5 array.
Looks as I could used mdadm --assemble
I cannot find anything stating it will keep exciting data intact.
After RAID is created it has to be configured in fstab to auto-mount on boot.
I am not sure where to obtain the correct format and mounting data to fstab.
I got as far as "UUID= ...."
I am using "mount -a" to verify fstab.
Is there a way to add line to fstab so mount will report / echo it as a comment ?
I am currently hacking it by putting invalid text to fstab, the "mount" reports such entry as an error and gives me a line # .
You can use --fake or -f to get mount to test your fstab.
What you put in /etc/fstab depends on what your raid is like. If you're using a hardware raid controller, then the RAID cluster is probably presented to the OS as /dev/sdx, but if you're using software raid, the I think the cluster is presented as /dev/mdn.
After creating your RAID, you'll need to partition and format, just like a normal Hard drive. Once you've done that, you can use blkid to get the UUID of the partition for fstab.
I am not sure why I am getting "PT" , but here is something I found in another forum
PTUUID is the UUID of the partition table itself, a unique identifier for the entire disk assigned at the time the disk was partitioned. It is the equivalent of the disk signature on MBR-partitioned disks but with more bits and a standardized procedure for its generation.
Now when I read blkid I am getting this - it identifies both /dev/md42 and the partition itself as /dev/md42p1
so, i was doing some programming with eclipse and stuff. But then i noticed that all of my .JAR files suddenly looked like a pinguin with some painting stuff on his hands. i need help, cause im not sure what is going on!! I use windows.
[SOLVED] I had to right click a JAR file, and "press open in application" then select Java JDK. For some reason i had two of those...