Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[SOLVED - BAD MB] new system, cant get HD to clear

Featured Replies

 

 

First time user, Rinning unraid 4.7 free version in a new machine.. I can get it loaded, I can access it via //tower, I can see my HD via

 

Dmesg|grep SATA|grep link

 

But unRaid wont recognize it through the gui nor can I get a preclear started through the console.  Since it’s a new array with no data, I think I should be able to clear it within unRaid also, but it cant seem to see it.  Ive tried different sata ports, and I ensured its not emulating an ide port in the BIOS, Ive tried different flash drives and Ive ensured the flash drive is named UNRAID

 

Ive tried 5rc2 then back down to 4.7 with same results

USING a GA-a75 MB and an a6-3500 APU, single rail PSU and, 4gb corsair memory, 2tb new segate barracuda.

The HD/MB/APU are brand new

Attached is my syslog..

 

Thanks

 

 

Sorry forgot to include the error when trying to preclear

I typed (at the boot prompt)

Quote

preclear_disk.sh -A /dev/sda

and was returned

Quote

Sorry, but /dev/sda is currently mounted and in use:

/dev/sda on /boot type vfat (re.noatime, nodiratime, unmask=0, shortname=mixed)

clearing will NOT be performed

root@tower:/boot#

 

 

Joe L.

 

 

The device you are giving is the device of your flash drive is /dev/sda, mounted at /boot.

 

What do you get when you type:

preclear_disk.sh -l

 

It will list the disks available for clearing.

 

The device you are attempting to clear is already mounted (and is your flash drive). 

You would never clear a disk that is mounted, and never clear your fl

syslog_5-18_new_install_of_4.7.txt

  • Author
****************************

Disks not assigned to the unRaid array

(potential candidates for clearing)

****************************

No un-assigned disks detected

 

  • Author

I believe so.. let me shutdown and re-check.  It DOES show up when I send this to the console

 

Dmesg|grep SATA|grep link

 

 

ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

 

unless this is my flashdrive that Joe was referring to

What does "Dmesg|grep SATA|grep link" output? It is showing sda because that is the one you selected to pre-clear. What makes you certain the the disk shows in "Dmesg|grep SATA|grep link"?

  • Author

ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

 

unless this is my flashdrive that Joe was referring to.. 

 

shutting down to check BIOS

  • Author

There is not a section is this bios (ami bios v6.00pg)  that specifically identifies the sata drives.  Is that where my problem is, MB is not seeing the hard drive?

  • Author

I think Im going to reset bios to defaults and go over the settings..  switch cables/ports again. If I dont see a change, Ill probably rip a known good sata out of my main PC and see if It will recognize it.  The hard drive in the unRaid box was taken out of a new external enclosure (cheaper than a comparable internal drive at the time), and if its bad.. I guess Im out $109 since the warranty is void.

 

Like Joe pointed out, the sda that I saw was the flash drive

and your BIOS suggestion echoes that also..

 

Thanks for steering me in the right direction guys, Ill report back when I put a known drive in the box and go through the BIOS.

 

 

I think Im going to reset bios to defaults and go over the settings..  switch cables/ports again. If I dont see a change, Ill probably rip a known good sata out of my main PC and see if It will recognize it.  The hard drive in the unRaid box was taken out of a new external enclosure (cheaper than a comparable internal drive at the time), and if its bad.. I guess Im out $109 since the warranty is void.

 

Like Joe pointed out, the sda that I saw was the flash drive

and your BIOS suggestion echoes that also..

 

Thanks for steering me in the right direction guys, Ill report back when I put a known drive in the box and go through the BIOS.

It could be the SATA ports are disabled in the BIOS, or, it could be there is no power to the drive (because of a bad cable, or a cable not seated properly, or a bad power splitter, or slot in the case.)

 

Until the drive is seen by the BIOS (and unRAID) there is nothing for you to use the preclear script on.

 

What disk controller are you using?  Are you using a NORCO style case?  Are you using a breakout cable?  (if so, are you using the correct type of breakout cable, there are two types)

 

Joe L.

ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

 

unless this is my flashdrive that Joe was referring to.. 

 

shutting down to check BIOS

 

This does not refer to the flash. Is there only one drive in the system?

  • Author

dgaschk, Yes there is only one HD hooked up.. its a brand new board with a new drive.  Ill have to wait till this evening before I 'dig in', Im about to head to work.  Ill check the BIOS and connections before I start switching drives around.

Thants what was throwing me off.. when I sent this to it.

 

Dmesg|grep SATA|grep link

 

it returned

 

ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

 

 

Joe its a plain vanilla mid-tower, using the onboard sata controller off the AMD a-75.  And Im just using the cables that came with the motherboard. I do have some monoprice sataIII cables from my daily beater that Ill try tonight too.  Family is going out of town, so I'll have plenty of time to tinker with it.

 

 

 

 

Apparently the disk is not identifying itself.  (and, not sure, but the motherboard BIOS might be using a USB interface which might not support the identify needed)

 

May 18 04:27:26 Tower kernel: scsi 0:0:0:0: Direct-Access              USB DISK 2.0    PMAP PQ: 0 ANSI: 0 CCS

May 18 04:27:26 Tower kernel: usb-storage: device scan complete

May 18 04:27:26 Tower kernel: sd 0:0:0:0: [sda] 3915776 512-byte logical blocks: (2.00 GB/1.86 GiB)

May 18 04:27:26 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off

May 18 04:27:26 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00

May 18 04:27:26 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through

May 18 04:27:26 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through

May 18 04:27:26 Tower kernel:  sda: sda1

May 18 04:27:26 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through

May 18 04:27:26 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk

May 18 04:27:26 Tower kernel: ata1.00: qc timeout (cmd 0xec)

May 18 04:27:26 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

May 18 04:27:26 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

May 18 04:27:26 Tower kernel: ata1.00: qc timeout (cmd 0xec)

May 18 04:27:26 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

May 18 04:27:26 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps

May 18 04:27:26 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

May 18 04:27:26 Tower kernel: ata1.00: qc timeout (cmd 0xec)

May 18 04:27:26 Tower kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

May 18 04:27:26 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

  • Author

Found the problem.. Bad onboard SATA, could not get it to recognize three different drives with various cables and power ports.  Changed BIOS to every combination including emulating IDE and even the fail safe settings.  I upgraded the BIOS and downgraded it.  And have come to the realitity that I will be making a trip to frys/microcenter this weekend.

 

Thanks for the time and effort guys!  Im thinking round two will be a lot better for me.

 

Any FM1 bords that anyone has real-world experience with? 

 

Found the problem.. Bad onboard SATA, could not get it to recognize three different drives with various cables and power ports.  Changed BIOS to every combination including emulating IDE and even the fail safe settings.  I upgraded the BIOS and downgraded it.  And have come to the realitity that I will be making a trip to frys/microcenter this weekend.

 

Thanks for the time and effort guys!  Im thinking round two will be a lot better for me.

 

Any FM1 bords that anyone has real-world experience with?

Did you try the 5.0-rc3 release? You have nothing to lose, and it could be your SATA chipset id not supported in the older kernel used in the 4.7 release.

 

Joe L.

  • Author

Yes I did Joe...  I even tried loading luniux live and a bootable flash drive version of a windows install I have.  Both the OS installs looked good until it came to choosing a destination disk to install to, which came up with an empty list every time.

 

Hopefully Ill be reporting a running system in a few days when I get time to exchange/get a new MB.  Should I steer away from these Gigabyte a75 boards, or did I just get a bad one?  I have a AsusZ68/i5 for my daily beater that I love other than the 90degree satas.  And an Asrock a51 FM1 thats been trouble free as a frontend since day one.  Never owned a Gigabyte product but had always thought of them is a decent upper mid-range board.

 

Thanks again for yours and dgaschks time and help.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.