[SOLVED] external hard disk fails to show up on bootin/re-booting my system sometimes
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
external hard disk fails to show up on bootin/re-booting my system sometimes
hi all
here is an issue i face....
some days when i restart my slackware, i see that my external hard disk fails to boot up or show in the mount point i had set it to...hence, my external hard disk becomes unavailable to use during the session...need a restart again to show it come up....
yesterday, i did a dmesg log check on it when it didnt come up and then later restarted to check dmesg again...and here is one line i found missing when it didnt show up...
a line which maps sdb to sdb1 thats my device right there in my /etc/fstab as i had set it earlier...
precisely, [sdb]:[sdb1] //missing when the external hard disk doesnt show up
in both boot cases ie when EHD(external hard disk) not showing and showing, the HD is detected with details except this critical matching line not performed...
Last edited by nitecrawler; 08-04-2015 at 04:57 AM.
Reason: edit: writing from my office desktop presently...
Instead of giving the device explicitly, one may indicate the (ext2 or xfs) filesystem that is to be mounted by its UUID or volume label (cf. e2label(8) or xfs_admin(8)), writing LABEL=<label> or UUID=<uuid>, e.g., 'LABEL=Boot' or 'UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. This will make the system more robust: adding or removing a SCSI disk changes the disk device name but not the filesystem volume label
its mentioned there too....
i am just curious how the disk device name changes on adding or removing...so does it mean sdb could change to something else or is it sdb1 may change to sdb2 etc?
i am just curious how the disk device name changes on adding or removing...so does it mean sdb could change to something else or is it sdb1 may change to sdb2 etc?
That's actually the name of the SCSI disk that change. This can happen for instance if you plug in an USB stick before your external hard disk. If the USB stick has been found first by the kernel it will be called sdb, then the external hard disk sdc, etc. You can check that easily yourself. But the partitions will keep their numbers, e.g. the one that you knew as /dev/sb1 could be named /dev/sdc1 or /dev/sdd1, but not /dev/sdc2 or /dev/sdd2.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.