You are not logged in.

#1 2010-06-24 01:25:08

thunderc
Member
Registered: 2010-06-24
Posts: 3

[Solved] Corrupted harddrive caused issues with arch install disk

Im current working trying to install arch onto a shuttle xpc, with 500MB of ram and a 150 GB hd, problem is the hard drive doesnt seem to exist when i run the install disk


currently running ubuntu (planning to remove it completely and use arch on the computer)

Here's what I know:

the system boots from cd and i tell it to boot arch,
it starts the boot process.
then eventually it stalls and says:
waiting for boot device...

Waiting 30 seconds for /dev/disk/by-label/ARCH_201005 ...
sr 1:0:0:0: [sr0] Unhandled sence code
sr 1:0:0:0: [sr0] Result: hostbyte=0x00 drivebyte=0x08
sr 1:0:0:0: [sr0] Sense Key : 0x4 [current[
sr 1:0:0:0: [sr0] ASC=0x3e ASCQ=0x2
sr 1:0:0:0: [sr0] CDB : cdb[0]=0x28 : 28 00 00 02 88 96 00 00 02 00
end_request: I/O error, dev sr0, sector 6654152
Buffer I/O error on device sr0, logical block 83019

(it repeats that several time)

eventually it says:
UDF-fs: Partition marked read-only; forcing read-only mount
SUCCESS: Mounted archiso volume successfully

(at this it appears to continue normally)

once the cd boots all the way up i log in as root (as prompted)

if i type df i get:
Filesystem                 1K-blocks                  Used     Available       Use%      Mounted on
none                              383628                     4200      379428         2%                /
udev                               10240                       168             10072      2%                 /dev
none                               255748                         0            255748      0%               /dev/shm

if i then run the setup script it works fine until i get to the partition hardrive part,
i choose Auto-Prepare and leave the default 100 in the box (note: i have noticed that the Disk Space Left label says 0 MiB which seems odd)

Selecting OK:

in lower left-hand corner i get 'ERROR: ask_number $3 must be a number! not -100' and a command prompt on the next line.

..............................................

in the ubuntu install

df in the terminal gives me:

Filesystem               1k-blocks                 Used        Available      Mounted on
/dev/sda1                   152357444        4799328     139818804      /
udev                                   254616                260           254356         /dev
none                                  254616                  1144       254528        /dev/shm
none                                   254616                 88             254528       /var/run
none                                   254616                 0                254616       /var/lock
none                                  254616                   0              254616        /lib/init/rw




My guess is that my hard drive is corrupted in some way, but i dont know if I will need a new one, or if I can fix it by another means

please help if you can

Last edited by thunderc (2010-06-24 03:18:12)

Offline

#2 2010-06-24 02:14:38

thunderc
Member
Registered: 2010-06-24
Posts: 3

Re: [Solved] Corrupted harddrive caused issues with arch install disk

I just checked the integrity of the disk and it appears to be ok, which means i have no clue why the hard drive doesnt show up in the install cd

Offline

#3 2010-06-24 02:51:36

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

Re: [Solved] Corrupted harddrive caused issues with arch install disk

df is only going to show mounted filesystems. The Arch installer doesn't mount anything for you. Look at 'fdisk -l' for a fair comparison.

Offline

#4 2010-06-24 03:16:05

thunderc
Member
Registered: 2010-06-24
Posts: 3

Re: [Solved] Corrupted harddrive caused issues with arch install disk

Thanks for the reply,

I just solved the problem actually,
I used a gparted live cd and recreated the partition that way, apparently my superblock was corrupted

df is only going to show mounted filesystems. The Arch installer doesn't mount anything for you. Look at 'fdisk -l' for a fair comparison

i didnt know that, thanks

Offline

Board footer

Powered by FluxBB