Go Back   TechArena Community > Software > Operating Systems
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



Fedora /dev/sda1 is not valid block device

Operating Systems


Reply
 
Thread Tools Search this Thread
  #1  
Old 28-07-2009
Member
 
Join Date: Jul 2009
Posts: 17
Fedora /dev/sda1 is not valid block device
  

I have asus motherboard and i use Fedora 6. My board has an onboard Promise 378 RAID controller. I am not using raid but just conencting an additional drive through it. At first i got this error :
Code:
$ sudo mount -v /dev/sda1 /mnt/sda1 -t ext3
mount: /dev/sda1 is not a valid block device
After trying for sometime the disk was detected and i partitioned it. I mounted the disk successfully to sda1 and I could also write to the disk. I just edited the /etc/fstab file and added the following line :
Code:
/dev/sda1    /mnt/sda1    ext3    defaults    0 0
But then after reboot the disk failed to mount and i cannot access it.
My dmsg shows :
Code:
SCSI subsystem initialized
libata version 2.00 loaded.
sata_promise 0000:03:04.0: version 1.04
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 23 (level, low) -> IRQ 193
sata_promise PATA port found
ata1: SATA max UDMA/133 cmd 0xF0836200 ctl 0xF0836238 bmdma 0x0 irq 193
ata2: SATA max UDMA/133 cmd 0xF0836280 ctl 0xF08362B8 bmdma 0x0 irq 193
ata3: PATA max UDMA/133 cmd 0xF0836300 ctl 0xF0836338 bmdma 0x0 irq 193
scsi0 : sata_promise
ata1: SATA link down (SStatus 0 SControl 0)
scsi1 : sata_promise
ata2: SATA link down (SStatus 0 SControl 300)
scsi2 : sata_promise
ata3.00: ATA-7, max UDMA/133, 320173056 sectors: LBA48 
ata3.00: ata3: dev 0 multi count 0
ata3.00: configured for UDMA/133
  Vendor: ATA       Model: Maxtor 4R160L4    Rev: RAMB
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1
sd 2:0:0:0: Attached scsi disk sda
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
device-mapper: multipath: version 1.0.4 loaded
device-mapper: multipath round-robin: version 1.0.0 loaded
device-mapper: table: 253:0: multipath: error getting device
device-mapper: ioctl: error adding target to table
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
audit(1165767520.088:2): enforcing=1 old_enforcing=0 auid=4294967295
security:  3 users, 6 roles, 1560 types, 166 bools, 1 sens, 1024 cats
security:  58 classes, 48173 rules
sd 2:0:0:0: Attached scsi disk sda
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
device-mapper: multipath: version 1.0.4 loaded
device-mapper: multipath round-robin: version 1.0.0 loaded
device-mapper: table: 253:0: multipath: error getting device
device-mapper: ioctl: error adding target to table
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
audit(1165767520.088:2): enforcing=1 old_enforcing=0 auid=4294967295
security:  3 users, 6 roles, 1560 types, 166 bools, 1 sens, 1024 cats
security:  58 classes, 48173 rules
SELinux:  Completing initialization.
SELinux:  Setting up existing superblocks.
SELinux: initialized (dev dm-0, type ext3), uses xattr
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev eventpollfs, type eventpollfs), uses task SIDs
SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev cpuset, type cpuset), not configured for labeling
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
audit(1165767520.444:3): policy loaded auid=4294967295
Any help? Thanks!

Reply With Quote
  #2  
Old 28-07-2009
Member
 
Join Date: Jan 2008
Posts: 3,384
Re: Fedora /dev/sda1 is not valid block device

I would suggest you to mount the disk manually from console. Use the command you used before :
Code:
sudo mount -v /dev/sda1 /mnt/sda1 -t ext3
This might get the disk mounted. Also check if all the cables are properly connected and it has no physical connection problems, else the drive can be damaged. If this doesn't help, reboot and try once again. Else post back...
Reply With Quote
  #3  
Old 28-07-2009
Member
 
Join Date: Jul 2009
Posts: 17
Re: Fedora /dev/sda1 is not valid block device

I tried manually mouting the disk too, but still i get the following error that occured the first time :
Code:
$ sudo mount -v /dev/sda1 /mnt/sda1 -t ext3
mount: /dev/sda1 is not a valid block device
Any other help? I don't know whats wrong. Please help.
Reply With Quote
  #4  
Old 28-07-2009
Member
 
Join Date: Apr 2008
Posts: 3,260
Re: Fedora /dev/sda1 is not valid block device

I had the same problem when i was with fedora 6. Everything worked well with Fedora 5, as soon as i updated to fedora 6 i could not mount the second drive. I tried to clean install fedora 6 and the same problem with the second drive. Whenever i tried to mount any drive i would get "mount: /dev/xxx is not a valid block device". Then i updated fedora 6 and i could mount the second drive. Fedora 6 had this bug.. Update your fedora and your disk would be able to mount...
Reply With Quote
  #5  
Old 08-01-2010
Member
 
Join Date: Jan 2010
Posts: 1
Re: Fedora /dev/sda1 is not valid block device

Ok try to do the next,

find ./ -name sda

the problem in my case was the path, this wasn't /dev/sda1, when I did the find I had:

#find ./ -name sda1
./sys/devices/platform/musb_hdrc/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
./sys/class/block/sda1
./dev/block/sda1

with that, now you can mount the partition

#mount /dev/block/sda1 /mnt
#df -h
Filesystem Size Used Available Use% Mounted on
/dev/block/vold/179:2
7.3G 359.3M 6.6G 5% /
tmpfs 91.2M 0 91.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block//vold/179:1
69.5M 2.3M 67.2M 3% /sdcard
/dev/block/sda1 245.5M 10.0M 235.5M 4% /mnt

Regards
Echavolla
Reply With Quote
Reply

  TechArena Community > Software > Operating Systems
Tags: , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Fedora /dev/sda1 is not valid block device"
Thread Thread Starter Forum Replies Last Post
1/4 block auto-block and 1/6 block auto throw techniques destroying Street Fighter X Tekken Rashid Video Games 6 30-04-2012 12:30 PM
How to remotely Block Sim-on service to KMS 9 running device Mudhol Portable Devices 4 02-10-2011 07:45 PM
I receive "The device, \Device\Harddisk1\D, has a bad block." Hasit Windows XP Support 4 07-04-2010 03:10 PM
Openfiler Cant partition block device correctly zaid Operating Systems 3 08-08-2009 01:29 PM
device hard disk has a bad block Daiwikr Windows XP Support 2 14-03-2007 10:35 AM


All times are GMT +5.5. The time now is 12:04 AM.