Hdparm Failed Input Output Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the hdparm missing passwd workings and policies of this site About Us Learn more about Stack hdparm frozen Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions hdparm disable security Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it hdparm erase only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top hdparm: SECURITY_SET_PASS: Input/output error up vote 1 down vote favorite I'm trying to use hdparm to secure erase an SSD as suggested here. Following the directions in that guide has worked okay
Security Unlock Input Output Error
so far, but I can't seem to resolve this error: ~ $ sudo hdparm --user-master m --security-set-pass NUL /dev/sda security_password="NUL" /dev/sda: Issuing SECURITY_SET_PASS command, password="NUL", user=master, mode=high SECURITY_SET_PASS: Input/output error I've searched around and tested things, as suggested here, but to no avail. How else can I deep-wipe an SSD, if this is not an option? Note: Yes, there is a BIOS password "on" the hard disk, in that it must be typed at boot, but it's not (as far as I know) attached to the disk itself. sudo hdparm -I /dev/sda: /dev/sda: ATA device, with non-removable media Model Number: SanDisk SDSSDA240G Serial Number: 153655402044 Firmware Revision: U21010RL Media Serial Num: Media Manufacturer: Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Used: unknown (minor revision code 0x0110) Supported: 9 8 7 6 5 Likely used: 9 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 468862128 Logical Sector size: 512 bytes Phy
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad
Master Password Revision Code = 65534
Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook hdparm remove password Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please unlock ssd read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] HDIO_Drive_CMD failed: input/output error Having an Issue With Posting ? Do you want to http://unix.stackexchange.com/questions/252265/hdparm-security-set-pass-input-output-error help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 4 of 4 Thread: HDIO_Drive_CMD failed: input/output error Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode May 4th, 2008 #1 Nonsense View Profile View Forum Posts Private Message 5 Cups of Ubuntu Join https://ubuntuforums.org/showthread.php?t=781793 Date Nov 2007 Location Sweden Beans 44 DistroUbuntu 9.10 Karmic Koala HDIO_Drive_CMD failed: input/output error Every now and then my Ubuntu freezes and then gives me a black screen with the following message: Code: /dev/sda1: Setting Advanced Power Management level disabled HDIO_Drive_CMD failed: input/output error I looked around the forum a bit and some suggest Code: hdparm -b 255 but that just gives me the same message as when the desktop crashes: Code: /dev/sda1: Setting Advanced Power Management level disabled HDIO_Drive_CMD failed: input/output error Suggestions? Adv Reply November 16th, 2008 #2 panfist View Profile View Forum Posts Private Message Just Give Me the Beans! Join Date Mar 2007 Beans 57 Re: HDIO_Drive_CMD failed: input/output error I have the same problem. Adv Reply November 17th, 2008 #3 Nonsense View Profile View Forum Posts Private Message 5 Cups of Ubuntu Join Date Nov 2007 Location Sweden Beans 44 DistroUbuntu 9.10 Karmic Koala Re: HDIO_Drive_CMD failed: input/output error It turns out that my problem was due to a faulty ram. I pulled out the bad memory and my problems are gone. Run memtest that comes with the Live CD and ch
Member Registered: 2007-12-10 Posts: 46 Hard disk spindown setting not working I have a Seagate ST4000VX000 drive, and I seem to be unable to prevent it from parking the heads.The drive goes https://bbs.archlinux.org/viewtopic.php?id=193711 to either sleep or standby after very short time, even if I use hdparm -S 0. I get the message "setting standby to 0 (off)" but this does not help. Granted, http://www.larkinweb.co.uk/computing/spinning_down_hard_drives_in_linux.html the drive is functional again within some seconds. However, I have concerns that the disk may deteriorate unnecessarily. Moreover, the lag can be annoying. For example, if I am working on a input output text file and the drive went to sleep while grabbing a coffee, I need to wait for it to wake up until I can start typing again.I tried hdparm -S0 and also a high value of the sleep timer (e.g., hdparm -S 242), without results.The drive complains when I try to use the APM method, so hdparm -B 255 fails with "HDIO_DRIVE_CMD failed: Input/output input output error error" and hdparm -B says "APM_level = not supported"The documentation from Seagate says that "The drive provides programmable power management to provide greater energy efficiency. In most systems, users can control power management through the system setup program". And the data sheet mentions idle3: "Idle3 spin control features enable power-on in standby mode or drive spin‐down to conserve power and improve reliability during archival periods."I have not tried to set the sleep time in the windows power settings, because I believe that this will not be a permanent setting. On the other hand, I could not find any utility from Seagate that would allow to permanently change the timers.Currently I am running out of ideas. I tried "idle3ctl --force -g" to see if I could get idle3 tools to play with the drive (given that idle3 was mentioned in the data sheet), but I get "sg16(VSC_ENABLE) failed: Input/output error"By the way, the SSD in the system also fails in hdparm -B, and I am wondering if this could be related to BIOS settings. I seem to remember disabling APM some time ago because I was having some
Oxford in the snow, 2010 panoramas » Oyster Bay » Lake Placid » Paris » The Louvre » Versailles Orangery » Versailles Façade » Slioch from Loch Maree » Camas Mor Bay science computing workshop miscellany contact web-mail homecomputing Computing menu Previous article:Accurate ISO files from CDs Next article:Changing Munin default graph colours Useful links Computing home About this category Contact me Spinning down hard drives in Linux I have a system with an SSD containing my OS (OpenSUSE) and a lot of my data as well as a traditional spinning hard drive with extra data. I don't often access the data on the spinning hard drive so would like to be able to spin it down to both make it quieter and use less energy. This turned out to be harder than originally envisaged. The ultimate solution is below but here's a little background to start. hdparm and initial troubles There's a linux utility called hdparm which is designed to get or set parameters on SATA or IDE hard drives. This is what everyone recommends using to set your idle timeout on the drive. The parameter you want to set for spin-down timing is '-S' which is a value from 1 to 255. The values between 1 and 240 represent an idle timeout of value x 5 seconds, e.g. a value of 1 is a timeout of 5 seconds and a value of 120 is a timeout of 10 minutes: $ sudo hdparm -S 120 /dev/sdb Unfortunately, this didn't work for me. Even when I set the timeout to 5 seconds, the disk didn't spin down. I tried manually making the disk spin down: $ sudo hdparm -C /dev/sdb /dev/sdb: drive state is: active/idle $ sudo hdparm -Y /dev/sdb /dev/sdb: issuing sleep command $ sudo hdparm -C /dev/sdb /dev/sdb: drive state is: standby This worked fine which suggested that there was perhaps a process still trying to access the disk, thereby preventing it spinning down. To troubleshoot this I installed iotop (available in many distribution's repositories). By running iotop and using the "o" (only active processes) and "a" (accumulating) options in the program, you can see which processes are accessing data from hard drives. I couldn't find a way to distinguish between data access from different hard drives but it was clear from the list of processes that none of them were accessing the hard drive I wanted to spin down: Some further googling led me to this related askubuntu questi