One of these drives is source, one of these drives is backup drive.
How the f*ck do you tell which is which ?!
This is problem with current harddisk technology.
No proper labelling.
This is scary a f*ck for disk-to-disk backup purposes.
Is this the best IT technology has to offer ?! Very shamefull !
Excellent example of this horrific situation is the super poor open source software called "Clonezilla" it makes absolutely no attempt to identify dri ves in any meaningfull way by for example reading NTFS labels to give the u sers some clue as to which drive is which. There may be some info inspectio n option in it's menu or not... I have not even used this software, just wa tched some youtube videos.
I do however use windows and it has the same problem and it's very annoying when I need to identify which is the boot drive and which is something tot ally else.
Surely hardware manufacturers can find some flashable ep-rom chip somewhere to allow users to properly label their hardware ?!
This has to change for the better !
Some simple "label-technology-chip" could be created which can be added to products, this would make me feel goooooood.
Label meaning letters and digits at the very least.
So user can for example rename hardware as follows:
Well, i hate to tell you,but there is writable RAM on the hard drives, and even a fairly decent CPU on them. Absolutely no need for more of the same. There is something called a LABEL which can be used in Windoze , simply click on the name and rename it to what you want. Clonezilla ALSO has the option to change the name of a drive.
e software called "Clonezilla" it makes absolutely no attempt to identify d rives in any meaningfull way by for example reading NTFS labels to give the users some clue as to which drive is which. There may be some info inspect ion option in it's menu or not... I have not even used this software, just watched some youtube videos.
ng when I need to identify which is the boot drive and which is something t otally else.
re to allow users to properly label their hardware ?!
o products, this would make me feel goooooood.
Someone hasn't heard of volume labels. If your software doesn't read them u se something that does.
Robert Baer wrote in news:8WviF.2$eW2.0 @fx25.iad:
Linux has volume labelling as well.
There are physical drives, and then there are the file system volume(s) mapped out onto them. One (the physical)is assigned a name and the other(s) is user assignable.
Oh, a volume label is good, but not nearly enough. After all, the volume can be one of ten, and with four disks in the box... which volume is on which physical medium?
On MacOS, the disk utility usually can tell you the manufacturer and model of the disks, and which volumes are on 'em, but it's a bit harder to find the serial number on an installed disk (if there's two or more instances of the make/model).
Well, when you format your medium you get to set the volume label.
Once you've set the volume label you don't need to. If it's essential to be able to pull the right disc of twins out, write the volume label on each disc before formatting it.
I typically partion a disk with several filesystems (logical volumes, each with its own label/name), not always in the same format. That way, I can clean-install any old OS, and boot into it when appropriate.
I'm likely to change the volume label(s) at a whim, it is unlikely to match a paper attached to a drive. There's a 'System Information' way to find which interfaces have which hardware attached, so wire-tracing can work. That tool also grabs disk serial numbers (but those aren't always easy to locate on physical drives).
whit3rd wrote in news: snipped-for-privacy@googlegroups.com:
snip
There is a linux bash script that yields copius amounts of system information. There is a drives section that is pretty comprehensive.
Linfo1.sh by Marek Novotny (the github page is gone now) Quote:
#!/bin/bash
############################################################# # # script : linfo.sh # version : 2.36 # About : Simple Linux System Information # Updated : 2016-11-04 # Written by : Marek Novotny # Contributors : Chris Davies # : Jonathan N. Little # : Bit Twister # : Andrew # : Gamo # Testers : Wildman # : Mike Easter # # license : GPL v2 (only) # github :
foldText () { paramError () { printf "$(basename $0) error! Incorrect parameters sent to foldText function from ln: $recdLine\n $1\n" >&2 exit $2 } # usage foldText {numeric tab} {item name} {item value string} {option -s or blank}
mtab="$1" # set the tab column item="$2" # set the string name string="$3" # set the string itself option="$4" # set the option type -s for fold at space # or leave blank for hard cut let y=1 # set the counter so the first line # printed gets the item name only. # make sure in script parameters are appropriate if [ $# -lt 3 -o $# -gt 4 ] ; then paramError "Incorrect number of arguments ($#)" 2 fi regEx='^[0-9]+$' if ! [[ $1 =~ $regEx ]] ; then paramError "mtab is not set to a numeric value" 3 fi if [ "$option" != "-s" ] ; then option="" fi if [ -z "$string" ] ; then paramError "The string is empty" 4 fi
# set the column length to fold at
let foldCol=$(( $(tput cols) - ($mtab + 4) )) # take long string and wrap it nicely around the edge of the terminal # taking into account the item name + tab size oldIFS=$IFS ; IFS=$'\n' if [ ${#string} -gt $foldCol ] ; then array=( $(echo $string | fold $option -w$foldCol) ) for x in ${array[@]} ; do if [ $y -eq 1 ] ; then printf "%${mtab}s: %s\n" "$item" "$x" ((y++)) else printf "%${mtab}s: %s\n" "" "$x" ((y++)) fi done else printf "%${mtab}s: %s\n" "$item" "$string" fi IFS=$oldIFS }
for (( x = 0 ; x /dev/null if [ $? -eq 0 ] ; then cmd="grub-install" fi grub2-install --version &> /dev/null if [ $? -eq 0 ] ; then cmd="grub2-install" fi gver=$($cmd --version | sed -e 's/grub-install (//g;s/grub2- install (//g;s/)//g') }
# report kernel taint status if any taintStatus=$(cat /proc/sys/kernel/tainted) if [ $taintStatus -ne 0 ] ; then taintArray=( "A module with a non-GPL license has been loaded, which includes modules with no license set by modutils >= 2.4.9 and module-init- tools." "A module was force loaded by insmod -f set by modutils >= 2.4.9 and module-init-tools." "Unsafe SMP processors: SMP with CPUs not designed for SMP." "A module was forcibly unloaded from the system by rmmod -f." "A hardware machine check error occurred on the system." "A bad page was discovered on the system." "The user has asked that the system be marked tainted. This could be because they are running software that directly modifies the hardware, or for other reasons." "The system has died." "The ACPI DSDT has been overridden with one supplied by the user instead of using the one provided by the hardware." "A kernel warning has occurred." "A module from drivers/staging was loaded." "The system is working around a severe firmware bug." "An out-of-tree module has been loaded." "An unsigned module has been loaded in a kernel supporting module signature." "A soft lockup has previously occurred on the system." "The kernel has been live patched." )
divider "Linux Kernel Taint Status Description" let z=0 ; values=() for (( a=1 ; a < 35000 ; a = a * 2 )) ; do values+=( $a ) done for mask in ${values[@]} ; do if (( taintStatus & mask )) ; then recdLine=$((LINENO + 1)) foldText $mtab $mask "${taintArray[$z]}" -s printf "\n" fi ((z++)) done fi
# report SELinux status if running
which sestatus &> /dev/null if [ $? -eq 0 ] ; then oldmtab=$mtab let mtab=30 oldIFS=$IFS IFS=$'\n\:'
divider "SELinux Status" sestatus | while read item status ; do status=$(echo $status | awk '{print $1}') printf "%${mtab}s: %s\n" "$item" "$status" done echo mtab=$oldmtab IFS=$oldIFS fi
# report user info
divider "User Info" set -- "User Name" "Pass" "User ID" "Primary Group" "Full Name" "Home Directory" "Shell" for x in {1..7} ; do field=$(grep ^$USER /etc/passwd | head -n1 | cut -d: -f$x) printf "%${mtab}s: %s\n" "$1" "${field:="Not Set"}" shift done printf "\n"
# group reporting
divider "Group Info" Groups=( $(grep $USER /etc/group | cut -d: -f1,3 | tr ':' ' ') ) for x in ${Groups[@]} ; do oldIFS=$IFS IFS=$' ' read GrpName GrpID < /dev/null | awk '{print $1,$2}' | tr '_' ' ') ) if [ "${#soundMod[@]}" -eq 0 ] ; then soundMod=("Not Detected") fi else soundMod=("Not Detected") fi
for x in "${soundMod[@]}" ; do printf "%${mtab}s: %s\n" "Sound Module" "$x" done
# report sound driver
if [ -r /proc/asound/version ] ; then soundDrv=$(cat /proc/asound/version | awk -F "[Dd]river " '{print $2}') if [ "${#soundDrv}" -eq 0 ] ; then soundDrv="Not Detected" fi else soundDrv="Not Detected" fi
if [ ! -z "$tempVar" ] ; then if [[ "$tempVar" == *"version"* ]] ; then driverVersion=$(modinfo "${driver}" 2> /dev/null | grep -i version | awk 'NR==1 {print $2}') fi fi
if [ -z $driverVersion ] ; then driverVersion="Not Detected" fi
MailExchange=$(dig +short $DomainName MX | head -n1 | awk '{print $2}') if [ -z $MailExchange ] ; then MailExchange="None Detected" fi printf "%${mtab}s: %s\n" "Mail Exchange" "$MailExchange"
# Collect nameserver and DNS Name if [ $(dig +short $DomainName NS | head -n1) ] ; then NameServer=$(dig +short $DomainName NS | head -n1) else NameServer="None Detected" fi
ping -c 1 $addr &> /dev/null if [ $? -eq 0 ] ; then let pingResult=0 printf " (Pass)\n" else let pingResult=1 printf " (Fail)\n" fi }
dnsTest () { # DNS test routine
dig redhat.com @$x &> /dev/null if [ $? -eq 0 ] ; then let dnsResult=0 printf " (Pass)\n" else let dnsResult=1 printf " (Fail)\n" fi }
# test if network is up and if so obtain IP address and device ID
ip addr | grep -i "state up" &> /dev/null if [ $? -eq 0 ] ; then let networkStatusResult=0
# get local IP address
set -- $(ip route get 8.8.8.8) while [ "$1" != "src" ] ; do shift assignedIP="$2" done
# get local device ID
set -- $(ip route get 8.8.8.8) while [ "$1" != "dev" ] ; do shift deviceID="$2" done
# find the gateway IP address
set -- $(ip route get 8.8.8.8) while [ "$1" != "via" ] ; do shift gatewayIP="$2" done
# find dns ip address
which nm-tool &> /dev/null if [ $? -eq 0 ] ; then DNS=$(nm-tool | grep $assignedIP -A5 | awk /DNS/'{print $2}') else DNS=$(dig redhat.com | grep -i server | tr '#()' ' ' | awk '{print $3}') fi
# print the local device and assigned ip and perform ping test on it
divider "Inside Network" printf "%${mtab}s: %s %s" "Assigned IP" "$assignedIP" "($deviceID)" addr=$assignedIP pingTest # print thee local gateway and perform ping test on it
printf "%${mtab}s: %s" "Gateway" "$gatewayIP" addr=$gatewayIP pingTest # print the found dns listings
for x in ${DNS[@]} ; do printf "%${mtab}s: %s" "DNS" "$x" dnsTest done printf "\n" else let networkStatusResult=1 fi IFS=$oldIFS }
# test inside network, if successful, test hosts, if successful, get outside network
insideNetwork if [ $pingResult -eq 0 -a $dnsResult -eq 0 ] ; then webTest if [ $webTestResult -eq 0 ] ; then outsideNetwork fi fi
# report device status if network is up
if [ $networkStatusResult -eq 0 ] ; then
divider "Interface Status" let line=1 scnSize=$(( $(tput cols) - 4 )) array=($(ip -s link show $deviceID | sed -e 's/^[1-9]\: //')) for x in "${array[@]}" ; do if [ $line -eq 1 ] ; then printf "\t%s\n\n" "$x" | fmt -c -w$scnSize else printf "\t%s\n" "$x" fi ((line++)) done printf "\n" fi
# report device block info from available options
which lsblk &> /dev/null if [ $? -eq 0 ] ; then options=(NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL UUID) for x in ${options[@]} ; do lsblk -o $x &> /dev/null if [ $? -eq 0 ] ; then params+=( $x ) fi cmdOptions=$(echo ${params[@]} | tr ' ' ',') done divider "Device Info" lsblk -o $cmdOptions printf "\n" fi
This is a common problem when cloning identical model and size drives. I run into it all the time. Most programs that do cloning will provide something more than the drive model. Usually, there is info on exact drive size, partition sizes, partition names, diskspace used, operating system version, drive serial numbers, and such. That's usually sufficient to identify the source and the destination.
However, I sometimes run into the situation when I'm cloning identical drive types, which might have identical partition layouts. Then, I need to identify which drive is which by the serial number, which is usually not easily accessible if the drive is buried inside a machine. So, I extract ONE of the two drives, run the program again, and it will tell me the serial number of the remaining drive in the machine. Knowing that, I can now tell which drive is which.
Sometimes, like last night, I was too tired and brain dead to do the job correctly. I started with a Dell Precision M6800 laptop, with two identical Toshiba hybrid 500GB drives. The plan was to clone the boot drive to a Samsung 860 500GB SSD. Rather than risk screwing things up, I decided to:
Make an image backup of the boot drive with Macrium Reflect to an external USB 3.0 hard disk.
Remove the unused second drive (D:).
Remove the boot (C:) drive and replace it with the SSD drive.
Restore the boot drive C: from the USB 3.0 hard disk to the SSD.
Replace the unused second drive (D:). This took longer than a direct drive to drive cloning copy, but since only one drive was in the machine at a time, there was no risk of overscribbling the wrong drive. It also gave me an image backup on the USB 3.0 hard disk just in case I somehow managed to clobber the boot drive(s). Better safe, than sorry.
--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
Master and slave drives went out of style with PATA (parallel ATA drives). SATA drives are the current fashion and does NOT share the controller on the master in order to share the ribbon cable bus with the slave drive.
However, I can see what you're trying to suggest. If you can positively designate which drive is the boot drive and designate it as the source, it's a fair assumption that you have the correct drive for the source, with the other drive being the destination.
That worked great until the BIOS allowed booting from literally any drive, including an external drive connected via USB. That made it rather difficult to identify the boot drive in a cloning program that offered little in the way of help for identifying the drive, or required command line amusements that had to be determined by the user, such as dd.
The example you give suggests that you're using Clonezilla: Great program for Linux, but not the best or fastest for Windoze. Details if anyone wants them. Time for a late dinner.
--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
I KISS by making a copy of a drive to another by ALWAYS making the source drive sdc (or primary master) and the destination sdd (or primary slave). Never a problem,except maybe no copy if destination is smaller.
Jeff Liebermann wrote in news: snipped-for-privacy@4ax.com:
Does a Linux session in Windows allow access to all drives?
If so, one would think that dd is the fastest, properly executed.
I have yet to test large file moves (movie files of 2 to 6 GB).
So far, Windows appears to do it in chunks of memory writes, then drive writes, using the Windows VM file as a buffer. I do not know if that is the best strategy.
DD likely operates pretty good, if the user specifies the parameters right. (or well enough). (haha he said Orwell)
rce software called "Clonezilla" it makes absolutely no attempt to identify drives in any meaningfull way by for example reading NTFS labels to give t he users some clue as to which drive is which. There may be some info inspe ction option in it's menu or not... I have not even used this software, jus t watched some youtube videos.
ying when I need to identify which is the boot drive and which is something totally else.
here to allow users to properly label their hardware ?!
to products, this would make me feel goooooood.
I love to hate you to tell you, you a retard. RAM contents are lost at powe r loss.
Irrelevant.
This is not what I called for.
This proves you are a retard. As far as I know all LABELS are related to fi le systems.
I want a non-file-sytem-label that simply labels that HARDWARE DISK itself.
INDEPEDENT OF OPERATING SYSTEMS, FILE SYSTEMS OR ANY SOFTWARE FOR THAT MATT ER EXCEPT IT'S OWN DEFINED API TO RETRIEVE THIS LABEL FROM THE HARDWARE.
PROVE IT. I'm pretty sure you'll be messing with some FILE SYSTEM.
WHAT IF IT'S A NEW FILESYSTEM UNKNOWN TO FILEZILLA, is you retarded brain c apable of comprehending this ?!
What if it's not formatted. Cloning is technically a sector by sector copy perhaps... It should not even need to known anything about file systems.
Clonezilla might optimize cloning by knowning about file systems, but theor etically it's not required.
This knowing of file systems clearly makes clonezilla weak, simply because it won't be able to handle any further file systems that it does not known of.
rce software called "Clonezilla" it makes absolutely no attempt to identify drives in any meaningfull way by for example reading NTFS labels to give t he users some clue as to which drive is which. There may be some info inspe ction option in it's menu or not... I have not even used this software, jus t watched some youtube videos.
ying when I need to identify which is the boot drive and which is something totally else.
here to allow users to properly label their hardware ?!
to products, this would make me feel goooooood.
HERE YOU GO YOU DUMB BITCH:
The very first google on "where is volume label stored" returns this inform ation without even clicking the link:
" From a Windows internals perspective, the label name is stored per volume i n a NTFS metafile called $Volume. A file record within exists called $Volum e_Name that contains the label name.Aug 24, 2014 "
THAT MEANS VOLUME LABELS ARE SOFTWARE STORED ON THE DISK and THUS CAN BE WH IPED AND THUS YOUR HARDWARE DISK BECOMES UNIDENTIFIEABLE BY VOLUME LABEL CA USE THE VOLUME LABEL IS NOT THERE.
HERE IS MY QUESTION FOR YOU RETARD:
HOW WILL YOU IDENTIFY YOUR DISK IF THERE IS NO VOLUME LABEL, WHEN THERE IS NO FILE SYSTEM.
YOU NOT CAPABLE OF UNDERSTANDING THIS MARKS YOU AS EITHER:
A VERY INEXPERIENCED NOOB WHO HAS ALWAYS HAD ONLY ONE DRIVE.
OR HAS NEVER DONE ANY VIRTUAL DISK OPERATINGS IN WINDOWS CAUSE THEN YOU WOULD HAVE NOTICED THIS DIFFICULTY OF IDENTIFIEING DRIVES AND VIRTUAL HARDD ISKS WHICH MIGHT EVEN HAVE THE SAME PROBLEM. FIGURING OUT ON WHICH PHYSICAL DRIVE A VIRTUAL DRIVE IS IS ONE OF THESE EXAMPLES.
OR A COMPLETE RETARD DOESN'T UNDERSTAND SHIT LOL.
OR A TROLL.
TIME TO WISE UP AND READ THE INFO ABOVE.
SEE YA.
ALSO BUY TWO DISKS AND START USING DISK MANAGEMENT IN WINDOWS AND GET A CLU E.
HERE IS A NICE CHALLENGE FOR YOU:
LABEL THE DISKS ANYWAY YOU WANT.
FORMAT YOUR DISKS/DELETE WINDOWS
SEE IF THE LABELS ARE STILL THERE LOLOLOLOLOLOLOLOLOLOLOL
(AND NO SERIAL NUMBERS DON'T CUT IT WHICH WAS THE WHOLE POINT OF THIS THREA D)
ource software called "Clonezilla" it makes absolutely no attempt to identi fy drives in any meaningfull way by for example reading NTFS labels to give the users some clue as to which drive is which. There may be some info ins pection option in it's menu or not... I have not even used this software, j ust watched some youtube videos.
noying when I need to identify which is the boot drive and which is somethi ng totally else.
ewhere to allow users to properly label their hardware ?!
ed to products, this would make me feel goooooood.
rmation without even clicking the link:
in a NTFS metafile called $Volume. A file record within exists called $Vol ume_Name that contains the label name.Aug 24, 2014
WHIPED AND THUS YOUR HARDWARE DISK BECOMES UNIDENTIFIEABLE BY VOLUME LABEL CAUSE THE VOLUME LABEL IS NOT THERE.
S NO FILE SYSTEM.
U WOULD HAVE NOTICED THIS DIFFICULTY OF IDENTIFIEING DRIVES AND VIRTUAL HAR DDISKS WHICH MIGHT EVEN HAVE THE SAME PROBLEM. FIGURING OUT ON WHICH PHYSIC AL DRIVE A VIRTUAL DRIVE IS IS ONE OF THESE EXAMPLES.
LUE.
EAD)
LOL EVEN SERIAL NUMBERS (volume serial numbers) ARE SOFTWARE DEPENDENT:
"
formatting link
volume serial number, sometimes seen as VSN, is a unique, hexadecimal numb er assigned to a drive during the creation of the file system during the fo rmat process.
The volume serial number is stored in the disk parameter block part of the volume boot record.
Microsoft and IBM added the volume serial number to the format process in 1
987 when they were working together to develop the OS/2 operating system. "
SO IT IS COMPLETELY USELESS TO IDENTIFIEING ACTUALY HARDWARE DEVICES/DISKS.
(IT CAN EVEN BE FAKED POSSIBLY) IT REQUIRES A FILE SYSTEM AND FILESYSTEM SP ECIFIC SOFTWARE.
THESE CLONE TOOLS DON'T LIKE THAT.
I DON'T LIKE IT AS WELL.
I WANT HARDWARE IDENTIFICATION WITH HARDWARE LABELS.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.