As the title says, I have under my care a SuperMicro server running a hardware RAID 6 with a MegaRAID SAS 8708ELP on Linux. I have two failed disks that I have identified as the drives in slot 2 and 4, howerver, my boss tells me that the drives are somewhat scrambled and since the slots start in 0, I'm not sure which hard disks I'm supposed to be changing. I tried to find out the serial number of the drives so I could compare with the drives I remove, but all the commands I've been running to find such info haven't been working.
Windows View Disk Serial Number
Windows If your drive is connected to your computer: Seagate has created a very simple tool that will tell you the serial number and the model number of any and all Seagate, Samsung and Maxtor-brand drives connected in or to your computer. Use the DriveDetect.exe method to find both numbers.
If your drive is not detected or connected to your computer: The USB devices have the serial numbers printed on the external cases and internal drives have the serial and part numbers on the drive labels.
Hello guys,I need to find out what is my drive's serial number under win XP.I know that there are one serial number from manufacturer (real hard drive) and serial numbers generated by windows.I know that if disk is partitioned into more partitions that each partition will have unique serial number called Volume serial number.That number can be obtained by typing dir into cmd prompt.Is there any other way to find out real serial number without need to open case.
For XP, navigate: start>control panel>system, select the 'hardware' tab>device manager, expand 'disk drives' then right click on the hdd in question. select properties then click the 'details' tab. from the drop down box select 'hardware ids' and bingo.....info should include brand name manufacturer,interface type,model no,serial etc, all you should need!!
Therefore, the serial number is the best way to establish which drive is which without having to shut down and open the case, and even then you may not know which one is E or F (especially with serial drives, SATA). For my system, I keep a sheet of paper with all my hard drive serial numbers on it, and the drives are numbered with yellow electricians tape.
GetDiskSerial.DLL is a standard Windows DLL that does not depend on the "support" libraries. You can use it to read the serial number of hard disk easily. As we all know, this serial number is unique in the world. So this DLL is of great use, for example, you can use this serial number to create an machine id or encrypt number.
I am new to Netapp and looking for a way to get the serial numbers on the disk shelves we have attached to our filers without a physical visit to our Co-lo's. we have a fas2240-2, V3240, and a fas3140?
As described above, to know what motherboard model and serial number you have is very important. Hence, this part will talk about some solutions to find out motherboard model and serial number. You can pick one to check the information freely.
Motherboard model and serial number details can also be found in Windows system information. However, this way sometimes cannot work. If your motherboard is compatible, this method may be the easiest way to check your PC motherboard model and serial number.
But this 'serial number' didn't match with I could see in iDRAC. The ones that were working correctly had the correct serial number. I tried to change it in PRTG (maybe there is a way, but I couldn't find it). So I removed the sensor and re-added the same disk, and sure enough it works, and with the correct serial number! I don't know why or how it changed (I'm assuming Dell's OMSA SNMP picked up a different number for the disk upon reboot), but removing and re-adding the sensor for the same disk allowed PRTG to look for the updated serial number.
Removing and re-adding the sensor works for me as well, but only until the next reboot, at which point it will break again. What seems to be happening in my case is that the last digit of the serial gets cut of on one reboot and re-added on the next reboot, then cut off again, and so on. Is there any way I can make the PRTG sensor more flexible by either using a wildcard for the serial number or by ignoring the serial number and just using the physical location/SAS port (which does not change between reboots)?
Unfortunately, as of now, there's no way of inserting a wildcard for the disk serial. The only workaround would be to pause the old sensor infinitely and create a new one once it fails :( Is there any update available for the target host ILO to prevent that from happening by any chance?
Actually, by "their own software", I meant "OpenManage Essentials" running on a separate server. So it does not get restarted when these servers do, nor does iDRAC (I would need to cut power for that to happen). I'm guessing Dell does not use the serial number as an identifying marker on disks, but rather the "Connector - Enclosure - Disk" combo because I've ran into issues in the past where disks where replaced without following proper procedure and the "failed" flag would carry over to the new disk, even though the serial number had changed. Controller simply didn't care or wasn't smart enough to reset the flag.
I'm having similar issues with disk sensors on a UCS FMC device. The error code is PE156 We have tried recreating the sensors, but this error still intermittently comes up. The time interval between errors does not appear to have any pattern. Any other suggestions??The disk with the serial number "xxxxxx" could not be found. The reason might be that the respective disk was replaced or that there was a server restart. To resolve this issue, remove the respective sensor and add it anew. (code: PE156) This issue only appeared recently (March 5th, 2021). We performed a version update last month and are on PRTG version 21.1.65.1767+
I had this problem with IDRAC8 where PRTG no longer recognizes the serial numbers of some SSD disks. After logging into Idrac, i noticed that there too the Serial Numbers did not appear for these disks, so I restarted my IDRAC and the Serial Numbers returned and PRTG recognized them again.
As an administrator, you can find details about the ChromeOS devices in your domain in the Google Admin console. You can see the user of each device and review information, such as serial number, enrollment date, and last synchronization. You can also create organizational units to apply settings to different groups of devices.
Click the serial number of any device to see device details. On the left, you can choose to move, disable, deprovision, clear user profiles, or remotely access a device. If the device is an autolaunched kiosk, you can also choose to reboot, capture logs, take a screenshot, set the volume on the device.
The Volume Serial Number (also known as VSN) is a unique serial number that is assigned to an optical disk (CD or DVD) or a hard drive after formatting. The Volume Serial Number was added by Microsoft and IBM so that the operating system could recognize if an optical disk or a drive is changed on the system. By that time the only way to determine this, was the volume label (Volume Name) that the user defined to each storage disk. But that way, there was a problem if a user gave the same (Volume) name to two (or more) disks. To bypass this problem, Microsoft and IBM decided to assign a new unique number in hexadecimal form (called 'Volume Serial Number' or 'Volume ID' or 'VSN') when a drive (optical disk or hard drive) was formatted.
Taking advantage of VSN, some software vendors use the Volume Serial Number to avoid pirate copying of their products. This means that software from these vendors can not run if the Volume Serial Number is different from the VSN of the product's original optical disk that was shipped or of the hard drive that the software was first installed. Also this technique was previously used by multiplayer game vendors to ban the gamers that tried to cheat. Nowadays, this method is useless because the game or software vendors now use the hardcoded serial number (HDD Manufacture's S/N that is embedded into the firmware) to identify (ban) cheaters or they ban the CD key.
In windows 10 (Oct 2018) I get "The parameter is incorrect" when trying to change the VolumeID of the C: drive using the SysInternals volumeid.exe. Also the Hard Disk Serial Number Changer fails with the error "Unable to write to this disk in drive". Any ideas how I can change the volumeID?Just for info, I have tried this with Windows10 VM running under Fusion on Mac OS, ands also with Win10 installed on a BOOTCAMP partition on Mac also. No joy with either. Windows is installed under EFI setup, so GPT volume. Not sure if this is the cause?
Program on disk C.CMD Run administrator.cd c:\Volumeid.exe C: 1234-5678Restart.C: 1234-5678 -Disk and new numberReading the number.C:\Windows\System32\cmd.exe As a file .batRunning on a changed drive.Write in.vol
Oh this is incredibly kind guide I have ever found today. Thank you so much.But unfortunately, this doesn't work for the number of the Sandisk I have.. I think it is the product issue.. because the micro SD which is from Samsung works fine with both ways(volumeID and Hard Disk Serial Number Changer).
It would be better to point out that the volume serial number is a general identifyer for all volumes, not only for a disk and that what you are talking about here, is only the volume serial number of the first volume (partition) of a disk.
Thank you for listing the recent addition to diskpart. I use the tool as part of my job and had never played with that feature. Unfortunately I think that is a different ID than what people here are talking about. If you type 'vol c:' at a command prompt you will see a Serial number that is unrelated to the uniqueid. One of the giveaways is that each partition has an ID, but uniqueid only deals with a disk (that may contain several partitions). I believe the number being discussed here lives in the VBR. 2ff7e9595c
Comments