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.

Pre-clear doesn't list drive...

Featured Replies

I have a strange issue; I am just going through the process of setting up my new unRAID server. I have three old 250GB drives that I want to preclear.

 

I have added these drives to the server and booted up. All three appear in the list of drives when the add-on SATA card boots upduring post, and all three drives appear in the web GUI in the drives list to be allocated (though I of course haven't allocated any of them to the array yet), but when I run "preclear_disk.sh -l" from the terminal, to find the /dev/sd? drive path, one of the drives (a Hitachi Deskstar) does not appear on the list.

 

I therefore can't start the pre-clear on this drive, as I can't finish the command with the drive path. The drive is from an old PC (the one I have converted into an unRAID server), so it is already formatted to NTFS.

 

I'm sure I have probably missed thing really obvious, but I haven't been able to find anything searching on the issue, and I am an absolute Linux beginner!

 

Thanks in advance for any help you can give.

Have you assigned the Hitachi to one of the drive slots in unRAID?  If so, unassign it and try again.

 

If not, post your syslog (refer to the troubleshooting link in my sig for instructions)

I have a strange issue; I am just going through the process of setting up my new unRAID server. I have three old 250GB drives that I want to preclear.

 

I have added these drives to the server and booted up. All three appear in the list of drives when the add-on SATA card boots upduring post, and all three drives appear in the web GUI in the drives list to be allocated (though I of course haven't allocated any of them to the array yet), but when I run "preclear_disk.sh -l" from the terminal, to find the /dev/sd? drive path, one of the drives (a Hitachi Deskstar) does not appear on the list.

 

I therefore can't start the pre-clear on this drive, as I can't finish the command with the drive path. The drive is from an old PC (the one I have converted into an unRAID server), so it is already formatted to NTFS.

 

I'm sure I have probably missed thing really obvious, but I haven't been able to find anything searching on the issue, and I am an absolute Linux beginner!

 

Thanks in advance for any help you can give.

First, the drives reported in the "-l" have nothing to do with which you may clear.  It is a guide to help the less experienced.

 

When you request any drive to be pre-cleared, it will have to pass another series of tests before I'll let the pre-clear run on it.  Those tests are all to prevent the pre-clear from being run on a disk that is in use or assigned to the array.  (keeps you from shooting yourself in the foot)

 

All that said, I'm human and obviously do not have every possible hardware combination here, so it is possible for the script to exclude a drive from being a possible pre-clear candidate when it might be otherwise.

 

If you can post the output of a few commands, I'll try to figure out what is happening on your server.

 

Could you please post the output of the following commands:

ls -l /dev/disk/by-id/ | grep -v -- "-part"

 

ls -l /dev/disk/by-path/ | grep -v -- "-part"

 

mount

cat /boot/config/disk.cfg

 

Also, please attach a copy of your system log.  (as an attachment)  See the instructions under "Troubleshooting" in the wiki for how to capture a copy of it.

 

Joe L.

Oh yes, one more thing... what version of the pre-clear script are you using?  I know the initial version with the "-l" command has been enhanced several times. 

 

preclear_disk.sh -v

 

current version as of this post is version 1.1.

 

Joe L.

  • Author

Thanks for coming back to me guys...

 

@ bjp 999

 

No, I haven't assigned the drive to the array yet, it just appear in the list of 'assignable' drives. I will get the Syslog and post it up - should I post the entire thing,

 

@ Joe L.

 

Version of the preclear script is the latest one I think - or at least a release since you added to -A setting for advanced format drives.

 

Regarding your comment about being 'human', please don't take my query the wrong way, your pre-clear script is excellent - a fantastic way of getting the disks ready without taking the array down - it is not a criticism of it by any stretch. It is much more likely that I have done something wrong somewhere!!

 

Which is exactly the case with the '-l', command. I thought this displayed all drives in the system that weren't already added to the array - so my lack of Linux knowledge shining through!

 

Is there a general Linux command I can run to show all drives and their /dev/sd* paths, or do drives need to show up in the list generated by the '-l' command to be able to use the preclear script with them?

 

I will run the other commands you have listed, when I get home tonight, and post the results.

Thanks for coming back to me guys...

 

@ bjp 999

 

No, I haven't assigned the drive to the array yet, it just appear in the list of 'assignable' drives. I will get the Syslog and post it up - should I post the entire thing,

Yes.  Zip it if is too large otherwise... they compress well

 

Version of the preclear script is the latest one I think - or at least a release since you added to -A setting for advanced format drives.

There have been 5 versions since I added the "-A" option.  use "preclear_disk.sh -v" to see your version. current version as of this post is "1.1"

Regarding your comment about being 'human', please don't take my query the wrong way, your pre-clear script is excellent - a fantastic way of getting the disks ready without taking the array down - it is not a criticism of it by any stretch. It is much more likely that I have done something wrong somewhere!!

Or I did not anticipate something that shows in certain hardware configurations.  It is why I asked for the output of the commands.

 

Which is exactly the case with the '-l', command. I thought this displayed all drives in the system that weren't already added to the array - so my lack of Linux knowledge shining through!

It is supposed to be a listing of those that are not already assigned to the array.

Is there a general Linux command I can run to show all drives and their /dev/sd* paths,

Yes, the two "ls" commands I gave in my prior post.
or do drives need to show up in the list generated by the '-l' command to be able to use the preclear script with them?
Actually they do not need to be in the list generated by the "-l" option.  But they do need to not be assigned to your array, and not currently busy, and not mounted, and be a valid "block" device.  Those tests will occur before the disk may be pre-cleared.

 

I'd like to fix the "-l" option if it not working correctly, so you can help everybody by assisting me with the output of those commands.

I will run the other commands you have listed, when I get home tonight, and post the results.

Great... I'll be curious what is happening.

 

Joe L.

  • Author

Joe, results as follows:

 

Just to clarify -

'sdb' - is currently being processed with preclear_disk.sh

'sde/f' - have been pre-cleared and are assigned as data disks in the array

'sdd' - has been pre-cleared and is waiting for me to make the initial data copy from the existing NAS before being assigned as the parity drive

'sdg' - has been precleared and is waiting to be assigned as cache drive

'sdc/h' - awaiting preclear, but don't appear in the 'preclear_disk.sh -l' list, which appears as follows:

 

root@Tower:/boot# preclear_disk.sh -l

========================================

Disks not assigned to the unRAID array

  (potential candidates for clearing)

========================================

    /dev/sdb = ata-SAMSUNG_SP2504C_S09QJ1QP306628

    /dev/sdd = ata-WDC_WD20EARS-00MVWB0_WD-WCAZA2081945

    /dev/sdg = ata-WDC_WD740GD-00FLC0_WD-WMAKE2243184

 

 

ls -l /dev/disk/by-id/ | grep -v -- "-part"

 

total 0

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-SAMSUNG_SP2504C_S09QJ1QP306628 -> ../              ../sdb

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA1988119                -> ../../sde

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA2023359                -> ../../sdf

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA2081945                -> ../../sdd

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-WDC_WD740GD-00FLC0_WD-WMAKE2243184 ->                ../../sdg

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_HDS722525VLSA80_VN6JTECFEBZ3AA                -> ../../sdc

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_SAMSUNG_SP2504CS09QJ1QP306628 -              > ../../sdb

lrwxrwxrwx 1 root root  9 Jan 23 12:17 scsi-SATA_SAMSUNG_SP2504CS09QJ1QP306643 -              > ../../sdh

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA1988119                -> ../../sde

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA2023359                -> ../../sdf

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA2081945                -> ../../sdd

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_WDC_WD740GD-00FWD-WMAKE2243184                -> ../../sdg

lrwxrwxrwx 1 root root  9 Jan 23 11:39 usb-SanDisk_Cruzer_Blade_2004220390118E60              77C2-0:0 -> ../../sda

 

ls -l /dev/disk/by-path/ | grep -v -- "-part"

 

total 0

lrwxrwxrwx 1 root root  9 Jan 23 11:39 pci-0000:00:0b.1-usb-0:3:1.0-scsi-0:0:0:0 -> ../../sda

lrwxrwxrwx 1 root root  9 Jan 23 11:39 pci-0000:00:0e.1-scsi-0:0:0:0 -> ../../sdd

lrwxrwxrwx 1 root root  9 Jan 23 11:39 pci-0000:00:0e.1-scsi-1:0:0:0 -> ../../sde

lrwxrwxrwx 1 root root  9 Jan 23 11:39 pci-0000:00:0e.2-scsi-0:0:0:0 -> ../../sdf

lrwxrwxrwx 1 root root  9 Jan 23 11:39 pci-0000:00:0e.2-scsi-1:0:0:0 -> ../../sdg

lrwxrwxrwx 1 root root  9 Jan 23 11:39 pci-0000:01:00.0-sas-phy0:1-0x0000000000000000:0-lun0 -> ../../sdb

lrwxrwxrwx 1 root root  9 Jan 23 11:39 pci-0000:01:00.0-sas-phy1:1-0x0100000000000000:1-lun0 -> ../../sdc

lrwxrwxrwx 1 root root  9 Jan 23 12:17 pci-0000:01:00.0-sas-phy2:1-0x0200000000000000:2-lun0 -> ../../sdh

 

mount

 

fusectl on /sys/fs/fuse/connections type fusectl (rw)

usbfs on /proc/bus/usb type usbfs (rw)

/dev/sda1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed)

nfsd on /proc/fs/nfs type nfsd (rw)

/dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)

/dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,noacl,nouser_xattr)

shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other,default_permissions)

 

cat /boot/config/disk.cfg

 

# Disk configuration

spindownDelay=1

queueDepth=1

spinupGroups=yes

defaultFormat=2

md_num_stripes_default=1280

md_write_limit_default=768

md_sync_window_default=288

disk1=pci-0000:00:0e.1-scsi-1:0:0:0

disk2=pci-0000:00:0e.2-scsi-0:0:0:0

diskSpindownDelay.1=-1

diskSpindownDelay.2=-1

diskSpinupGroup.1=host5

diskSpinupGroup.2=host6

 

Also, please attach a copy of your system log.  (as an attachment)  See the instructions under "Troubleshooting" in the wiki for how to capture a copy of it.

 

Joe L.

 

Attached! If you need anything else, let me know.

syslog.zip

  • Author

@ Joe

 

Now that you're commands have told me what the /dev/sd* paths are for the missing two drives, I have been able to start the preclear script on each of them.

 

So thanks for that, but it will still be interesting to know why they don't appear in the '-l' list.

me too.

Ill look at it tonight when I get home.

what version of preclear_disk.sh are you using?

 

Type

preclear_disk.sh -v

to find out.

  • Author

what version of preclear_disk.sh are you using?

 

Type

preclear_disk.sh -v

to find out.

 

Version .9.9d

  • Author

Have you had any luck on this Joe? Just for info, I have upgraded to v1.1, and the drives still don't appear in the list - I'm just interested to know your thoughts before I add the drives to the array, in case the reason they are not listing is some fault in my system.

 

Have you had any luck on this Joe? Just for info, I have upgraded to v1.1, and the drives still don't appear in the list - I'm just interested to know your thoughts before I add the drives to the array, in case the reason they are not listing is some fault in my system.

 

I was distracted and did not get to look in detail, until you reminded me just now...

 

I did discover the cause though...

 

If you look at the output of your listing of /dev/disk-by-id you will see "ata-" prefaced names for all your disks EXCEPT the three that do not show up in the "preclear_disk.sh -l" 

 

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-SAMSUNG_SP2504C_S09QJ1QP306628 -> ../              ../sdb

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA1988119                -> ../../sde

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA2023359                -> ../../sdf

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA2081945                -> ../../sdd

lrwxrwxrwx 1 root root  9 Jan 23 11:39 ata-WDC_WD740GD-00FLC0_WD-WMAKE2243184 ->                ../../sdg

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_HDS722525VLSA80_VN6JTECFEBZ3AA                -> ../../sdc

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_SAMSUNG_SP2504CS09QJ1QP306628 -              > ../../sdb

lrwxrwxrwx 1 root root  9 Jan 23 12:17 scsi-SATA_SAMSUNG_SP2504CS09QJ1QP306643 -              > ../../sdh

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA1988119                -> ../../sde

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA2023359                -> ../../sdf

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA2081945                -> ../../sdd

lrwxrwxrwx 1 root root  9 Jan 23 11:39 scsi-SATA_WDC_WD740GD-00FWD-WMAKE2243184                -> ../../sdg

lrwxrwxrwx 1 root root  9 Jan 23 11:39 usb-SanDisk_Cruzer_Blade_2004220390118E60              77C2-0:0 -> ../../sda

 

On my system, there is an "ata-" listing and for all my disks, and for some, a "scsi-" listing. 

 

The preclear script was only using the "ata-" listings.  It was bypassing the "scsi-" listings as duplicates.

 

On your system the "scsi-" lines are not all duplicates.

 

I was attempting to not have the same disk appear twice in the output listing, so I was excluding the "scsi-" listings entirely.  The original logic worked... except for your system with its add-on SATA card, where there are no "ata-" device listings.

 

I've changed how I eliminate the duplicate listing of potential drives to be cleared.    Your previous post allowed my to see what it was.

 

The next version of preclear_disk.sh will have the fix.

 

Joe L.

  • Author

Hi Joe,

 

Thanks for that. I have tried v1.2 and it list all drives perfectly.

 

You'll have to excuse my ignorance, but what do the 'ata' and 'scsi' terms on the drive listings mean? The sata card is the usual Supermicro card recommended on this forum, so I am a bit woried if my system is the only ones thats setting up drives differently somehow?

Hi Joe,

 

Thanks for that. I have tried v1.2 and it list all drives perfectly.

 

You'll have to excuse my ignorance, but what do the 'ata' and 'scsi' terms on the drive listings mean? The sata card is the usual Supermicro card recommended on this forum, so I am a bit woried if my system is the only ones thats setting up drives differently somehow?

Don't be worried, you are just the first with that card to try the "-l" option and notice drives missing.

 

"ata" refers to the protocol used to talk to the disks. 

See here: http://en.wikipedia.org/wiki/Parallel_ATA

"SATA" drives are treated as "scsi" drives and I thought all would have an "ata" entry too.  It depends on the "udev" rules on your version of unRAID and how it creates device entries for hardware.

 

In any case, now you know as much as me.

 

Joe L.

  • Author

This is a bit beyond my understanding unfortunately, but all the drives are SATA so I'm surprised the system uses Parallel ATA to talk to a SATA drive, but as long as nothing is amiss and my drives arebeing setup properly, I'm happy!

  • 1 year later...

I seem to be experiencing something similar.  Just added two disks, sdr & sdq, and neither are appearing in -l (v1.13)

 

root@Tower:~# ls -l /dev/disk/by-id/ | grep -v -- "-part"
total 0
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-Hitachi_HDS722020ALA330_JK1130YAGX9TVT -> ../../sds
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD154UI_49101A461A7KRV -> ../../sdg
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD154UI_618331FS806845 -> ../../sdu
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD154UI_S1XWJ1KZ101601 -> ../../sdc
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD154UI_S1XWJ1MSA01151 -> ../../sdt
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD154UI_S1Y6J1KS516326 -> ../../sdw
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD154UI_S1Y6J1KS516537 -> ../../sda
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD154UI_S1Y6J1KS616605 -> ../../sdl
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD203WI_S1UYJ1KZ313963 -> ../../sdo
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD204UI_S2H7J9JB716995 -> ../../sdj
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD204UI_S2HGJ1BZ824876 -> ../../sdv
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-SAMSUNG_HD501LJ_S12ZJ1CPA10595 -> ../../sdb
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-ST2000DL003-9VT166_5YD51R7B -> ../../sdi
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-ST2000DL003-9VT166_6YD05CDC -> ../../sdk
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-ST3000DM001-9YN166_W1F0AVDS -> ../../sdp
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-ST3000DM001-9YN166_W1F0C9MK -> ../../sdh
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-ST32000542AS_5XW11NCD -> ../../sdn
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA3623485 -> ../../sdd
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA3624247 -> ../../sdm
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-WDC_WD30EZRS-00J99B0_WD-WCAWZ0273281 -> ../../sdq
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-WDC_WD30EZRS-00J99B0_WD-WCAWZ0370365 -> ../../sdr
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 ata-WDC_WD3200AAJS-60Z0A0_WD-WCAV2N177967 -> ../../sdf
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_Hitachi_HDS7220_JK1130YAGX9TVT -> ../../sds
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD154UI49101A461A7KRV -> ../../sdg
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD154UI618331FS806845 -> ../../sdu
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD154UIS1XWJ1KZ101601 -> ../../sdc
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD154UIS1XWJ1MSA01151 -> ../../sdt
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD154UIS1Y6J1KS516326 -> ../../sdw
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD154UIS1Y6J1KS516537 -> ../../sda
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD154UIS1Y6J1KS616605 -> ../../sdl
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD203WIS1UYJ1KZ313963 -> ../../sdo
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD204UIS2H7J9JB716995 -> ../../sdj
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD204UIS2HGJ1BZ824876 -> ../../sdv
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_SAMSUNG_HD501LJS12ZJ1CPA10595 -> ../../sdb
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_ST2000DL003-9VT_5YD51R7B -> ../../sdi
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_ST2000DL003-9VT_6YD05CDC -> ../../sdk
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_ST3000DM001-9YN_W1F0AVDS -> ../../sdp
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_ST3000DM001-9YN_W1F0C9MK -> ../../sdh
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_ST32000542AS_5XW11NCD -> ../../sdn
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA3623485 -> ../../sdd
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA3624247 -> ../../sdm
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_WDC_WD30EZRS-00_WD-WCAWZ0273281 -> ../../sdq
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_WDC_WD30EZRS-00_WD-WCAWZ0370365 -> ../../sdr
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 scsi-SATA_WDC_WD3200AAJS-_WD-WCAV2N177967 -> ../../sdf
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 usb-Kingston_DataTraveler_2.0_89980116200801151425ECE9-0:0 -> ../../sde
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50000f001ba10595 -> ../../sdb
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50000f001ba1a700 -> ../../sdg
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50000f003a088654 -> ../../sdu
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x5000c50029e671ec -> ../../sdn
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x5000c5003650ca75 -> ../../sdk
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x5000c5003e34445a -> ../../sdi
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x5000c5004567e88a -> ../../sdp
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x5000c5004574be4f -> ../../sdh
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x5000cca221ccdf2f -> ../../sds
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50014ee1581f7ab2 -> ../../sdf
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50014ee205a35292 -> ../../sdr
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50014ee25ac5ae03 -> ../../sdm
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50014ee25ac5b05b -> ../../sdd
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50014ee2b03064c2 -> ../../sdq
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50024e90018362e8 -> ../../sdw
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50024e9001836fd6 -> ../../sda
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50024e9001913228 -> ../../sdl
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50024e900245b1c1 -> ../../sdt
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50024e9002c2b3a6 -> ../../sdc
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50024e90033320de -> ../../sdo
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50024e9003eedfe8 -> ../../sdv
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 wwn-0x50024e9205c64b46 -> ../../sdj
root@Tower:~# ls -l /dev/disk/by-path/ | grep -v -- "-part"
total 0
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 pci-0000:00:12.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 pci-0000:00:12.0-scsi-3:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 pci-0000:00:12.0-scsi-4:0:0:0 -> ../../sdc
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 pci-0000:00:12.0-scsi-5:0:0:0 -> ../../sdd
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 pci-0000:00:13.5-usb-0:8:1.0-scsi-0:0:0:0 -> ../../sde
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 pci-0000:03:00.0-scsi-1:0:0:0 -> ../../sdf
lrwxrwxrwx 1 root root  9 2012-08-26 11:16 pci-0000:03:00.0-scsi-1:0:1:0 -> ../../sdg
root@Tower:~# mount
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
/dev/sde1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed)
/dev/sdb1 on /mnt/cache type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md17 on /mnt/disk17 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md15 on /mnt/disk15 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md13 on /mnt/disk13 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md10 on /mnt/disk10 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md6 on /mnt/disk6 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md18 on /mnt/disk18 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md11 on /mnt/disk11 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md14 on /mnt/disk14 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md9 on /mnt/disk9 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md8 on /mnt/disk8 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md12 on /mnt/disk12 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md16 on /mnt/disk16 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md5 on /mnt/disk5 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md7 on /mnt/disk7 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other,default_permissions)
shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other,default_permissions)
root@Tower:~# cat /boot/config/disk.cfg
# Generated settings:
spindownDelay="30"
queueDepth="1"
spinupGroups="no"
defaultFormat="2"
startState="STOPPED"
md_num_stripes="1280"
md_write_limit="768"
md_sync_window="288"
diskSpindownDelay.0="-1"
diskSpinupGroup.0="host7"
diskSpindownDelay.1="-1"
diskSpinupGroup.1="host4"
diskExport.1="e"
diskSecurity.1="public"
diskReadList.1=""
diskWriteList.1=""
diskExportNFS.1="e"
diskSecurityNFS.1="public"
diskHostListNFS.1=""
diskExportAFP.1="-"
diskSecurityAFP.1="public"
diskReadListAFP.1=""
diskWriteListAFP.1=""
diskVolsizelimitAFP.1=""
diskSpindownDelay.2="-1"
diskSpinupGroup.2="host5"
diskExport.2="e"
diskSecurity.2="public"
diskReadList.2=""
diskWriteList.2=""
diskExportNFS.2="-"
diskSecurityNFS.2="public"
diskHostListNFS.2=""
diskExportAFP.2="-"
diskSecurityAFP.2="public"
diskReadListAFP.2=""
diskWriteListAFP.2=""
diskVolsizelimitAFP.2=""
diskSpindownDelay.3="30"
diskSpinupGroup.3="host0"
diskExport.3="e"
diskSecurity.3="public"
diskReadList.3=""
diskWriteList.3=""
diskExportNFS.3="-"
diskSecurityNFS.3="public"
diskHostListNFS.3=""
diskExportAFP.3="-"
diskSecurityAFP.3="public"
diskReadListAFP.3=""
diskWriteListAFP.3=""
diskVolsizelimitAFP.3=""
diskSpindownDelay.4="-1"
diskSpinupGroup.4="host7"
diskExport.4="e"
diskSecurity.4="public"
diskReadList.4=""
diskWriteList.4=""
diskExportNFS.4="-"
diskSecurityNFS.4="public"
diskHostListNFS.4=""
diskExportAFP.4="-"
diskSecurityAFP.4="public"
diskReadListAFP.4=""
diskWriteListAFP.4=""
diskVolsizelimitAFP.4=""
diskSpindownDelay.5="-1"
diskSpinupGroup.5="host10"
diskExport.5="e"
diskSecurity.5="public"
diskReadList.5=""
diskWriteList.5=""
diskExportNFS.5="-"
diskSecurityNFS.5="public"
diskHostListNFS.5=""
diskExportAFP.5="-"
diskSecurityAFP.5="public"
diskReadListAFP.5=""
diskWriteListAFP.5=""
diskVolsizelimitAFP.5=""
diskSpindownDelay.6="-1"
diskSpinupGroup.6="host10"
diskExport.6="e"
diskSecurity.6="public"
diskReadList.6=""
diskWriteList.6=""
diskExportNFS.6="-"
diskSecurityNFS.6="public"
diskHostListNFS.6=""
diskExportAFP.6="-"
diskSecurityAFP.6="public"
diskReadListAFP.6=""
diskWriteListAFP.6=""
diskVolsizelimitAFP.6=""
diskSpindownDelay.7="-1"
diskSpinupGroup.7="host10"
diskExport.7="e"
diskSecurity.7="public"
diskReadList.7=""
diskWriteList.7=""
diskExportNFS.7="-"
diskSecurityNFS.7="public"
diskHostListNFS.7=""
diskExportAFP.7="-"
diskSecurityAFP.7="public"
diskReadListAFP.7=""
diskWriteListAFP.7=""
diskVolsizelimitAFP.7=""
diskSpindownDelay.8="-1"
diskSpinupGroup.8="host10"
diskExport.8="e"
diskSecurity.8="public"
diskReadList.8=""
diskWriteList.8=""
diskExportNFS.8="-"
diskSecurityNFS.8="public"
diskHostListNFS.8=""
diskExportAFP.8="-"
diskSecurityAFP.8="public"
diskReadListAFP.8=""
diskWriteListAFP.8=""
diskVolsizelimitAFP.8=""
diskSpindownDelay.9="-1"
diskSpinupGroup.9="host1"
diskExport.9="e"
diskSecurity.9="public"
diskReadList.9=""
diskWriteList.9=""
diskExportNFS.9="-"
diskSecurityNFS.9="public"
diskHostListNFS.9=""
diskExportAFP.9="-"
diskSecurityAFP.9="public"
diskReadListAFP.9=""
diskWriteListAFP.9=""
diskVolsizelimitAFP.9=""
diskSpindownDelay.10="-1"
diskSpinupGroup.10="host1"
diskExport.10="e"
diskSecurity.10="public"
diskReadList.10=""
diskWriteList.10=""
diskExportNFS.10="-"
diskSecurityNFS.10="public"
diskHostListNFS.10=""
diskExportAFP.10="-"
diskSecurityAFP.10="public"
diskReadListAFP.10=""
diskWriteListAFP.10=""
diskVolsizelimitAFP.10=""
diskSpindownDelay.11="-1"
diskSpinupGroup.11="host1"
diskExport.11="e"
diskSecurity.11="public"
diskReadList.11=""
diskWriteList.11=""
diskExportNFS.11="-"
diskSecurityNFS.11="public"
diskHostListNFS.11=""
diskExportAFP.11="-"
diskSecurityAFP.11="public"
diskReadListAFP.11=""
diskWriteListAFP.11=""
diskVolsizelimitAFP.11=""
diskSpindownDelay.12="-1"
diskSpinupGroup.12="host1"
diskExport.12="e"
diskSecurity.12="public"
diskReadList.12=""
diskWriteList.12=""
diskExportNFS.12="-"
diskSecurityNFS.12="public"
diskHostListNFS.12=""
diskExportAFP.12="-"
diskSecurityAFP.12="public"
diskReadListAFP.12=""
diskWriteListAFP.12=""
diskVolsizelimitAFP.12=""
diskSpindownDelay.13="-1"
diskSpinupGroup.13="host1"
diskExport.13="e"
diskSecurity.13="public"
diskReadList.13=""
diskWriteList.13=""
diskExportNFS.13="-"
diskSecurityNFS.13="public"
diskHostListNFS.13=""
diskExportAFP.13="-"
diskSecurityAFP.13="public"
diskReadListAFP.13=""
diskWriteListAFP.13=""
diskVolsizelimitAFP.13=""
diskSpindownDelay.14="30"
diskSpinupGroup.14="host1"
diskExport.14="e"
diskSecurity.14="public"
diskReadList.14=""
diskWriteList.14=""
diskExportNFS.14="-"
diskSecurityNFS.14="public"
diskHostListNFS.14=""
diskExportAFP.14="-"
diskSecurityAFP.14="public"
diskReadListAFP.14=""
diskWriteListAFP.14=""
diskVolsizelimitAFP.14=""
diskSpindownDelay.15="30"
diskSpinupGroup.15="host1"
diskExport.15="e"
diskSecurity.15="public"
diskReadList.15=""
diskWriteList.15=""
diskExportNFS.15="-"
diskSecurityNFS.15="public"
diskHostListNFS.15=""
diskExportAFP.15="-"
diskSecurityAFP.15="public"
diskReadListAFP.15=""
diskWriteListAFP.15=""
diskVolsizelimitAFP.15=""
diskSpindownDelay.16="-1"
diskSpinupGroup.16="host1"
diskExport.16="e"
diskSecurity.16="public"
diskReadList.16=""
diskWriteList.16=""
diskExportNFS.16="-"
diskSecurityNFS.16="public"
diskHostListNFS.16=""
diskExportAFP.16="-"
diskSecurityAFP.16="public"
diskReadListAFP.16=""
diskWriteListAFP.16=""
diskVolsizelimitAFP.16=""
diskSpindownDelay.17=""
diskSpinupGroup.17=""
diskExport.17="e"
diskSecurity.17="public"
diskReadList.17=""
diskWriteList.17=""
diskExportNFS.17="-"
diskSecurityNFS.17="public"
diskHostListNFS.17=""
diskExportAFP.17="-"
diskSecurityAFP.17="public"
diskReadListAFP.17=""
diskWriteListAFP.17=""
diskVolsizelimitAFP.17=""
diskSpindownDelay.18=""
diskSpinupGroup.18=""
diskExport.18="e"
diskSecurity.18="public"
diskReadList.18=""
diskWriteList.18=""
diskExportNFS.18="-"
diskSecurityNFS.18="public"
diskHostListNFS.18=""
diskExportAFP.18="-"
diskSecurityAFP.18="public"
diskReadListAFP.18=""
diskWriteListAFP.18=""
diskVolsizelimitAFP.18=""
diskSpindownDelay.19=""
diskSpinupGroup.19=""
diskExport.19="e"
diskSecurity.19="public"
diskReadList.19=""
diskWriteList.19=""
diskExportNFS.19="-"
diskSecurityNFS.19="public"
diskHostListNFS.19=""
diskExportAFP.19="-"
diskSecurityAFP.19="public"
diskReadListAFP.19=""
diskWriteListAFP.19=""
diskVolsizelimitAFP.19=""
diskSpindownDelay.20=""
diskSpinupGroup.20=""
diskExport.20="e"
diskSecurity.20="public"
diskReadList.20=""
diskWriteList.20=""
diskExportNFS.20="-"
diskSecurityNFS.20="public"
diskHostListNFS.20=""
diskExportAFP.20="-"
diskSecurityAFP.20="public"
diskReadListAFP.20=""
diskWriteListAFP.20=""
diskVolsizelimitAFP.20=""
cacheId="SAMSUNG_HD501LJ_S12ZJ1CPA10595"
cacheSpindownDelay=""
cacheSpinupGroup="host3"
cacheExport="e"
cacheSecurity="public"
cacheReadList=""
cacheWriteList=""
cacheExportNFS="-"
cacheSecurityNFS="public"
cacheHostListNFS=""
cacheExportAFP="-"
cacheSecurityAFP="public"
cacheReadListAFP=""
cacheWriteListAFP=""
cacheVolsizelimitAFP=""

syslog.txt

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.