Input/output Error During Read On /tmp/ Sda
Contents |
we highly recommend that you visit our Guide for New Members. Solved: Input/output error during read on /dev/sda...on installing Ubuntu 10.04 Discussion in 'Linux and Unix' started by Vyomgrisham, Jan 31, input/output error during read on /dev/sda gparted 2011. Thread Status: Not open for further replies. Advertisement Vyomgrisham Thread Starter Joined: Jan 27,
Input/output Error During Write On /dev/sdb
2011 Messages: 7 I have an Emachines D725 series laptop with a seagate 250 GB hard drive.I have been trying to install Ubuntu
Input/output Error During Read On /dev/sdb Gparted
Netbook 10.04 from my flash drive ( tried with CD too...no luck ).The boot order is set to detect USB first. This is the error message I get "Input/output error during read on /dev/sda" while installing Ubuntu
Error Fsyncing/closing /dev/sdb Input/output Error
10.04 on my hard drive. On clicking Retry, The installation shows 15 % completed and returns another error " The ext4 file system creation in partition 5 of SCSI (0,0,0) (sda) failed. The Ubuntu runs perfectly from the pen drive and the disk utility which I ran from Ubuntu showed my disk as healthy ( the utility was not able to format the hard drive either... ). I was able to install windows XP on the error fsyncing/closing /dev/sda1 input/output error same hard drive later after formatting it.It seems there is nothing wrong with my hard drive as even running chkdsk didnt bring out anything.I am not sure if I missing out anything here...any help would be much appreciated. Vyomgrisham, Jan 31, 2011 #1 Sponsor lotuseclat79 Joined: Sep 12, 2003 Messages: 20,583 Hi Vyomgrisham, Welcome to TSG! Ubuntu 10.10 (Maverick Meerkat) is the latest version available until April when a new release 11.04 is scheduled. Prior to attempting to install Ubuntu, it is necessary to create a partition on your disk. If you entire disk is already formatted for WinXP on an NTFS file system, you need to repartition the disk and create at least say a 10-20GB or more partion for EXT4 in which to install Ubuntu. If you don't setup the EXT4 partition prior to attempting to install Ubuntu - that could be the cause of your I/O problems. From what you describe, I would boot up from your USB, and then use the GParted partition editor to repartition your 250GB harddrive to create the EXT4 partition to receive Ubuntu Netbook for dual-boot with WinXP or for the entire partition which would wipe WinXP out on the harddrive. Then proceed with the installation. -- Tom lotuseclat79, Jan 31, 2011 #2 Vyomgrisham Thread Starter Joined: Jan 27, 2011 Messages: 7 Than
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings error fsyncing/closing /dev/sda input/output error gparted and policies of this site About Us Learn more about Stack Overflow error fsyncing/closing /dev/mmcblk0rpmb the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users input output error during read on dev sda centos Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it https://forums.techguy.org/threads/solved-input-output-error-during-read-on-dev-sda-on-installing-ubuntu-10-04.977983/ works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Why am I getting “Input/output error during read on /dev/sda” during a CentOS text-mode installation? up vote 1 down vote favorite I'm trying to install CentOS 5.7 on an HP Proliant DL380 G5 (with an HP P400 Smart Array RAID controller) http://serverfault.com/questions/399236/why-am-i-getting-input-output-error-during-read-on-dev-sda-during-a-centos-te and am getting the following error during the text mode installer: ERROR: pdc: reading /dev/sda[Input/output error] Input/output error during read on /dev/sda To me, this sounds like either a faulty drive or unsupported hardware. That being said, the server appears to be fine (I'm in the process of running diagnostics) and I see it listed on the RedHat HCL: https://hardware.redhat.com/show.cgi?id=228312 Is there anything else I can be checking? centos redhat hard-drive hp-proliant share|improve this question edited Jun 15 '12 at 18:06 Dmitri Chubarov 1,8811820 asked Jun 15 '12 at 17:44 Mike B 3,9611967111 2 A proliant probably has a raid controller. Is the raid array initialized? –Dmitri Chubarov Jun 15 '12 at 17:49 @DmitriChubarov It does indeed - HP P400 Smart Array RAID. Can you please clarify what you mean by initialize? –Mike B Jun 15 '12 at 17:52 1 Mike, When you set up a new server, on the first boot you enter the RAID BIOS and configure the array. –Dmitri Chubarov Jun 15 '12 at 17:53 3 See this array configuration guide &n
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http://unix.stackexchange.com/questions/39905/input-output-error-when-accessing-a-directory Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is https://answers.launchpad.net/ubuntu/+question/239746 a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can output error answer The best answers are voted up and rise to the top “Input/output error” when accessing a directory up vote 39 down vote favorite 9 I want to list and remove the content of a directory on a removable hard drive. But I have experienced "Input/output error": $ rm pic -R rm: cannot remove `pic/60.jpg': Input/output error rm: cannot remove `pic/006.jpg': Input/output error rm: cannot remove `pic/008.jpg': Input/output error output error during rm: cannot remove `pic/011.jpg': Input/output error $ ls -la pic ls: cannot access pic/60.jpg: Input/output error -????????? ? ? ? ? ? 006.jpg -????????? ? ? ? ? ? 006.jpg -????????? ? ? ? ? ? 011.jpg I was wondering what the problem is? How can I recover or remove the directory pic and all of its content? My OS is Ubuntu 12.04, and the removable hard drive has ntfs filesystem. Other directories not containing or inside pic on the removable hard drive are working fine. Added: Last part of output of dmesg after I tried to list the content of the directory: [19000.712070] usb 1-1: new high-speed USB device number 2 using ehci_hcd [19000.853167] usb-storage 1-1:1.0: Quirks match for vid 05e3 pid 0702: 520 [19000.853195] scsi5 : usb-storage 1-1:1.0 [19001.856687] scsi 5:0:0:0: Direct-Access ST316002 1A 0811 PQ: 0 ANSI: 0 [19001.858821] sd 5:0:0:0: Attached scsi generic sg2 type 0 [19001.861733] sd 5:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB) [19001.862969] sd 5:0:0:0: [sdb] Test WP failed, assume Write Enabled [19001.865223] sd 5:0:0:0: [sdb] Cache data unavailable [19001.865232] sd 5:0:0:0: [sdb] Assuming drive cache: write through [19001.867597] sd 5:0:0:0: [sdb] Test WP failed, assume Write Enabled [19001.869214] sd 5:0:0:0: [sdb] Cache data unavailable [19001.869218] sd 5:0:0:
went black and all I saw was a black screen with a GRUB command line and a flashing cursor. I rebooted the netbook and still just got the flashing cursor and GRUB I then booted up Ubuntu off a USB stick and ran boot repair After doing this there was no boot menu and on startup windows automatically loads. I ran boot repair again and got the same outcome. Below is the output from running boot repair. Are you able to help me to get back the GRUB so I can choose to run Ubuntu instead of always windows? Thanks Sam Boot Info Script e7fc706 + Boot-Repair extra info [Boot-Info 6Nov2013] ============================= Boot Info Summary: =============================== => Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sda. => Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sdb. sda1: __________________________________________________________________________ File system: ntfs Boot sector type: Windows 7/2008: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Windows 7 Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe sda2: __________________________________________________________________________ File system: ntfs Boot sector type: Windows 7/2008: NTFS Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: sda3: __________________________________________________________________________ File system: Boot sector type: - Boot sector info: Mounting failed: mount: unknown filesystem type '' sda4: __________________________________________________________________________ File system: Extended Partition Boot sector type: Unknown Boot sector info: sdb1: __________________________________________________________________________ File system: vfat Boot sector type: SYSLINUX 4.05 20120702 Boot sector info: Syslinux looks at sector 1639136 of /dev/sdb1 for its second stage. SYSLINUX is installed in the directory. According to the info in the boot sector, sdb1 starts at sector 0. But according to the info from fdisk, sdb1 starts at sector 32. Operating System: Boot files: /syslinux/syslinux.cfg /ldlinux.sys ============================ Drive/Partition Info: ============================= Drive: sda _____________________________________________________________________ Partition Boot Start Sector End Sector # of Sectors Id System /dev/sda1 * 2,048 209,717,247 209,715,200 7 NTFS / exFAT / HPFS /dev/sda2 209,717,248 467,388,415 257,671,168 7 NTFS / exFAT / HPFS /d